@c This is part of the Emacs manual.
-@c Copyright (C) 1985, 86, 87, 93, 94, 95, 1997 Free Software Foundation, Inc.
+@c Copyright (C) 1985,86,87,93,94,95,1997,2001,2004 Free Software Foundation, Inc.
@c See file emacs.texi for copying conditions.
@iftex
@chapter Dealing with Common Problems
also considered.
@end iftex
+@ifnottex
+@raisesections
+@end ifnottex
+
@node Quitting, Lossage, Customization, Top
@section Quitting and Aborting
@cindex quitting
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
@section Dealing with Emacs Trouble
This section describes various conditions in which Emacs fails to work
-normally, and how to recognize them and correct them.
+normally, and how to recognize them and correct them. For a list of
+additional problems you might encounter, see @ref{Bugs and problems, ,
+Bugs and problems, efaq, GNU Emacs FAQ}, and the file @file{etc/PROBLEMS}
+in the Emacs distribution. Type @kbd{C-h C-f} to read the FAQ; type
+@kbd{C-h C-e} to read the @file{PROBLEMS} file.
@menu
-* DEL Gets Help:: What to do if @key{DEL} doesn't delete.
-* Stuck Recursive:: `[...]' in mode line around the parentheses.
-* Screen Garbled:: Garbage on the screen.
-* Text Garbled:: Garbage in the text.
-* Unasked-for Search:: Spontaneous entry to incremental search.
-* Memory Full:: How to cope when you run out of memory.
-* After a Crash:: Recovering editing in an Emacs session that crashed.
-* Emergency Escape:: Emergency escape---
- What to do if Emacs stops responding.
-* Total Frustration:: When you are at your wits' end.
+* DEL Does Not Delete:: What to do if @key{DEL} doesn't delete.
+* Stuck Recursive:: `[...]' in mode line around the parentheses.
+* Screen Garbled:: Garbage on the screen.
+* Text Garbled:: Garbage in the text.
+* Unasked-for Search:: Spontaneous entry to incremental search.
+* Memory Full:: How to cope when you run out of memory.
+* After a Crash:: Recovering editing in an Emacs session that crashed.
+* Emergency Escape:: Emergency escape---
+ What to do if Emacs stops responding.
+* Total Frustration:: When you are at your wits' end.
@end menu
-@node DEL Gets Help
+@node DEL Does Not Delete
@subsection If @key{DEL} Fails to Delete
@cindex @key{DEL} vs @key{BACKSPACE}
@cindex @key{BACKSPACE} vs @key{DEL}
@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
To make it possible for us to fix a bug, you must report it. In order
to do so effectively, you must know when and how to do it.
+ Before reporting a bug, it is a good idea to see if it is already
+known. You can find the list of known problems in the file
+@file{etc/PROBLEMS} in the Emacs distribution; type @kbd{C-h C-e} to read
+it. Some additional user-level problems can be found in @ref{Bugs and
+problems, , Bugs and problems, efaq, GNU Emacs FAQ}. Looking up your
+problem in these two documents might provide you with a solution or a
+work-around, or give you additional information about related issues.
+
@menu
* Criteria: Bug Criteria. Have you really found a bug?
* Understanding Bug Reporting:: How to report a bug effectively.
stimulates the bug.@refill
@item
-If non-ASCII text or internationalization is relevant, the locale that
+If non-@acronym{ASCII} text or internationalization is relevant, the locale that
was current when you started Emacs. On GNU/Linux and Unix systems, or
-if you use a Unix-style shell such as Bash, you can use this shell
+if you use a Posix-style shell such as Bash, you can use this shell
command to view the relevant values:
@smallexample
-echo LC_ALL=$LC_ALL LC_COLLATE=$LC_COLLATE LC_TYPE=$LC_TYPE \
+echo LC_ALL=$LC_ALL LC_COLLATE=$LC_COLLATE LC_CTYPE=$LC_CTYPE \
LC_MESSAGES=$LC_MESSAGES LC_TIME=$LC_TIME LANG=$LANG
@end smallexample
You can use the @kbd{M-!} command to execute these commands from
Emacs, and then copy the output from the @samp{*Messages*} buffer into
the bug report. Alternatively, @kbd{M-x getenv @key{RET} LC_ALL
-@key{RET}} will print the value of @code{LC_ALL} in the echo area, and
+@key{RET}} will display the value of @code{LC_ALL} in the echo area, and
you can copy its output from the @samp{*Messages*} buffer.
@item
@code{Fsignal}.
For a short listing of Lisp functions running, type the GDB
-command @code{xbacktrace}.
+command @code{xbacktrace}.
The file @file{.gdbinit} defines several other commands that are useful
for examining the data types and contents of Lisp objects. Their names
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.
-@node Service, Command Arguments, Contributing, Top
+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
If you need help installing, using or changing GNU Emacs, there are two
The service directory is found in the file named @file{etc/SERVICE} in the
Emacs distribution.
@end itemize
+
+@ifnottex
+@lowersections
+@end ifnottex
+
+@ignore
+ arch-tag: c9cba76d-b2cb-4e0c-ae3f-19d5ef35817c
+@end ignore