diff options
| author | Alan Mackenzie <acm@muc.de> | 2019-10-12 09:30:23 +0000 |
|---|---|---|
| committer | Alan Mackenzie <acm@muc.de> | 2019-10-12 09:30:23 +0000 |
| commit | 55fdbec44316036b85d96a4d808a5f1f17276fc6 (patch) | |
| tree | 4551d60f6ef739e487719f87c58c8398fadc18b5 /lisp/progmodes/cc-defs.el | |
| parent | 933c0bb96e7b157b551665dfd02141d1cd860771 (diff) | |
| download | emacs-55fdbec44316036b85d96a4d808a5f1f17276fc6.tar.gz | |
CC-Mode: Remove unneeded backslashes from doc strings and regular expressions
Also make miscellaneous amendments.
* lisp/progmodes/cc-align.el, lisp/progmodes/cc-cmds.el
* lisp/progmodes/cc-defs.el, lisp/progmodes/cc-engine.el
* lisp/progmodes/cc-langs.el, lisp/progmodes/cc-vars.el: Remove lots of
unneeded backslashes.
* lisp/progmodes/cc-langs.el (c-string-innards-re-alist): Remove redundant
"\\|\r" from regular expression.
* lisp/progmodes/cc-mode.el (c-make-mode-syntax-table): Correct the name of
the hook normal-erase-is-backspace-MODE-hook from a non-existant hook name.
Diffstat (limited to 'lisp/progmodes/cc-defs.el')
| -rw-r--r-- | lisp/progmodes/cc-defs.el | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/lisp/progmodes/cc-defs.el b/lisp/progmodes/cc-defs.el index 34f47debb16..e9a3e16db36 100644 --- a/lisp/progmodes/cc-defs.el +++ b/lisp/progmodes/cc-defs.el @@ -566,11 +566,11 @@ known to be writable. That way, these text properties remain set even if the user undoes the command which set them. This macro should ALWAYS be placed around \"temporary\" internal buffer -changes \(like adding a newline to calculate a text-property then +changes (like adding a newline to calculate a text-property then deleting it again), so that the user never sees them on his `buffer-undo-list'. See also `c-tentative-buffer-changes'. -However, any user-visible changes to the buffer \(like auto-newlines) +However, any user-visible changes to the buffer (like auto-newlines) must not be within a `c-save-buffer-state', since the user then wouldn't be able to undo them. @@ -597,7 +597,7 @@ was in before BODY. Any changes are kept if the last form in BODY returns non-nil. Otherwise it's undone using the undo facility, and various other buffer state that might be affected by the changes is restored. That includes the current buffer, point, mark, mark -activation \(similar to `save-excursion'), and the modified state. +activation (similar to `save-excursion'), and the modified state. The state is also restored if BODY exits nonlocally. If BODY makes a change that unconditionally is undone then wrap this @@ -2360,7 +2360,7 @@ VAL is not evaluated right away but rather when the value is requested with `c-lang-const'. Thus it's possible to use `c-lang-const' inside VAL to refer to language constants that haven't been defined yet. However, if the definition of a language constant is in another file -then that file must be loaded \(at compile time) before it's safe to +then that file must be loaded (at compile time) before it's safe to reference the constant. The assignments in ARGS are processed in sequence like `setq', so |