Mercurial > emacs

comparison man/entering.texi @ 75056:523d34e0b6b3

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
(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 b327bddebef6
children 4ad431d8e164
comparison
equal deleted inserted replaced
75055:e7558ed0caed 75056:523d34e0b6b3
37 Many editors are designed to edit one file. When done with that 37 Many editors are designed to edit one file. When done with that
38 file, you exit the editor. The next time you want to edit a file, you 38 file, you exit the editor. The next time you want to edit a file, you
39 must start the editor again. Working this way, it is convenient to 39 must start the editor again. Working this way, it is convenient to
40 use a command-line argument to say which file to edit. 40 use a command-line argument to say which file to edit.
41 41
42 It's not smart to start Emacs afresh for every file you edit. Emacs 42 However, killing Emacs after editing one each and starting it afresh
43 can visit more than one file in a single editing session, and upon 43 for the next file is both unnecessary and harmful, since it denies you
44 exit Emacs loses valuable accumulated context, such as the kill ring, 44 the full power of Emacs. Emacs can visit more than one file in a
45 registers, undo history, and mark ring. These features are useful for 45 single editing session, and that is the right way to use it. Exiting
46 operating on multiple files, or even one. If you kill Emacs after 46 the Emacs session loses valuable accumulated context, such as the kill
47 each file, you don't take advantage of them. 47 ring, registers, undo history, and mark ring. These features are
48 useful for operating on multiple files, or even continuing to edit one
49 file. If you kill Emacs after each file, you don't take advantage of
50 them.
48 51
49 The recommended way to use GNU Emacs is to start it only once, just 52 The recommended way to use GNU Emacs is to start it only once, just
50 after you log in, and do all your editing in the same Emacs session. 53 after you log in, and do all your editing in the same Emacs session.
51 Each time you edit a file, you visit it with the existing Emacs, which 54 Each time you edit a file, you visit it with the existing Emacs, which
52 eventually has many files in it ready for editing. Usually you do not 55 eventually has many files in it ready for editing. Usually you do not