Mercurial > emacs
changeset 75056:523d34e0b6b3
(Entering Emacs): Clean up text about restarting Emacs for each file.
| author | Richard M. Stallman <rms@gnu.org> |
|---|---|
| date | Tue, 02 Jan 2007 21:01:42 +0000 |
| parents | e7558ed0caed |
| children | d6884873458d |
| files | man/entering.texi |
| diffstat | 1 files changed, 9 insertions(+), 6 deletions(-) [+] |
line wrap: on
line diff
--- a/man/entering.texi Tue Jan 02 21:01:08 2007 +0000 +++ b/man/entering.texi Tue Jan 02 21:01:42 2007 +0000 @@ -39,12 +39,15 @@ must start the editor again. Working this way, it is convenient to use a command-line argument to say which file to edit. - It's not smart to start Emacs afresh for every file you edit. Emacs -can visit more than one file in a single editing session, and upon -exit Emacs loses valuable accumulated context, such as the kill ring, -registers, undo history, and mark ring. These features are useful for -operating on multiple files, or even one. If you kill Emacs after -each file, you don't take advantage of them. + However, killing Emacs after editing one each and starting it afresh +for the next file is both unnecessary and harmful, since it denies you +the full power of Emacs. Emacs can visit more than one file in a +single editing session, and that is the right way to use it. Exiting +the Emacs session loses valuable accumulated context, such as the kill +ring, registers, undo history, and mark ring. These features are +useful for operating on multiple files, or even continuing to edit one +file. If you kill Emacs after each file, you don't take advantage of +them. The recommended way to use GNU Emacs is to start it only once, just after you log in, and do all your editing in the same Emacs session.