aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorGlenn Morris2012-02-06 00:04:36 -0800
committerGlenn Morris2012-02-06 00:04:36 -0800
commit2b18055e4e523798eb6e826a2ed3949c9dfcefc3 (patch)
treefd4a01bceaf44ed54745d589c4c177598c088a6b
parent42a275e05e9a0f4bfe2d83f0c5f57070bee2ae9e (diff)
downloademacs-2b18055e4e523798eb6e826a2ed3949c9dfcefc3.tar.gz
emacs-2b18055e4e523798eb6e826a2ed3949c9dfcefc3.zip
Expand NEWS entry on old-style backquotes.
-rw-r--r--etc/NEWS11
1 files changed, 10 insertions, 1 deletions
diff --git a/etc/NEWS b/etc/NEWS
index 2e50271d2dd..065d2d5b91d 100644
--- a/etc/NEWS
+++ b/etc/NEWS
@@ -995,7 +995,16 @@ coordinate in the POSITION list now counts from the top of the text
995area, excluding any header line. Previously, it counted from the top 995area, excluding any header line. Previously, it counted from the top
996of the header line. 996of the header line.
997 997
998** A backquote not followed by a space is now always treated as new-style. 998---
999** Support for "old-style" backquotes, which have been obsolete for
1000more than 10 years, has been further reduced. Now a backquote not
1001followed by a space is always treated as a "new-style" backquote.
1002Please consider completely removing all "old-style" backquotes from
1003your code as a matter of some urgency. If your code uses backquotes
1004as documented in the Elisp manual, and compiles without warning, then
1005you have nothing to do in this regard. Code not following the
1006appropriate conventions may fail to compile. The most common cause of
1007trouble seems to be an old-style backquote followed by a newline.
999 1008
1000--- 1009---
1001** view-buffer now treats special mode-class in the same way that 1010** view-buffer now treats special mode-class in the same way that