From 284c470ef752967fcd8bae6a450dc138462b1e49 Mon Sep 17 00:00:00 2001 From: Paul Eggert Date: Thu, 17 Sep 2015 16:08:20 -0700 Subject: Backslash cleanup in Elisp source files MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit This patch should not change behavior. It typically omits backslashes where they are redundant (e.g., in the string literal "^\$"). In a few places, insert backslashes where they make regular expressions clearer: e.g., replace "^\*" (equivalent to "^*") with "^\\*", which has the same effect as a regular expression. Also, use ‘\ %’ instead of ‘\%’ when avoiding confusion with SCCS IDs, and similarly use ‘\ $’ instead of ‘\$’ when avoiding confusion with RCS IDs, as that makes it clearer that the backslash is intended. --- lisp/files.el | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'lisp/files.el') diff --git a/lisp/files.el b/lisp/files.el index c309f86f85b..8565aa83266 100644 --- a/lisp/files.el +++ b/lisp/files.el @@ -1057,7 +1057,7 @@ Tip: You can use this expansion of remote identifier components to derive a new remote file name from an existing one. For example, if FILE is \"/sudo::/path/to/file\" then - \(concat \(file-remote-p FILE) \"/bin/sh\") + (concat (file-remote-p FILE) \"/bin/sh\") returns a remote file name for file \"/bin/sh\" that has the same remote identifier as FILE but expanded; a name such as @@ -3863,7 +3863,7 @@ directories." However, the mode will not be changed if \(1) a local variables list or the `-*-' line specifies a major mode, or \(2) the current major mode is a \"special\" mode, -\ not suitable for ordinary files, or + not suitable for ordinary files, or \(3) the new file name does not particularly specify any mode." :type 'boolean :group 'editing-basics) -- cgit v1.2.3