|
From: | Paul Eggert |
Subject: | bug#23867: 25.1.50; Doc string containing `\N' |
Date: | Wed, 6 Jul 2016 16:56:57 +0200 |
User-agent: | Mozilla/5.0 (X11; Linux i686; rv:38.0) Gecko/20100101 Thunderbird/38.8.0 |
Is it too difficult for \N followed by anything other than { to be treated (possibly with a warning?) as before (ie, not as an escape)?
It could be done, but I'd rather not. lread.c doesn't warn about other stuff, by and large, and any warnings are likely to be ignored anyway. It would be additional complexity for very little benefit.
As a general rule Elisp code should not use \X unless \X is documented to be part of an escape sequence, or X is an ASCII punctuation character that might otherwise confuse Emacs. (By the way, are the punctuation characters still an issue? I've forgotten what their problem was or is.)
[Prev in Thread] | Current Thread | [Next in Thread] |