[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Emacs-diffs] Changes to emacs/man/entering.texi,v
From: |
Richard M. Stallman |
Subject: |
[Emacs-diffs] Changes to emacs/man/entering.texi,v |
Date: |
Tue, 02 Jan 2007 21:01:42 +0000 |
CVSROOT: /cvsroot/emacs
Module name: emacs
Changes by: Richard M. Stallman <rms> 07/01/02 21:01:42
Index: entering.texi
===================================================================
RCS file: /cvsroot/emacs/emacs/man/entering.texi,v
retrieving revision 1.18
retrieving revision 1.19
diff -u -b -r1.18 -r1.19
--- entering.texi 25 Aug 2006 21:08:35 -0000 1.18
+++ entering.texi 2 Jan 2007 21:01:42 -0000 1.19
@@ -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.
- [Emacs-diffs] Changes to emacs/man/entering.texi,v,
Richard M. Stallman <=