summaryrefslogtreecommitdiff
path: root/etc/NEWS
diff options
context:
space:
mode:
authorChong Yidong <cyd@gnu.org>2012-03-05 11:13:46 +0800
committerChong Yidong <cyd@gnu.org>2012-03-05 11:13:46 +0800
commit50ab02c5cc9c84ecb6459bb3b1a041154365f8ac (patch)
tree0e8715167a79f9a9aec43cfedcf9459717de926d /etc/NEWS
parentee30fbcdd3813fef35f401702c9fbedfdf837397 (diff)
downloademacs-50ab02c5cc9c84ecb6459bb3b1a041154365f8ac.tar.gz
etc/NEWS: Mention impact of old-style backquotes on key sequences.
Diffstat (limited to 'etc/NEWS')
-rw-r--r--etc/NEWS16
1 files changed, 10 insertions, 6 deletions
diff --git a/etc/NEWS b/etc/NEWS
index 2629155110f..b611d726eea 100644
--- a/etc/NEWS
+++ b/etc/NEWS
@@ -1049,12 +1049,16 @@ of the header line.
** Support for "old-style" backquotes, which have been obsolete for
more than 10 years, has been further reduced. Now a backquote not
followed by a space is always treated as a "new-style" backquote.
-Please consider completely removing all "old-style" backquotes from
-your code as a matter of some urgency. If your code uses backquotes
-as documented in the Elisp manual, and compiles without warning, then
-you have nothing to do in this regard. Code not following the
-appropriate conventions may fail to compile. The most common cause of
-trouble seems to be an old-style backquote followed by a newline.
+Please remove all "old-style" backquotes from your code. If your code
+uses backquotes as documented in the Elisp manual, and compiles
+without warning, then you have nothing to do in this regard. Code not
+following the appropriate conventions may fail to compile.
+
+The most common cause of trouble seems to be an old-style backquote
+followed by a newline. Another cause of trouble is vector notation
+for key sequence notation: instead of [(control ,)] and [(control ')],
+you should write [(control ?,)] and [(control ?')], which will work in
+older Emacs too.
+++
** The macro `eval-at-startup' was removed in Emacs 23.2, but this