Skip to content
GitLab
Projects
Groups
Snippets
Help
Loading...
Help
Help
Support
Community forum
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
Open sidebar
emacs
emacs
Commits
faccede1
Commit
faccede1
authored
Feb 12, 2012
by
Chong Yidong
Browse files
* debugging.texi (Debugger Commands): Continuing is now allowed for errors.
parent
afd83bd1
Changes
4
Hide whitespace changes
Inline
Side-by-side
Showing
4 changed files
with
13 additions
and
12 deletions
+13
-12
admin/FOR-RELEASE
admin/FOR-RELEASE
+3
-3
doc/lispref/ChangeLog
doc/lispref/ChangeLog
+5
-0
doc/lispref/debugging.texi
doc/lispref/debugging.texi
+4
-8
lisp/dired.el
lisp/dired.el
+1
-1
No files found.
admin/FOR-RELEASE
View file @
faccede1
...
...
@@ -185,11 +185,11 @@ anti.texi
back.texi
backups.texi
buffers.texi
commands.texi
commands.texi
cyd
compile.texi cyd
control.texi cyd
customize.texi cyd
debugging.texi
debugging.texi
cyd
display.texi
edebug.texi
elisp.texi
...
...
@@ -222,7 +222,7 @@ positions.texi
processes.texi
searching.texi
sequences.texi cyd
streams.texi
streams.texi
cyd
strings.texi cyd
symbols.texi cyd
syntax.texi
...
...
doc/lispref/ChangeLog
View file @
faccede1
2012-02-12 Chong Yidong <cyd@gnu.org>
* debugging.texi (Debugger Commands): Continuing is now allowed
for errors.
2012-02-11 Chong Yidong <cyd@gnu.org>
* display.texi (Fringe Indicators): Add xref to Fringe Bitmaps.
...
...
doc/lispref/debugging.texi
View file @
faccede1
...
...
@@ -370,14 +370,10 @@ to step through a primitive function.
@table @kbd
@item c
Exit the debugger and continue execution. When continuing is possible,
it resumes execution of the program as if the debugger had never been
entered (aside from any side-effects that you caused by changing
variable values or data structures while inside the debugger).
Continuing is possible after entry to the debugger due to function entry
or exit, explicit invocation, or quitting. You cannot continue if the
debugger was entered because of an error.
Exit the debugger and continue execution. This resumes execution of
the program as if the debugger had never been entered (aside from any
side-effects that you caused by changing variable values or data
structures while inside the debugger).
@item d
Continue execution, but enter the debugger the next time any Lisp
...
...
lisp/dired.el
View file @
faccede1
...
...
@@ -4196,7 +4196,7 @@ instead.
;;;***
;;;### (autoloads (dired-do-relsymlink dired-jump-other-window dired-jump)
;;;;;; "
dired-x
" "
dired-x.el
" "
8d995933a8d82be3a8662d7eff7543cc
")
;;;;;; "
dired-x
" "
dired-x.el
" "
bc516591d881911d72b58eeed8816576
")
;;; Generated autoloads from dired-x.el
(autoload 'dired-jump "
dired-x
" "
\
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
.
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment