diff options
author | Paul Eggert <eggert@cs.ucla.edu> | 2015-09-17 16:08:20 -0700 |
---|---|---|
committer | Paul Eggert <eggert@cs.ucla.edu> | 2015-09-17 16:09:39 -0700 |
commit | 284c470ef752967fcd8bae6a450dc138462b1e49 (patch) | |
tree | 83e8bcfe4c756e741ee9d4ecdf80f6b8d0e73c91 /lisp/progmodes/cc-align.el | |
parent | d149ff5233805c0a09b6067e0cf27549291cc83a (diff) | |
download | emacs-284c470ef752967fcd8bae6a450dc138462b1e49.tar.gz |
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.
Diffstat (limited to 'lisp/progmodes/cc-align.el')
-rw-r--r-- | lisp/progmodes/cc-align.el | 16 |
1 files changed, 8 insertions, 8 deletions
diff --git a/lisp/progmodes/cc-align.el b/lisp/progmodes/cc-align.el index b0c4a6425bf..1e3cb8e16f9 100644 --- a/lisp/progmodes/cc-align.el +++ b/lisp/progmodes/cc-align.el @@ -1075,7 +1075,7 @@ Works with: brace-list-entry, brace-entry-open, statement, arglist-cont." (save-excursion (goto-char (c-langelem-pos langelem)) - (when (looking-at "\\s\(") + (when (looking-at "\\s(") (if (c-go-up-list-backward) (let ((pos (point))) (back-to-indentation) @@ -1093,24 +1093,24 @@ v beg of preceding constr v beg of preceding constr const char msg[] = if (!running) \"Some text.\"; error(\"Not running!\"); -#define X(A, B) \ #define X(A, B) \ -do { \ <-> do { \ <- c-lineup-cpp-define - printf (A, B); \ printf (A, B); \ +#define X(A, B) \\ #define X(A, B) \\ +do { \\ <-> do { \\ <- c-lineup-cpp-define + printf (A, B); \\ printf (A, B); \\ } while (0) } while (0) If `c-syntactic-indentation-in-macros' is non-nil, the function returns the relative indentation to the macro start line to allow accumulation with other offsets. E.g. in the following cases, cpp-define-intro is combined with the statement-block-intro that comes -from the \"do {\" that hangs on the \"#define\" line: +from the `do {' that hangs on the `#define' line: int dribble() { const char msg[] = if (!running) \"Some text.\"; error(\"Not running!\"); -#define X(A, B) do { \ #define X(A, B) do { \ - printf (A, B); \ <-> printf (A, B); \ <- c-lineup-cpp-define - this->refs++; \ this->refs++; \ +#define X(A, B) do { \\ #define X(A, B) do { \\ + printf (A, B); \\ <-> printf (A, B); \\ <- c-lineup-cpp-define + this->refs++; \\ this->refs++; \\ } while (0) <-> } while (0) <- c-lineup-cpp-define The relative indentation returned by `c-lineup-cpp-define' is zero and |