Skip to content
GitLab
Projects
Groups
Snippets
Help
Loading...
Help
Help
Support
Community forum
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
Open sidebar
emacs
emacs
Commits
bda2c1ff
Commit
bda2c1ff
authored
Aug 11, 2005
by
Lute Kamstra
Browse files
(generic-font-lock-defaults): Declare with define-obsolete-variable-alias.
parent
248634e9
Changes
2
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
with
10 additions
and
2 deletions
+10
-2
lisp/ChangeLog
lisp/ChangeLog
+9
-0
lisp/emacs-lisp/generic.el
lisp/emacs-lisp/generic.el
+1
-2
No files found.
lisp/ChangeLog
View file @
bda2c1ff
2005-08-11 Richard M. Stallman <rms@gnu.org>
* battery.el (battery-status-function): Don't use ignore-errors.
2005-08-11 Lute Kamstra <lute@gnu.org>
* emacs-lisp/generic.el (generic-font-lock-defaults): Declare with
define-obsolete-variable-alias.
2005-08-11 Stefan Monnier <monnier@iro.umontreal.ca>
2005-08-11 Stefan Monnier <monnier@iro.umontreal.ca>
* net/ange-ftp.el: Use \\` and \\' instead of ^ and $ in regexps.
* net/ange-ftp.el: Use \\` and \\' instead of ^ and $ in regexps.
...
...
lisp/emacs-lisp/generic.el
View file @
bda2c1ff
...
@@ -102,8 +102,7 @@
...
@@ -102,8 +102,7 @@
(
defvar
generic-font-lock-keywords
nil
(
defvar
generic-font-lock-keywords
nil
"Keywords for `font-lock-defaults' in a generic mode."
)
"Keywords for `font-lock-defaults' in a generic mode."
)
(
make-variable-buffer-local
'generic-font-lock-keywords
)
(
make-variable-buffer-local
'generic-font-lock-keywords
)
(
defvaralias
'generic-font-lock-defaults
'generic-font-lock-keywords
)
(
define-obsolete-variable-alias
'generic-font-lock-defaults
'generic-font-lock-keywords
"22.1"
)
(
make-obsolete-variable
'generic-font-lock-defaults
'generic-font-lock-keywords
"22.1"
)
;;;###autoload
;;;###autoload
(
defvar
generic-mode-list
nil
(
defvar
generic-mode-list
nil
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
.
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment