Backslash cleanup in Elisp source files

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.

1 files changed, 2 insertions, 2 deletions

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