mirror of
git://git.sv.gnu.org/emacs.git
synced 2025-12-17 11:20:39 -08:00
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.
This commit is contained in:
parent
d149ff5233
commit
284c470ef7
237 changed files with 916 additions and 914 deletions
|
|
@ -397,7 +397,7 @@ invoked interactively are excluded from this list."
|
|||
"Alist of functions and their call tree.
|
||||
Each element looks like
|
||||
|
||||
\(FUNCTION CALLERS CALLS\)
|
||||
(FUNCTION CALLERS CALLS)
|
||||
|
||||
where CALLERS is a list of functions that call FUNCTION, and CALLS
|
||||
is a list of functions for which calls were generated while compiling
|
||||
|
|
@ -4529,11 +4529,11 @@ whose definitions have been compiled in this Emacs session, as well as
|
|||
all functions called by those functions.
|
||||
|
||||
The call graph does not include macros, inline functions, or
|
||||
primitives that the byte-code interpreter knows about directly \(eq,
|
||||
cons, etc.\).
|
||||
primitives that the byte-code interpreter knows about directly
|
||||
\(`eq', `cons', etc.).
|
||||
|
||||
The call tree also lists those functions which are not known to be called
|
||||
\(that is, to which no calls have been compiled\), and which cannot be
|
||||
\(that is, to which no calls have been compiled), and which cannot be
|
||||
invoked interactively."
|
||||
(interactive)
|
||||
(message "Generating call tree...")
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue