@table @kbd
@item C-g
-@itemx C-@key{BREAK} (MS-DOS)
-Quit. Cancel running or partially typed command.
+@itemx C-@key{BREAK}@r{ (MS-DOS only)}
+Quit (@code{keyboard-quit}): cancel running or partially typed command.
@item C-]
Abort innermost recursive editing level and cancel the command which
invoked it (@code{abort-recursive-edit}).
(@xref{Recursive Edit}.)
@cindex quitting
+@findex keyboard-quit
@kindex C-g
Quitting with @kbd{C-g} is used for getting rid of a partially typed
command, or a numeric argument that you don't want. It also stops a
@findex open-dribble-file
@cindex dribble file
+@cindex logging keystrokes
The easy way to record the input to Emacs precisely is to write a
dribble file. To start the file, execute the Lisp expression
@item
@findex open-termscript
@cindex termscript file
-@cindex @code{TERM} environment variable
+@cindex @env{TERM} environment variable
For possible display bugs, the terminal type (the value of environment
-variable @code{TERM}), the complete termcap entry for the terminal from
+variable @env{TERM}), the complete termcap entry for the terminal from
@file{/etc/termcap} (since that file is not identical on all machines),
and the output that Emacs actually sent to the terminal.
terminal-dependent bug without access to a terminal of the type that
stimulates the bug.@refill
+@item
+If non-ASCII text or internationalization is relevant, the locale that
+was current when you started Emacs. You can use this shell command to
+view the relevant values:
+
+@example
+echo LC_ALL=$LC_ALL LC_CTYPE=$LC_CTYPE LANG=$LANG
+@end example
+
+You can use the @kbd{M-!} command to execute the shell command from
+Emacs, and then copy the output from the @samp{*Messages*} buffer into
+the bug report.
+
@item
A description of what behavior you observe that you believe is
incorrect. For example, ``The Emacs process gets a fatal signal,'' or,
If the symptom of the bug is that Emacs fails to respond, don't assume
Emacs is ``hung''---it may instead be in an infinite loop. To find out
which, make the problem happen under GDB and stop Emacs once it is not
-responding. (If Emacs is using X Windows directly, you can stop Emacs
-by typing @kbd{C-z} at the GDB job.) Then try stepping with
-@samp{step}. If Emacs is hung, the @samp{step} command won't return.
-If it is looping, @samp{step} will return.
+responding. (If Emacs is using X directly, you can stop Emacs by typing
+@kbd{C-z} at the GDB job.) Then try stepping with @samp{step}. If
+Emacs is hung, the @samp{step} command won't return. If it is looping,
+@samp{step} will return.
If this shows Emacs is hung in a system call, stop it again and examine
the arguments of the call. In your bug report, state exactly where in
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 @code{bug-gnu-emacs@@gnu.org}. A pretester
+the maintainers at @email{bug-gnu-emacs@@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
-@code{bug-gnu-emacs@@gnu.org} before you start; it might be
+@email{bug-gnu-emacs@@gnu.org} before you start; it might be
possible to suggest ways to make your extension fit in better with the
rest of Emacs.
@itemize @bullet
@item
Send a message to the mailing list
-@code{help-gnu-emacs@@gnu.org}, or post your request on
+@email{help-gnu-emacs@@gnu.org}, or post your request on
newsgroup @code{gnu.emacs.help}. (This mailing list and newsgroup
interconnect, so it does not matter which one you use.)