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/progmodes/prog-mode.el | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'lisp/progmodes/prog-mode.el') diff --git a/lisp/progmodes/prog-mode.el b/lisp/progmodes/prog-mode.el index 8f50887113e..f1aa35f2871 100644 --- a/lisp/progmodes/prog-mode.el +++ b/lisp/progmodes/prog-mode.el @@ -61,7 +61,7 @@ indentation of a line/region to the indentation engine of the sub mode, it is supposed to bind this variable to non-nil around the call. The non-nil value looks as follows - \(FIRST-COLUMN (START . END) PREVIOUS-CHUNKS) + (FIRST-COLUMN (START . END) PREVIOUS-CHUNKS) FIRST-COLUMN is the column the indentation engine of the sub mode should usually choose for top-level language constructs inside @@ -86,7 +86,7 @@ values are: - A function called with the start position of the current chunk. It will return either the region of the previous chunk - as \(PREV-START . PREV-END) or nil if there is no further + as (PREV-START . PREV-END) or nil if there is no further previous chunk. A typical use case are literate programming sources - the -- cgit v1.2.3