procyberian/emacs
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Backslash cleanup in Elisp source files

Browse source 
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:
Paul Eggert 2015-09-17 16:08:20 -07:00
parent d149ff5233
commit 284c470ef7
237 changed files with 916 additions and 914 deletions
Download patch file Download diff file Expand all files Collapse all files

8
lisp/emacs-lisp/edebug.el
View file

@ -3162,12 +3162,12 @@ Do this when stopped before the form or it will be too late.
One side effect of using this command is that the next time the
function or macro is called, Edebug will be called there as well."
(interactive)
(if (not (looking-at "\("))
(if (not (looking-at "("))
(error "You must be before a list form")
(let ((func
(save-excursion
(down-list 1)
(if (looking-at "\(")
(if (looking-at "(")
(edebug--form-data-name
(edebug-get-form-data-entry (point)))
(read (current-buffer))))))
@ -3790,10 +3790,10 @@ Otherwise call `debug' normally."
(if t (progn
;; Delete interspersed edebug internals.
(while (re-search-forward "^ \(?edebug" nil t)
(while (re-search-forward "^ (?edebug" nil t)
(beginning-of-line)
(cond
((looking-at "^ \(edebug-after")
((looking-at "^ (edebug-after")
;; Previous lines may contain code, so just delete this line.
(setq last-ok-point (point))
(forward-line 1)