(After a Crash): Polish previous change.

This commit is contained in:
Richard M. Stallman 2005-06-04 10:18:46 +00:00
parent d4755e0491
commit 5cf98ab4b3

View file

@ -351,7 +351,6 @@ visits the file but gets the text from the auto-save file.
recover are present in Emacs buffers. You should then save them. Only
this---saving them---updates the files themselves.
As a last resort, if you had buffers with content which were not
associated with any files, or if the autosave was not recent enough to
have recorded important changes, you can use the
@ -360,16 +359,16 @@ retrieve them from a core dump--provided that a core dump was saved,
and that the Emacs executable was not stripped of its debugging
symbols.
To use this script, run @code{gdb} with the file name of your
Emacs executable and the file name of the core dump, e.g. @samp{gdb
To use this script, run @code{gdb} with the file name of your Emacs
executable and the file name of the core dump, e.g. @samp{gdb
/usr/bin/emacs core.emacs}. At the @code{(gdb)} prompt, load the
recovery script: @samp{source /usr/src/emacs/etc/emacs-buffer.gdb}.
You can now use the commands @code{ybuffer-list} and
@code{ysave-buffer} to list and save buffers. The @code{ysave-buffer}
command takes a buffer number (as listed by @code{ybuffer-list}) and a
file name to which to write the buffer contents. You should use a
file name which does not already exist; no backups of the previous
contents of the file will be saved, if any.
Then type the command @code{ybuffer-list} to see which buffers are
available. For each buffer, it lists a buffer number. To save a
buffer, use @code{ysave-buffer}; you specify the buffer number, and
the file name to write that buffer into. You should use a file name
which does not already exist; if the file does exist, the script does
not make make a backup of its old contents.
@node Emergency Escape
@subsection Emergency Escape