like @kbd{C-g}. The reason is that it is not feasible, on MS-DOS, to
recognize @kbd{C-g} while a command is running, between interactions
with the user. By contrast, it @emph{is} feasible to recognize
-@kbd{C-@key{BREAK}} at all times. @xref{MS-DOS Input}.
+@kbd{C-@key{BREAK}} at all times. @xref{MS-DOS Keyboard}.
@findex keyboard-quit
@kbd{C-g} works by setting the variable @code{quit-flag} to @code{t}
actually executed as a command if you type it while Emacs is waiting for
input. In that case, the command it runs is @code{keyboard-quit}.
- If you quit with @kbd{C-g} a second time before the first @kbd{C-g} is
-recognized, you activate the ``emergency escape'' feature and return to
-the shell. @xref{Emergency Escape}.
+ On a text terminal, if you quit with @kbd{C-g} a second time before
+the first @kbd{C-g} is recognized, you activate the ``emergency
+escape'' feature and return to the shell. @xref{Emergency Escape}.
@cindex NFS and quitting
There may be times when you cannot quit. When Emacs is waiting for
@node Screen Garbled
@subsection Garbage on the Screen
- If the data on the screen looks wrong, the first thing to do is see
-whether the text is really wrong. Type @kbd{C-l} to redisplay the
-entire screen. If the screen appears correct after this, the problem
-was entirely in the previous screen update. (Otherwise, see the following
-section.)
+ If the text on a text terminal looks wrong, the first thing to do is
+see whether it is wrong in the buffer. Type @kbd{C-l} to redisplay
+the entire screen. If the screen appears correct after this, the
+problem was entirely in the previous screen update. (Otherwise, see
+the following section.)
Display updating problems often result from an incorrect termcap entry
for the terminal you are using. The file @file{etc/TERMS} in the Emacs
If you would like to help pretest Emacs releases to assure they work
well, or if you would like to work on improving Emacs, please contact
-the maintainers at @email{bug-gnu-emacs@@gnu.org}. A pretester
+the maintainers at @email{emacs-devel@@gnu.org}. A pretester
should be prepared to investigate bugs as well as report them. If you'd
like to work on improving Emacs, please ask for suggested projects or
suggest your own ideas.
If you have already written an improvement, please tell us about it. If
you have not yet started work, it is useful to contact
-@email{bug-gnu-emacs@@gnu.org} before you start; it might be
+@email{emacs-devel@@gnu.org} before you start; it might be
possible to suggest ways to make your extension fit in better with the
rest of Emacs.
+The development version of Emacs can be downloaded from the CVS
+repository where it is actively maintained by a group of developers.
+See the Emacs project page http://savannah.gnu.org/projects/emacs/ for
+details.
+
@node Service, Copying, Contributing, Top
@section How To Get Help with GNU Emacs