annotate man/trouble.texi @ 66688:4f7af488adb0

(Mark Ring): Fix typo.
author Romain Francoise <romain@orebokech.com>
date Fri, 04 Nov 2005 07:37:36 +0000
parents 97aa71642e9c
children dc2d5a6655a3 7beb78bc1f8e
Ignore whitespace changes - Everywhere: Within whitespace: At end of lines:
rev   line source
25829
Dave Love <fx@gnu.org>
parents:
diff changeset
1 @c This is part of the Emacs manual.
64890
3723093a21fd Update years in copyright notice; nfc.
Thien-Thi Nguyen <ttn@gnuvola.org>
parents: 64464
diff changeset
2 @c Copyright (C) 1985, 1986, 1987, 1993, 1994, 1995, 1997, 2001, 2002,
3723093a21fd Update years in copyright notice; nfc.
Thien-Thi Nguyen <ttn@gnuvola.org>
parents: 64464
diff changeset
3 @c 2003, 2004, 2005 Free Software Foundation, Inc.
25829
Dave Love <fx@gnu.org>
parents:
diff changeset
4 @c See file emacs.texi for copying conditions.
Dave Love <fx@gnu.org>
parents:
diff changeset
5 @iftex
Dave Love <fx@gnu.org>
parents:
diff changeset
6 @chapter Dealing with Common Problems
Dave Love <fx@gnu.org>
parents:
diff changeset
7
Dave Love <fx@gnu.org>
parents:
diff changeset
8 If you type an Emacs command you did not intend, the results are often
Dave Love <fx@gnu.org>
parents:
diff changeset
9 mysterious. This chapter tells what you can do to cancel your mistake or
Dave Love <fx@gnu.org>
parents:
diff changeset
10 recover from a mysterious situation. Emacs bugs and system crashes are
Dave Love <fx@gnu.org>
parents:
diff changeset
11 also considered.
Dave Love <fx@gnu.org>
parents:
diff changeset
12 @end iftex
Dave Love <fx@gnu.org>
parents:
diff changeset
13
56812
16152de85a64 Adapt sectioning in Info to the node structure.
Luc Teirlinck <teirllm@auburn.edu>
parents: 54478
diff changeset
14 @ifnottex
16152de85a64 Adapt sectioning in Info to the node structure.
Luc Teirlinck <teirllm@auburn.edu>
parents: 54478
diff changeset
15 @raisesections
16152de85a64 Adapt sectioning in Info to the node structure.
Luc Teirlinck <teirllm@auburn.edu>
parents: 54478
diff changeset
16 @end ifnottex
16152de85a64 Adapt sectioning in Info to the node structure.
Luc Teirlinck <teirllm@auburn.edu>
parents: 54478
diff changeset
17
25829
Dave Love <fx@gnu.org>
parents:
diff changeset
18 @node Quitting, Lossage, Customization, Top
Dave Love <fx@gnu.org>
parents:
diff changeset
19 @section Quitting and Aborting
Dave Love <fx@gnu.org>
parents:
diff changeset
20 @cindex quitting
Dave Love <fx@gnu.org>
parents:
diff changeset
21
Dave Love <fx@gnu.org>
parents:
diff changeset
22 @table @kbd
Dave Love <fx@gnu.org>
parents:
diff changeset
23 @item C-g
36180
252e21b04fb1 Suggest copying problematical manual text into the bug report.
Richard M. Stallman <rms@gnu.org>
parents: 35874
diff changeset
24 @itemx C-@key{BREAK} @r{(MS-DOS only)}
252e21b04fb1 Suggest copying problematical manual text into the bug report.
Richard M. Stallman <rms@gnu.org>
parents: 35874
diff changeset
25 Quit: cancel running or partially typed command.
25829
Dave Love <fx@gnu.org>
parents:
diff changeset
26 @item C-]
Dave Love <fx@gnu.org>
parents:
diff changeset
27 Abort innermost recursive editing level and cancel the command which
Dave Love <fx@gnu.org>
parents:
diff changeset
28 invoked it (@code{abort-recursive-edit}).
Dave Love <fx@gnu.org>
parents:
diff changeset
29 @item @key{ESC} @key{ESC} @key{ESC}
Dave Love <fx@gnu.org>
parents:
diff changeset
30 Either quit or abort, whichever makes sense (@code{keyboard-escape-quit}).
Dave Love <fx@gnu.org>
parents:
diff changeset
31 @item M-x top-level
Dave Love <fx@gnu.org>
parents:
diff changeset
32 Abort all recursive editing levels that are currently executing.
Dave Love <fx@gnu.org>
parents:
diff changeset
33 @item C-x u
Dave Love <fx@gnu.org>
parents:
diff changeset
34 Cancel a previously made change in the buffer contents (@code{undo}).
Dave Love <fx@gnu.org>
parents:
diff changeset
35 @end table
Dave Love <fx@gnu.org>
parents:
diff changeset
36
Dave Love <fx@gnu.org>
parents:
diff changeset
37 There are two ways of canceling commands which are not finished
Dave Love <fx@gnu.org>
parents:
diff changeset
38 executing: @dfn{quitting} with @kbd{C-g}, and @dfn{aborting} with
Dave Love <fx@gnu.org>
parents:
diff changeset
39 @kbd{C-]} or @kbd{M-x top-level}. Quitting cancels a partially typed
Dave Love <fx@gnu.org>
parents:
diff changeset
40 command or one which is already running. Aborting exits a recursive
Dave Love <fx@gnu.org>
parents:
diff changeset
41 editing level and cancels the command that invoked the recursive edit.
Dave Love <fx@gnu.org>
parents:
diff changeset
42 (@xref{Recursive Edit}.)
Dave Love <fx@gnu.org>
parents:
diff changeset
43
Dave Love <fx@gnu.org>
parents:
diff changeset
44 @cindex quitting
Dave Love <fx@gnu.org>
parents:
diff changeset
45 @kindex C-g
Dave Love <fx@gnu.org>
parents:
diff changeset
46 Quitting with @kbd{C-g} is used for getting rid of a partially typed
Dave Love <fx@gnu.org>
parents:
diff changeset
47 command, or a numeric argument that you don't want. It also stops a
Dave Love <fx@gnu.org>
parents:
diff changeset
48 running command in the middle in a relatively safe way, so you can use
Dave Love <fx@gnu.org>
parents:
diff changeset
49 it if you accidentally give a command which takes a long time. In
Dave Love <fx@gnu.org>
parents:
diff changeset
50 particular, it is safe to quit out of killing; either your text will
Dave Love <fx@gnu.org>
parents:
diff changeset
51 @emph{all} still be in the buffer, or it will @emph{all} be in the kill
Dave Love <fx@gnu.org>
parents:
diff changeset
52 ring (or maybe both). Quitting an incremental search does special
Dave Love <fx@gnu.org>
parents:
diff changeset
53 things documented under searching; in general, it may take two
Dave Love <fx@gnu.org>
parents:
diff changeset
54 successive @kbd{C-g} characters to get out of a search
Dave Love <fx@gnu.org>
parents:
diff changeset
55 (@pxref{Incremental Search}).
Dave Love <fx@gnu.org>
parents:
diff changeset
56
Dave Love <fx@gnu.org>
parents:
diff changeset
57 On MS-DOS, the character @kbd{C-@key{BREAK}} serves as a quit character
Dave Love <fx@gnu.org>
parents:
diff changeset
58 like @kbd{C-g}. The reason is that it is not feasible, on MS-DOS, to
Dave Love <fx@gnu.org>
parents:
diff changeset
59 recognize @kbd{C-g} while a command is running, between interactions
Dave Love <fx@gnu.org>
parents:
diff changeset
60 with the user. By contrast, it @emph{is} feasible to recognize
60121
07602b55f1ef (Quitting): Update xref for splitting of node in msdog.texi.
Luc Teirlinck <teirllm@auburn.edu>
parents: 60115
diff changeset
61 @kbd{C-@key{BREAK}} at all times. @xref{MS-DOS Keyboard}.
25829
Dave Love <fx@gnu.org>
parents:
diff changeset
62
36180
252e21b04fb1 Suggest copying problematical manual text into the bug report.
Richard M. Stallman <rms@gnu.org>
parents: 35874
diff changeset
63 @findex keyboard-quit
25829
Dave Love <fx@gnu.org>
parents:
diff changeset
64 @kbd{C-g} works by setting the variable @code{quit-flag} to @code{t}
Dave Love <fx@gnu.org>
parents:
diff changeset
65 the instant @kbd{C-g} is typed; Emacs Lisp checks this variable
Dave Love <fx@gnu.org>
parents:
diff changeset
66 frequently and quits if it is non-@code{nil}. @kbd{C-g} is only
Dave Love <fx@gnu.org>
parents:
diff changeset
67 actually executed as a command if you type it while Emacs is waiting for
36180
252e21b04fb1 Suggest copying problematical manual text into the bug report.
Richard M. Stallman <rms@gnu.org>
parents: 35874
diff changeset
68 input. In that case, the command it runs is @code{keyboard-quit}.
25829
Dave Love <fx@gnu.org>
parents:
diff changeset
69
60115
63c8eb0c25c0 (Quitting): Emergency escape only for text terminal.
Richard M. Stallman <rms@gnu.org>
parents: 56812
diff changeset
70 On a text terminal, if you quit with @kbd{C-g} a second time before
63c8eb0c25c0 (Quitting): Emergency escape only for text terminal.
Richard M. Stallman <rms@gnu.org>
parents: 56812
diff changeset
71 the first @kbd{C-g} is recognized, you activate the ``emergency
63c8eb0c25c0 (Quitting): Emergency escape only for text terminal.
Richard M. Stallman <rms@gnu.org>
parents: 56812
diff changeset
72 escape'' feature and return to the shell. @xref{Emergency Escape}.
25829
Dave Love <fx@gnu.org>
parents:
diff changeset
73
Dave Love <fx@gnu.org>
parents:
diff changeset
74 @cindex NFS and quitting
Dave Love <fx@gnu.org>
parents:
diff changeset
75 There may be times when you cannot quit. When Emacs is waiting for
Dave Love <fx@gnu.org>
parents:
diff changeset
76 the operating system to do something, quitting is impossible unless
Dave Love <fx@gnu.org>
parents:
diff changeset
77 special pains are taken for the particular system call within Emacs
Dave Love <fx@gnu.org>
parents:
diff changeset
78 where the waiting occurs. We have done this for the system calls that
Dave Love <fx@gnu.org>
parents:
diff changeset
79 users are likely to want to quit from, but it's possible you will find
Dave Love <fx@gnu.org>
parents:
diff changeset
80 another. In one very common case---waiting for file input or output
37869
3f26bbf930e8 Minor fixes.
Richard M. Stallman <rms@gnu.org>
parents: 37580
diff changeset
81 using NFS---Emacs itself knows how to quit, but many NFS implementations
25829
Dave Love <fx@gnu.org>
parents:
diff changeset
82 simply do not allow user programs to stop waiting for NFS when the NFS
Dave Love <fx@gnu.org>
parents:
diff changeset
83 server is hung.
Dave Love <fx@gnu.org>
parents:
diff changeset
84
Dave Love <fx@gnu.org>
parents:
diff changeset
85 @cindex aborting recursive edit
Dave Love <fx@gnu.org>
parents:
diff changeset
86 @findex abort-recursive-edit
Dave Love <fx@gnu.org>
parents:
diff changeset
87 @kindex C-]
Dave Love <fx@gnu.org>
parents:
diff changeset
88 Aborting with @kbd{C-]} (@code{abort-recursive-edit}) is used to get
Dave Love <fx@gnu.org>
parents:
diff changeset
89 out of a recursive editing level and cancel the command which invoked
Dave Love <fx@gnu.org>
parents:
diff changeset
90 it. Quitting with @kbd{C-g} does not do this, and could not do this,
Dave Love <fx@gnu.org>
parents:
diff changeset
91 because it is used to cancel a partially typed command @emph{within} the
Dave Love <fx@gnu.org>
parents:
diff changeset
92 recursive editing level. Both operations are useful. For example, if
Dave Love <fx@gnu.org>
parents:
diff changeset
93 you are in a recursive edit and type @kbd{C-u 8} to enter a numeric
Dave Love <fx@gnu.org>
parents:
diff changeset
94 argument, you can cancel that argument with @kbd{C-g} and remain in the
Dave Love <fx@gnu.org>
parents:
diff changeset
95 recursive edit.
Dave Love <fx@gnu.org>
parents:
diff changeset
96
Dave Love <fx@gnu.org>
parents:
diff changeset
97 @findex keyboard-escape-quit
Dave Love <fx@gnu.org>
parents:
diff changeset
98 @kindex ESC ESC ESC
Dave Love <fx@gnu.org>
parents:
diff changeset
99 The command @kbd{@key{ESC} @key{ESC} @key{ESC}}
Dave Love <fx@gnu.org>
parents:
diff changeset
100 (@code{keyboard-escape-quit}) can either quit or abort. This key was
Dave Love <fx@gnu.org>
parents:
diff changeset
101 defined because @key{ESC} is used to ``get out'' in many PC programs.
Dave Love <fx@gnu.org>
parents:
diff changeset
102 It can cancel a prefix argument, clear a selected region, or get out of
Dave Love <fx@gnu.org>
parents:
diff changeset
103 a Query Replace, like @kbd{C-g}. It can get out of the minibuffer or a
Dave Love <fx@gnu.org>
parents:
diff changeset
104 recursive edit, like @kbd{C-]}. It can also get out of splitting the
Dave Love <fx@gnu.org>
parents:
diff changeset
105 frame into multiple windows, like @kbd{C-x 1}. One thing it cannot do,
Dave Love <fx@gnu.org>
parents:
diff changeset
106 however, is stop a command that is running. That's because it executes
Dave Love <fx@gnu.org>
parents:
diff changeset
107 as an ordinary command, and Emacs doesn't notice it until it is ready
Dave Love <fx@gnu.org>
parents:
diff changeset
108 for a command.
Dave Love <fx@gnu.org>
parents:
diff changeset
109
Dave Love <fx@gnu.org>
parents:
diff changeset
110 @findex top-level
Dave Love <fx@gnu.org>
parents:
diff changeset
111 The command @kbd{M-x top-level} is equivalent to ``enough'' @kbd{C-]}
Dave Love <fx@gnu.org>
parents:
diff changeset
112 commands to get you out of all the levels of recursive edits that you
Dave Love <fx@gnu.org>
parents:
diff changeset
113 are in. @kbd{C-]} gets you out one level at a time, but @kbd{M-x
Dave Love <fx@gnu.org>
parents:
diff changeset
114 top-level} goes out all levels at once. Both @kbd{C-]} and @kbd{M-x
Dave Love <fx@gnu.org>
parents:
diff changeset
115 top-level} are like all other commands, and unlike @kbd{C-g}, in that
Dave Love <fx@gnu.org>
parents:
diff changeset
116 they take effect only when Emacs is ready for a command. @kbd{C-]} is
Dave Love <fx@gnu.org>
parents:
diff changeset
117 an ordinary key and has its meaning only because of its binding in the
Dave Love <fx@gnu.org>
parents:
diff changeset
118 keymap. @xref{Recursive Edit}.
Dave Love <fx@gnu.org>
parents:
diff changeset
119
Dave Love <fx@gnu.org>
parents:
diff changeset
120 @kbd{C-x u} (@code{undo}) is not strictly speaking a way of canceling
Dave Love <fx@gnu.org>
parents:
diff changeset
121 a command, but you can think of it as canceling a command that already
37869
3f26bbf930e8 Minor fixes.
Richard M. Stallman <rms@gnu.org>
parents: 37580
diff changeset
122 finished executing. @xref{Undo}, for more information
3f26bbf930e8 Minor fixes.
Richard M. Stallman <rms@gnu.org>
parents: 37580
diff changeset
123 about the undo facility.
25829
Dave Love <fx@gnu.org>
parents:
diff changeset
124
Dave Love <fx@gnu.org>
parents:
diff changeset
125 @node Lossage, Bugs, Quitting, Top
Dave Love <fx@gnu.org>
parents:
diff changeset
126 @section Dealing with Emacs Trouble
Dave Love <fx@gnu.org>
parents:
diff changeset
127
Dave Love <fx@gnu.org>
parents:
diff changeset
128 This section describes various conditions in which Emacs fails to work
38686
0d3019db87ac (Lossage, Bugs): Mention etc/PROBLEMS and the Bugs section of the FAQ.
Eli Zaretskii <eliz@gnu.org>
parents: 38245
diff changeset
129 normally, and how to recognize them and correct them. For a list of
0d3019db87ac (Lossage, Bugs): Mention etc/PROBLEMS and the Bugs section of the FAQ.
Eli Zaretskii <eliz@gnu.org>
parents: 38245
diff changeset
130 additional problems you might encounter, see @ref{Bugs and problems, ,
0d3019db87ac (Lossage, Bugs): Mention etc/PROBLEMS and the Bugs section of the FAQ.
Eli Zaretskii <eliz@gnu.org>
parents: 38245
diff changeset
131 Bugs and problems, efaq, GNU Emacs FAQ}, and the file @file{etc/PROBLEMS}
54478
c0b7b601058f Fix help key bindings.
Juri Linkov <juri@jurta.org>
parents: 52979
diff changeset
132 in the Emacs distribution. Type @kbd{C-h C-f} to read the FAQ; type
c0b7b601058f Fix help key bindings.
Juri Linkov <juri@jurta.org>
parents: 52979
diff changeset
133 @kbd{C-h C-e} to read the @file{PROBLEMS} file.
25829
Dave Love <fx@gnu.org>
parents:
diff changeset
134
Dave Love <fx@gnu.org>
parents:
diff changeset
135 @menu
46235
3fade010f334 Fix indentation.
Richard M. Stallman <rms@gnu.org>
parents: 42117
diff changeset
136 * DEL Does Not Delete:: What to do if @key{DEL} doesn't delete.
38767
5889c45fd6ad Change the name of the "DEL Doesn't Delete" node to "DEL Does Not Delete",
Eli Zaretskii <eliz@gnu.org>
parents: 38742
diff changeset
137 * Stuck Recursive:: `[...]' in mode line around the parentheses.
5889c45fd6ad Change the name of the "DEL Doesn't Delete" node to "DEL Does Not Delete",
Eli Zaretskii <eliz@gnu.org>
parents: 38742
diff changeset
138 * Screen Garbled:: Garbage on the screen.
5889c45fd6ad Change the name of the "DEL Doesn't Delete" node to "DEL Does Not Delete",
Eli Zaretskii <eliz@gnu.org>
parents: 38742
diff changeset
139 * Text Garbled:: Garbage in the text.
5889c45fd6ad Change the name of the "DEL Doesn't Delete" node to "DEL Does Not Delete",
Eli Zaretskii <eliz@gnu.org>
parents: 38742
diff changeset
140 * Unasked-for Search:: Spontaneous entry to incremental search.
5889c45fd6ad Change the name of the "DEL Doesn't Delete" node to "DEL Does Not Delete",
Eli Zaretskii <eliz@gnu.org>
parents: 38742
diff changeset
141 * Memory Full:: How to cope when you run out of memory.
5889c45fd6ad Change the name of the "DEL Doesn't Delete" node to "DEL Does Not Delete",
Eli Zaretskii <eliz@gnu.org>
parents: 38742
diff changeset
142 * After a Crash:: Recovering editing in an Emacs session that crashed.
5889c45fd6ad Change the name of the "DEL Doesn't Delete" node to "DEL Does Not Delete",
Eli Zaretskii <eliz@gnu.org>
parents: 38742
diff changeset
143 * Emergency Escape:: Emergency escape---
5889c45fd6ad Change the name of the "DEL Doesn't Delete" node to "DEL Does Not Delete",
Eli Zaretskii <eliz@gnu.org>
parents: 38742
diff changeset
144 What to do if Emacs stops responding.
5889c45fd6ad Change the name of the "DEL Doesn't Delete" node to "DEL Does Not Delete",
Eli Zaretskii <eliz@gnu.org>
parents: 38742
diff changeset
145 * Total Frustration:: When you are at your wits' end.
25829
Dave Love <fx@gnu.org>
parents:
diff changeset
146 @end menu
Dave Love <fx@gnu.org>
parents:
diff changeset
147
38767
5889c45fd6ad Change the name of the "DEL Doesn't Delete" node to "DEL Does Not Delete",
Eli Zaretskii <eliz@gnu.org>
parents: 38742
diff changeset
148 @node DEL Does Not Delete
25829
Dave Love <fx@gnu.org>
parents:
diff changeset
149 @subsection If @key{DEL} Fails to Delete
36791
308577404dc3 DEL Gets Help: Complete rewrite to deal with automatic
Richard M. Stallman <rms@gnu.org>
parents: 36620
diff changeset
150 @cindex @key{DEL} vs @key{BACKSPACE}
308577404dc3 DEL Gets Help: Complete rewrite to deal with automatic
Richard M. Stallman <rms@gnu.org>
parents: 36620
diff changeset
151 @cindex @key{BACKSPACE} vs @key{DEL}
37126
6a2d75e45a87 Add concept of "usual erasure key" to explain about DEL.
Richard M. Stallman <rms@gnu.org>
parents: 37119
diff changeset
152 @cindex usual erasure key
25829
Dave Love <fx@gnu.org>
parents:
diff changeset
153
37126
6a2d75e45a87 Add concept of "usual erasure key" to explain about DEL.
Richard M. Stallman <rms@gnu.org>
parents: 37119
diff changeset
154 Every keyboard has a large key, a little ways above the @key{RET} or
6a2d75e45a87 Add concept of "usual erasure key" to explain about DEL.
Richard M. Stallman <rms@gnu.org>
parents: 37119
diff changeset
155 @key{ENTER} key, which you normally use outside Emacs to erase the
6a2d75e45a87 Add concept of "usual erasure key" to explain about DEL.
Richard M. Stallman <rms@gnu.org>
parents: 37119
diff changeset
156 last character that you typed. We call this key @dfn{the usual
37347
bd817d6f9ba3 Minor clarifications regarding DEL key.
Richard M. Stallman <rms@gnu.org>
parents: 37126
diff changeset
157 erasure key}. In Emacs, it is supposed to be equivalent to @key{DEL},
bd817d6f9ba3 Minor clarifications regarding DEL key.
Richard M. Stallman <rms@gnu.org>
parents: 37126
diff changeset
158 and when Emacs is properly configured for your terminal, it translates
bd817d6f9ba3 Minor clarifications regarding DEL key.
Richard M. Stallman <rms@gnu.org>
parents: 37126
diff changeset
159 that key into the character @key{DEL}.
36791
308577404dc3 DEL Gets Help: Complete rewrite to deal with automatic
Richard M. Stallman <rms@gnu.org>
parents: 36620
diff changeset
160
308577404dc3 DEL Gets Help: Complete rewrite to deal with automatic
Richard M. Stallman <rms@gnu.org>
parents: 36620
diff changeset
161 When Emacs starts up using a window system, it determines
308577404dc3 DEL Gets Help: Complete rewrite to deal with automatic
Richard M. Stallman <rms@gnu.org>
parents: 36620
diff changeset
162 automatically which key should be @key{DEL}. In some unusual cases
37126
6a2d75e45a87 Add concept of "usual erasure key" to explain about DEL.
Richard M. Stallman <rms@gnu.org>
parents: 37119
diff changeset
163 Emacs gets the wrong information from the system. If the usual
6a2d75e45a87 Add concept of "usual erasure key" to explain about DEL.
Richard M. Stallman <rms@gnu.org>
parents: 37119
diff changeset
164 erasure key deletes forwards instead of backwards, that is probably
6a2d75e45a87 Add concept of "usual erasure key" to explain about DEL.
Richard M. Stallman <rms@gnu.org>
parents: 37119
diff changeset
165 what happened---Emacs ought to be treating the @key{DELETE} key as
36791
308577404dc3 DEL Gets Help: Complete rewrite to deal with automatic
Richard M. Stallman <rms@gnu.org>
parents: 36620
diff changeset
166 @key{DEL}, but it isn't.
308577404dc3 DEL Gets Help: Complete rewrite to deal with automatic
Richard M. Stallman <rms@gnu.org>
parents: 36620
diff changeset
167
37126
6a2d75e45a87 Add concept of "usual erasure key" to explain about DEL.
Richard M. Stallman <rms@gnu.org>
parents: 37119
diff changeset
168 With a window system, if the usual erasure key is labeled
6a2d75e45a87 Add concept of "usual erasure key" to explain about DEL.
Richard M. Stallman <rms@gnu.org>
parents: 37119
diff changeset
169 @key{BACKSPACE} and there is a @key{DELETE} key elsewhere, but the
6a2d75e45a87 Add concept of "usual erasure key" to explain about DEL.
Richard M. Stallman <rms@gnu.org>
parents: 37119
diff changeset
170 @key{DELETE} key deletes backward instead of forward, that too
6a2d75e45a87 Add concept of "usual erasure key" to explain about DEL.
Richard M. Stallman <rms@gnu.org>
parents: 37119
diff changeset
171 suggests Emacs got the wrong information---but in the opposite sense.
37357
ad563f9185fb Minor clarifications of BACKSPACE vs DEL.
Richard M. Stallman <rms@gnu.org>
parents: 37347
diff changeset
172 It ought to be treating the @key{BACKSPACE} key as @key{DEL}, and
ad563f9185fb Minor clarifications of BACKSPACE vs DEL.
Richard M. Stallman <rms@gnu.org>
parents: 37347
diff changeset
173 treating @key{DELETE} differently, but it isn't.
36791
308577404dc3 DEL Gets Help: Complete rewrite to deal with automatic
Richard M. Stallman <rms@gnu.org>
parents: 36620
diff changeset
174
37126
6a2d75e45a87 Add concept of "usual erasure key" to explain about DEL.
Richard M. Stallman <rms@gnu.org>
parents: 37119
diff changeset
175 On a text-only terminal, if you find the usual erasure key prompts
6a2d75e45a87 Add concept of "usual erasure key" to explain about DEL.
Richard M. Stallman <rms@gnu.org>
parents: 37119
diff changeset
176 for a Help command, like @kbd{Control-h}, instead of deleting a
6a2d75e45a87 Add concept of "usual erasure key" to explain about DEL.
Richard M. Stallman <rms@gnu.org>
parents: 37119
diff changeset
177 character, it means that key is actually sending the @key{BS}
6a2d75e45a87 Add concept of "usual erasure key" to explain about DEL.
Richard M. Stallman <rms@gnu.org>
parents: 37119
diff changeset
178 character. Emacs ought to be treating @key{BS} as @key{DEL}, but it
6a2d75e45a87 Add concept of "usual erasure key" to explain about DEL.
Richard M. Stallman <rms@gnu.org>
parents: 37119
diff changeset
179 isn't.
36791
308577404dc3 DEL Gets Help: Complete rewrite to deal with automatic
Richard M. Stallman <rms@gnu.org>
parents: 36620
diff changeset
180
308577404dc3 DEL Gets Help: Complete rewrite to deal with automatic
Richard M. Stallman <rms@gnu.org>
parents: 36620
diff changeset
181 In all of those cases, the immediate remedy is the same: use the
37498
0b7a984464cf Clarify when C-? is available as Help.
Richard M. Stallman <rms@gnu.org>
parents: 37357
diff changeset
182 command @kbd{M-x normal-erase-is-backspace-mode}. This toggles
0b7a984464cf Clarify when C-? is available as Help.
Richard M. Stallman <rms@gnu.org>
parents: 37357
diff changeset
183 between the two modes that Emacs supports for handling @key{DEL}, so
0b7a984464cf Clarify when C-? is available as Help.
Richard M. Stallman <rms@gnu.org>
parents: 37357
diff changeset
184 if Emacs starts in the wrong mode, it should switch to the right mode.
0b7a984464cf Clarify when C-? is available as Help.
Richard M. Stallman <rms@gnu.org>
parents: 37357
diff changeset
185 On a text-only terminal, if you want to ask for help when @key{BS} is
0b7a984464cf Clarify when C-? is available as Help.
Richard M. Stallman <rms@gnu.org>
parents: 37357
diff changeset
186 treated as @key{DEL}, use @key{F1}; @kbd{C-?} may also work, if it
0b7a984464cf Clarify when C-? is available as Help.
Richard M. Stallman <rms@gnu.org>
parents: 37357
diff changeset
187 sends character code 127.
36791
308577404dc3 DEL Gets Help: Complete rewrite to deal with automatic
Richard M. Stallman <rms@gnu.org>
parents: 36620
diff changeset
188
308577404dc3 DEL Gets Help: Complete rewrite to deal with automatic
Richard M. Stallman <rms@gnu.org>
parents: 36620
diff changeset
189 @findex normal-erase-is-backspace-mode
308577404dc3 DEL Gets Help: Complete rewrite to deal with automatic
Richard M. Stallman <rms@gnu.org>
parents: 36620
diff changeset
190 To fix the problem automatically for every Emacs session, you can
308577404dc3 DEL Gets Help: Complete rewrite to deal with automatic
Richard M. Stallman <rms@gnu.org>
parents: 36620
diff changeset
191 put one of the following lines into your @file{.emacs} file
37357
ad563f9185fb Minor clarifications of BACKSPACE vs DEL.
Richard M. Stallman <rms@gnu.org>
parents: 37347
diff changeset
192 (@pxref{Init File}). For the first case above, where @key{DELETE}
ad563f9185fb Minor clarifications of BACKSPACE vs DEL.
Richard M. Stallman <rms@gnu.org>
parents: 37347
diff changeset
193 deletes forwards instead of backwards, use this line to make
37498
0b7a984464cf Clarify when C-? is available as Help.
Richard M. Stallman <rms@gnu.org>
parents: 37357
diff changeset
194 @key{DELETE} act as @key{DEL} (resulting in behavior compatible
0b7a984464cf Clarify when C-? is available as Help.
Richard M. Stallman <rms@gnu.org>
parents: 37357
diff changeset
195 with Emacs 20 and previous versions):
36791
308577404dc3 DEL Gets Help: Complete rewrite to deal with automatic
Richard M. Stallman <rms@gnu.org>
parents: 36620
diff changeset
196
308577404dc3 DEL Gets Help: Complete rewrite to deal with automatic
Richard M. Stallman <rms@gnu.org>
parents: 36620
diff changeset
197 @lisp
308577404dc3 DEL Gets Help: Complete rewrite to deal with automatic
Richard M. Stallman <rms@gnu.org>
parents: 36620
diff changeset
198 (normal-erase-is-backspace-mode 0)
308577404dc3 DEL Gets Help: Complete rewrite to deal with automatic
Richard M. Stallman <rms@gnu.org>
parents: 36620
diff changeset
199 @end lisp
308577404dc3 DEL Gets Help: Complete rewrite to deal with automatic
Richard M. Stallman <rms@gnu.org>
parents: 36620
diff changeset
200
308577404dc3 DEL Gets Help: Complete rewrite to deal with automatic
Richard M. Stallman <rms@gnu.org>
parents: 36620
diff changeset
201 @noindent
37357
ad563f9185fb Minor clarifications of BACKSPACE vs DEL.
Richard M. Stallman <rms@gnu.org>
parents: 37347
diff changeset
202 For the other two cases, where @key{BACKSPACE} ought to act as
ad563f9185fb Minor clarifications of BACKSPACE vs DEL.
Richard M. Stallman <rms@gnu.org>
parents: 37347
diff changeset
203 @key{DEL}, use this line:
36791
308577404dc3 DEL Gets Help: Complete rewrite to deal with automatic
Richard M. Stallman <rms@gnu.org>
parents: 36620
diff changeset
204
308577404dc3 DEL Gets Help: Complete rewrite to deal with automatic
Richard M. Stallman <rms@gnu.org>
parents: 36620
diff changeset
205 @lisp
308577404dc3 DEL Gets Help: Complete rewrite to deal with automatic
Richard M. Stallman <rms@gnu.org>
parents: 36620
diff changeset
206 (normal-erase-is-backspace-mode 1)
308577404dc3 DEL Gets Help: Complete rewrite to deal with automatic
Richard M. Stallman <rms@gnu.org>
parents: 36620
diff changeset
207 @end lisp
308577404dc3 DEL Gets Help: Complete rewrite to deal with automatic
Richard M. Stallman <rms@gnu.org>
parents: 36620
diff changeset
208
308577404dc3 DEL Gets Help: Complete rewrite to deal with automatic
Richard M. Stallman <rms@gnu.org>
parents: 36620
diff changeset
209 @vindex normal-erase-is-backspace
308577404dc3 DEL Gets Help: Complete rewrite to deal with automatic
Richard M. Stallman <rms@gnu.org>
parents: 36620
diff changeset
210 Another way to fix the problem for every Emacs session is to
308577404dc3 DEL Gets Help: Complete rewrite to deal with automatic
Richard M. Stallman <rms@gnu.org>
parents: 36620
diff changeset
211 customize the variable @code{normal-erase-is-backspace}: the value
308577404dc3 DEL Gets Help: Complete rewrite to deal with automatic
Richard M. Stallman <rms@gnu.org>
parents: 36620
diff changeset
212 @code{t} specifies the mode where @key{BS} or @key{BACKSPACE} is
308577404dc3 DEL Gets Help: Complete rewrite to deal with automatic
Richard M. Stallman <rms@gnu.org>
parents: 36620
diff changeset
213 @key{DEL}, and @code{nil} specifies the other mode. @xref{Easy
308577404dc3 DEL Gets Help: Complete rewrite to deal with automatic
Richard M. Stallman <rms@gnu.org>
parents: 36620
diff changeset
214 Customization}.
25829
Dave Love <fx@gnu.org>
parents:
diff changeset
215
37498
0b7a984464cf Clarify when C-? is available as Help.
Richard M. Stallman <rms@gnu.org>
parents: 37357
diff changeset
216 With a window system, it can also happen that the usual erasure key
0b7a984464cf Clarify when C-? is available as Help.
Richard M. Stallman <rms@gnu.org>
parents: 37357
diff changeset
217 is labeled @key{BACKSPACE}, there is a @key{DELETE} key elsewhere, and
0b7a984464cf Clarify when C-? is available as Help.
Richard M. Stallman <rms@gnu.org>
parents: 37357
diff changeset
218 both keys delete forward. This probably means that someone has
0b7a984464cf Clarify when C-? is available as Help.
Richard M. Stallman <rms@gnu.org>
parents: 37357
diff changeset
219 redefined your @key{BACKSPACE} key as a @key{DELETE} key. With X,
0b7a984464cf Clarify when C-? is available as Help.
Richard M. Stallman <rms@gnu.org>
parents: 37357
diff changeset
220 this is typically done with a command to the @code{xmodmap} program
0b7a984464cf Clarify when C-? is available as Help.
Richard M. Stallman <rms@gnu.org>
parents: 37357
diff changeset
221 when you start the server or log in. The most likely motive for this
0b7a984464cf Clarify when C-? is available as Help.
Richard M. Stallman <rms@gnu.org>
parents: 37357
diff changeset
222 customization was to support old versions of Emacs, so we recommend
0b7a984464cf Clarify when C-? is available as Help.
Richard M. Stallman <rms@gnu.org>
parents: 37357
diff changeset
223 you simply remove it now.
0b7a984464cf Clarify when C-? is available as Help.
Richard M. Stallman <rms@gnu.org>
parents: 37357
diff changeset
224
25829
Dave Love <fx@gnu.org>
parents:
diff changeset
225 @node Stuck Recursive
Dave Love <fx@gnu.org>
parents:
diff changeset
226 @subsection Recursive Editing Levels
Dave Love <fx@gnu.org>
parents:
diff changeset
227
Dave Love <fx@gnu.org>
parents:
diff changeset
228 Recursive editing levels are important and useful features of Emacs, but
Dave Love <fx@gnu.org>
parents:
diff changeset
229 they can seem like malfunctions to the user who does not understand them.
Dave Love <fx@gnu.org>
parents:
diff changeset
230
Dave Love <fx@gnu.org>
parents:
diff changeset
231 If the mode line has square brackets @samp{[@dots{}]} around the parentheses
Dave Love <fx@gnu.org>
parents:
diff changeset
232 that contain the names of the major and minor modes, you have entered a
Dave Love <fx@gnu.org>
parents:
diff changeset
233 recursive editing level. If you did not do this on purpose, or if you
Dave Love <fx@gnu.org>
parents:
diff changeset
234 don't understand what that means, you should just get out of the recursive
Dave Love <fx@gnu.org>
parents:
diff changeset
235 editing level. To do so, type @kbd{M-x top-level}. This is called getting
Dave Love <fx@gnu.org>
parents:
diff changeset
236 back to top level. @xref{Recursive Edit}.
Dave Love <fx@gnu.org>
parents:
diff changeset
237
Dave Love <fx@gnu.org>
parents:
diff changeset
238 @node Screen Garbled
Dave Love <fx@gnu.org>
parents:
diff changeset
239 @subsection Garbage on the Screen
Dave Love <fx@gnu.org>
parents:
diff changeset
240
60115
63c8eb0c25c0 (Quitting): Emergency escape only for text terminal.
Richard M. Stallman <rms@gnu.org>
parents: 56812
diff changeset
241 If the text on a text terminal looks wrong, the first thing to do is
63c8eb0c25c0 (Quitting): Emergency escape only for text terminal.
Richard M. Stallman <rms@gnu.org>
parents: 56812
diff changeset
242 see whether it is wrong in the buffer. Type @kbd{C-l} to redisplay
63c8eb0c25c0 (Quitting): Emergency escape only for text terminal.
Richard M. Stallman <rms@gnu.org>
parents: 56812
diff changeset
243 the entire screen. If the screen appears correct after this, the
63c8eb0c25c0 (Quitting): Emergency escape only for text terminal.
Richard M. Stallman <rms@gnu.org>
parents: 56812
diff changeset
244 problem was entirely in the previous screen update. (Otherwise, see
63c8eb0c25c0 (Quitting): Emergency escape only for text terminal.
Richard M. Stallman <rms@gnu.org>
parents: 56812
diff changeset
245 the following section.)
25829
Dave Love <fx@gnu.org>
parents:
diff changeset
246
Dave Love <fx@gnu.org>
parents:
diff changeset
247 Display updating problems often result from an incorrect termcap entry
Dave Love <fx@gnu.org>
parents:
diff changeset
248 for the terminal you are using. The file @file{etc/TERMS} in the Emacs
Dave Love <fx@gnu.org>
parents:
diff changeset
249 distribution gives the fixes for known problems of this sort.
Dave Love <fx@gnu.org>
parents:
diff changeset
250 @file{INSTALL} contains general advice for these problems in one of its
Dave Love <fx@gnu.org>
parents:
diff changeset
251 sections. Very likely there is simply insufficient padding for certain
Dave Love <fx@gnu.org>
parents:
diff changeset
252 display operations. To investigate the possibility that you have this sort
Dave Love <fx@gnu.org>
parents:
diff changeset
253 of problem, try Emacs on another terminal made by a different manufacturer.
Dave Love <fx@gnu.org>
parents:
diff changeset
254 If problems happen frequently on one kind of terminal but not another kind,
Dave Love <fx@gnu.org>
parents:
diff changeset
255 it is likely to be a bad termcap entry, though it could also be due to a
Dave Love <fx@gnu.org>
parents:
diff changeset
256 bug in Emacs that appears for terminals that have or that lack specific
Dave Love <fx@gnu.org>
parents:
diff changeset
257 features.
Dave Love <fx@gnu.org>
parents:
diff changeset
258
Dave Love <fx@gnu.org>
parents:
diff changeset
259 @node Text Garbled
Dave Love <fx@gnu.org>
parents:
diff changeset
260 @subsection Garbage in the Text
Dave Love <fx@gnu.org>
parents:
diff changeset
261
Dave Love <fx@gnu.org>
parents:
diff changeset
262 If @kbd{C-l} shows that the text is wrong, try undoing the changes to it
Dave Love <fx@gnu.org>
parents:
diff changeset
263 using @kbd{C-x u} until it gets back to a state you consider correct. Also
Dave Love <fx@gnu.org>
parents:
diff changeset
264 try @kbd{C-h l} to find out what command you typed to produce the observed
Dave Love <fx@gnu.org>
parents:
diff changeset
265 results.
Dave Love <fx@gnu.org>
parents:
diff changeset
266
Dave Love <fx@gnu.org>
parents:
diff changeset
267 If a large portion of text appears to be missing at the beginning or
Dave Love <fx@gnu.org>
parents:
diff changeset
268 end of the buffer, check for the word @samp{Narrow} in the mode line.
Dave Love <fx@gnu.org>
parents:
diff changeset
269 If it appears, the text you don't see is probably still present, but
Dave Love <fx@gnu.org>
parents:
diff changeset
270 temporarily off-limits. To make it accessible again, type @kbd{C-x n
Dave Love <fx@gnu.org>
parents:
diff changeset
271 w}. @xref{Narrowing}.
Dave Love <fx@gnu.org>
parents:
diff changeset
272
Dave Love <fx@gnu.org>
parents:
diff changeset
273 @node Unasked-for Search
Dave Love <fx@gnu.org>
parents:
diff changeset
274 @subsection Spontaneous Entry to Incremental Search
Dave Love <fx@gnu.org>
parents:
diff changeset
275
Dave Love <fx@gnu.org>
parents:
diff changeset
276 If Emacs spontaneously displays @samp{I-search:} at the bottom of the
Dave Love <fx@gnu.org>
parents:
diff changeset
277 screen, it means that the terminal is sending @kbd{C-s} and @kbd{C-q}
Dave Love <fx@gnu.org>
parents:
diff changeset
278 according to the poorly designed xon/xoff ``flow control'' protocol.
Dave Love <fx@gnu.org>
parents:
diff changeset
279
Dave Love <fx@gnu.org>
parents:
diff changeset
280 If this happens to you, your best recourse is to put the terminal in a
Dave Love <fx@gnu.org>
parents:
diff changeset
281 mode where it will not use flow control, or give it so much padding that
Dave Love <fx@gnu.org>
parents:
diff changeset
282 it will never send a @kbd{C-s}. (One way to increase the amount of
Dave Love <fx@gnu.org>
parents:
diff changeset
283 padding is to set the variable @code{baud-rate} to a larger value. Its
Dave Love <fx@gnu.org>
parents:
diff changeset
284 value is the terminal output speed, measured in the conventional units
Dave Love <fx@gnu.org>
parents:
diff changeset
285 of baud.)
Dave Love <fx@gnu.org>
parents:
diff changeset
286
Dave Love <fx@gnu.org>
parents:
diff changeset
287 @cindex flow control
Dave Love <fx@gnu.org>
parents:
diff changeset
288 @cindex xon-xoff
Dave Love <fx@gnu.org>
parents:
diff changeset
289 @findex enable-flow-control
Dave Love <fx@gnu.org>
parents:
diff changeset
290 If you don't succeed in turning off flow control, the next best thing
Dave Love <fx@gnu.org>
parents:
diff changeset
291 is to tell Emacs to cope with it. To do this, call the function
Dave Love <fx@gnu.org>
parents:
diff changeset
292 @code{enable-flow-control}.
Dave Love <fx@gnu.org>
parents:
diff changeset
293
Dave Love <fx@gnu.org>
parents:
diff changeset
294 @findex enable-flow-control-on
Dave Love <fx@gnu.org>
parents:
diff changeset
295 Typically there are particular terminal types with which you must use
Dave Love <fx@gnu.org>
parents:
diff changeset
296 flow control. You can conveniently ask for flow control on those
Dave Love <fx@gnu.org>
parents:
diff changeset
297 terminal types only, using @code{enable-flow-control-on}. For example,
Dave Love <fx@gnu.org>
parents:
diff changeset
298 if you find you must use flow control on VT-100 and H19 terminals, put
Dave Love <fx@gnu.org>
parents:
diff changeset
299 the following in your @file{.emacs} file:
Dave Love <fx@gnu.org>
parents:
diff changeset
300
Dave Love <fx@gnu.org>
parents:
diff changeset
301 @example
Dave Love <fx@gnu.org>
parents:
diff changeset
302 (enable-flow-control-on "vt100" "h19")
Dave Love <fx@gnu.org>
parents:
diff changeset
303 @end example
Dave Love <fx@gnu.org>
parents:
diff changeset
304
Dave Love <fx@gnu.org>
parents:
diff changeset
305 When flow control is enabled, you must type @kbd{C-\} to get the
Dave Love <fx@gnu.org>
parents:
diff changeset
306 effect of a @kbd{C-s}, and type @kbd{C-^} to get the effect of a
65034
1d51a8cd0280 (Unasked-for Search): Delete xref to Keyboard Translations.
Richard M. Stallman <rms@gnu.org>
parents: 64890
diff changeset
307 @kbd{C-q}.
25829
Dave Love <fx@gnu.org>
parents:
diff changeset
308
Dave Love <fx@gnu.org>
parents:
diff changeset
309 @node Memory Full
Dave Love <fx@gnu.org>
parents:
diff changeset
310 @subsection Running out of Memory
Dave Love <fx@gnu.org>
parents:
diff changeset
311 @cindex memory full
Dave Love <fx@gnu.org>
parents:
diff changeset
312 @cindex out of memory
Dave Love <fx@gnu.org>
parents:
diff changeset
313
66503
97aa71642e9c (Memory Full): Mention !MEM FULL! in mode line.
Richard M. Stallman <rms@gnu.org>
parents: 65034
diff changeset
314 If you get the error message @samp{Virtual memory exceeded}, save
97aa71642e9c (Memory Full): Mention !MEM FULL! in mode line.
Richard M. Stallman <rms@gnu.org>
parents: 65034
diff changeset
315 your modified buffers with @kbd{C-x s}. This method of saving them
97aa71642e9c (Memory Full): Mention !MEM FULL! in mode line.
Richard M. Stallman <rms@gnu.org>
parents: 65034
diff changeset
316 has the smallest need for additional memory. Emacs keeps a reserve of
97aa71642e9c (Memory Full): Mention !MEM FULL! in mode line.
Richard M. Stallman <rms@gnu.org>
parents: 65034
diff changeset
317 memory which it makes available when this error happens; that should
97aa71642e9c (Memory Full): Mention !MEM FULL! in mode line.
Richard M. Stallman <rms@gnu.org>
parents: 65034
diff changeset
318 be enough to enable @kbd{C-x s} to complete its work. When the
97aa71642e9c (Memory Full): Mention !MEM FULL! in mode line.
Richard M. Stallman <rms@gnu.org>
parents: 65034
diff changeset
319 reserve has been used, @samp{!MEM FULL!} appears at the beginning of
97aa71642e9c (Memory Full): Mention !MEM FULL! in mode line.
Richard M. Stallman <rms@gnu.org>
parents: 65034
diff changeset
320 the mode line, indicating there is no more reserve.
25829
Dave Love <fx@gnu.org>
parents:
diff changeset
321
66503
97aa71642e9c (Memory Full): Mention !MEM FULL! in mode line.
Richard M. Stallman <rms@gnu.org>
parents: 65034
diff changeset
322 Once you have saved your modified buffers, you can exit this Emacs
97aa71642e9c (Memory Full): Mention !MEM FULL! in mode line.
Richard M. Stallman <rms@gnu.org>
parents: 65034
diff changeset
323 session and start another, or you can use @kbd{M-x kill-some-buffers}
97aa71642e9c (Memory Full): Mention !MEM FULL! in mode line.
Richard M. Stallman <rms@gnu.org>
parents: 65034
diff changeset
324 to free space in the current Emacs job. If this frees up sufficient
97aa71642e9c (Memory Full): Mention !MEM FULL! in mode line.
Richard M. Stallman <rms@gnu.org>
parents: 65034
diff changeset
325 space, Emacs will refill its memory reserve, and @samp{!MEM FULL!}
97aa71642e9c (Memory Full): Mention !MEM FULL! in mode line.
Richard M. Stallman <rms@gnu.org>
parents: 65034
diff changeset
326 will disappear from the mode line. That means you can safely go on
97aa71642e9c (Memory Full): Mention !MEM FULL! in mode line.
Richard M. Stallman <rms@gnu.org>
parents: 65034
diff changeset
327 editing in the same Emacs session.
25829
Dave Love <fx@gnu.org>
parents:
diff changeset
328
Dave Love <fx@gnu.org>
parents:
diff changeset
329 Do not use @kbd{M-x buffer-menu} to save or kill buffers when you run
37976
23dc2eca0bd3 Proofreading changes from Tim Goodwin <tjg@star.le.ac.uk>.
Eli Zaretskii <eliz@gnu.org>
parents: 37869
diff changeset
330 out of memory, because the buffer menu needs a fair amount of memory
25829
Dave Love <fx@gnu.org>
parents:
diff changeset
331 itself, and the reserve supply may not be enough.
Dave Love <fx@gnu.org>
parents:
diff changeset
332
Dave Love <fx@gnu.org>
parents:
diff changeset
333 @node After a Crash
Dave Love <fx@gnu.org>
parents:
diff changeset
334 @subsection Recovery After a Crash
Dave Love <fx@gnu.org>
parents:
diff changeset
335
Dave Love <fx@gnu.org>
parents:
diff changeset
336 If Emacs or the computer crashes, you can recover the files you were
Dave Love <fx@gnu.org>
parents:
diff changeset
337 editing at the time of the crash from their auto-save files. To do
Dave Love <fx@gnu.org>
parents:
diff changeset
338 this, start Emacs again and type the command @kbd{M-x recover-session}.
Dave Love <fx@gnu.org>
parents:
diff changeset
339
Dave Love <fx@gnu.org>
parents:
diff changeset
340 This command initially displays a buffer which lists interrupted
Dave Love <fx@gnu.org>
parents:
diff changeset
341 session files, each with its date. You must choose which session to
Dave Love <fx@gnu.org>
parents:
diff changeset
342 recover from. Typically the one you want is the most recent one. Move
Dave Love <fx@gnu.org>
parents:
diff changeset
343 point to the one you choose, and type @kbd{C-c C-c}.
Dave Love <fx@gnu.org>
parents:
diff changeset
344
Dave Love <fx@gnu.org>
parents:
diff changeset
345 Then @code{recover-session} asks about each of the files that you were
Dave Love <fx@gnu.org>
parents:
diff changeset
346 editing during that session; it asks whether to recover that file. If
Dave Love <fx@gnu.org>
parents:
diff changeset
347 you answer @kbd{y} for a file, it shows the dates of that file and its
Dave Love <fx@gnu.org>
parents:
diff changeset
348 auto-save file, then asks once again whether to recover that file. For
Dave Love <fx@gnu.org>
parents:
diff changeset
349 the second question, you must confirm with @kbd{yes}. If you do, Emacs
Dave Love <fx@gnu.org>
parents:
diff changeset
350 visits the file but gets the text from the auto-save file.
Dave Love <fx@gnu.org>
parents:
diff changeset
351
Dave Love <fx@gnu.org>
parents:
diff changeset
352 When @code{recover-session} is done, the files you've chosen to
Dave Love <fx@gnu.org>
parents:
diff changeset
353 recover are present in Emacs buffers. You should then save them. Only
Dave Love <fx@gnu.org>
parents:
diff changeset
354 this---saving them---updates the files themselves.
Dave Love <fx@gnu.org>
parents:
diff changeset
355
62897
6181dbed8947 (After a Crash): Mention emacs-buffer.gdb as a recovery mechanism.
Noah Friedman <friedman@splode.com>
parents: 60342
diff changeset
356 As a last resort, if you had buffers with content which were not
6181dbed8947 (After a Crash): Mention emacs-buffer.gdb as a recovery mechanism.
Noah Friedman <friedman@splode.com>
parents: 60342
diff changeset
357 associated with any files, or if the autosave was not recent enough to
6181dbed8947 (After a Crash): Mention emacs-buffer.gdb as a recovery mechanism.
Noah Friedman <friedman@splode.com>
parents: 60342
diff changeset
358 have recorded important changes, you can use the
62899
1a33c4dbb62b (After a Crash): Describe how to use emacs-buffer.gdb more explicitly.
Noah Friedman <friedman@splode.com>
parents: 62897
diff changeset
359 @file{etc/emacs-buffer.gdb} script with GDB (the GNU Debugger) to
1a33c4dbb62b (After a Crash): Describe how to use emacs-buffer.gdb more explicitly.
Noah Friedman <friedman@splode.com>
parents: 62897
diff changeset
360 retrieve them from a core dump--provided that a core dump was saved,
1a33c4dbb62b (After a Crash): Describe how to use emacs-buffer.gdb more explicitly.
Noah Friedman <friedman@splode.com>
parents: 62897
diff changeset
361 and that the Emacs executable was not stripped of its debugging
1a33c4dbb62b (After a Crash): Describe how to use emacs-buffer.gdb more explicitly.
Noah Friedman <friedman@splode.com>
parents: 62897
diff changeset
362 symbols.
1a33c4dbb62b (After a Crash): Describe how to use emacs-buffer.gdb more explicitly.
Noah Friedman <friedman@splode.com>
parents: 62897
diff changeset
363
62991
b9a3bc12a80f (After a Crash): Polish previous change.
Richard M. Stallman <rms@gnu.org>
parents: 62899
diff changeset
364 To use this script, run @code{gdb} with the file name of your Emacs
b9a3bc12a80f (After a Crash): Polish previous change.
Richard M. Stallman <rms@gnu.org>
parents: 62899
diff changeset
365 executable and the file name of the core dump, e.g. @samp{gdb
62899
1a33c4dbb62b (After a Crash): Describe how to use emacs-buffer.gdb more explicitly.
Noah Friedman <friedman@splode.com>
parents: 62897
diff changeset
366 /usr/bin/emacs core.emacs}. At the @code{(gdb)} prompt, load the
1a33c4dbb62b (After a Crash): Describe how to use emacs-buffer.gdb more explicitly.
Noah Friedman <friedman@splode.com>
parents: 62897
diff changeset
367 recovery script: @samp{source /usr/src/emacs/etc/emacs-buffer.gdb}.
62991
b9a3bc12a80f (After a Crash): Polish previous change.
Richard M. Stallman <rms@gnu.org>
parents: 62899
diff changeset
368 Then type the command @code{ybuffer-list} to see which buffers are
b9a3bc12a80f (After a Crash): Polish previous change.
Richard M. Stallman <rms@gnu.org>
parents: 62899
diff changeset
369 available. For each buffer, it lists a buffer number. To save a
b9a3bc12a80f (After a Crash): Polish previous change.
Richard M. Stallman <rms@gnu.org>
parents: 62899
diff changeset
370 buffer, use @code{ysave-buffer}; you specify the buffer number, and
b9a3bc12a80f (After a Crash): Polish previous change.
Richard M. Stallman <rms@gnu.org>
parents: 62899
diff changeset
371 the file name to write that buffer into. You should use a file name
b9a3bc12a80f (After a Crash): Polish previous change.
Richard M. Stallman <rms@gnu.org>
parents: 62899
diff changeset
372 which does not already exist; if the file does exist, the script does
64464
a40344cc40b0 (After a Crash): Delete duplicate words.
Juri Linkov <juri@jurta.org>
parents: 64083
diff changeset
373 not make a backup of its old contents.
62897
6181dbed8947 (After a Crash): Mention emacs-buffer.gdb as a recovery mechanism.
Noah Friedman <friedman@splode.com>
parents: 60342
diff changeset
374
25829
Dave Love <fx@gnu.org>
parents:
diff changeset
375 @node Emergency Escape
Dave Love <fx@gnu.org>
parents:
diff changeset
376 @subsection Emergency Escape
Dave Love <fx@gnu.org>
parents:
diff changeset
377
Dave Love <fx@gnu.org>
parents:
diff changeset
378 Because at times there have been bugs causing Emacs to loop without
Dave Love <fx@gnu.org>
parents:
diff changeset
379 checking @code{quit-flag}, a special feature causes Emacs to be suspended
Dave Love <fx@gnu.org>
parents:
diff changeset
380 immediately if you type a second @kbd{C-g} while the flag is already set,
Dave Love <fx@gnu.org>
parents:
diff changeset
381 so you can always get out of GNU Emacs. Normally Emacs recognizes and
Dave Love <fx@gnu.org>
parents:
diff changeset
382 clears @code{quit-flag} (and quits!) quickly enough to prevent this from
Dave Love <fx@gnu.org>
parents:
diff changeset
383 happening. (On MS-DOS and compatible systems, type @kbd{C-@key{BREAK}}
Dave Love <fx@gnu.org>
parents:
diff changeset
384 twice.)
Dave Love <fx@gnu.org>
parents:
diff changeset
385
Dave Love <fx@gnu.org>
parents:
diff changeset
386 When you resume Emacs after a suspension caused by multiple @kbd{C-g}, it
Dave Love <fx@gnu.org>
parents:
diff changeset
387 asks two questions before going back to what it had been doing:
Dave Love <fx@gnu.org>
parents:
diff changeset
388
Dave Love <fx@gnu.org>
parents:
diff changeset
389 @example
Dave Love <fx@gnu.org>
parents:
diff changeset
390 Auto-save? (y or n)
Dave Love <fx@gnu.org>
parents:
diff changeset
391 Abort (and dump core)? (y or n)
Dave Love <fx@gnu.org>
parents:
diff changeset
392 @end example
Dave Love <fx@gnu.org>
parents:
diff changeset
393
Dave Love <fx@gnu.org>
parents:
diff changeset
394 @noindent
Dave Love <fx@gnu.org>
parents:
diff changeset
395 Answer each one with @kbd{y} or @kbd{n} followed by @key{RET}.
Dave Love <fx@gnu.org>
parents:
diff changeset
396
Dave Love <fx@gnu.org>
parents:
diff changeset
397 Saying @kbd{y} to @samp{Auto-save?} causes immediate auto-saving of all
Dave Love <fx@gnu.org>
parents:
diff changeset
398 modified buffers in which auto-saving is enabled.
Dave Love <fx@gnu.org>
parents:
diff changeset
399
Dave Love <fx@gnu.org>
parents:
diff changeset
400 Saying @kbd{y} to @samp{Abort (and dump core)?} causes an illegal instruction to be
Dave Love <fx@gnu.org>
parents:
diff changeset
401 executed, dumping core. This is to enable a wizard to figure out why Emacs
Dave Love <fx@gnu.org>
parents:
diff changeset
402 was failing to quit in the first place. Execution does not continue
Dave Love <fx@gnu.org>
parents:
diff changeset
403 after a core dump. If you answer @kbd{n}, execution does continue. With
Dave Love <fx@gnu.org>
parents:
diff changeset
404 luck, GNU Emacs will ultimately check @code{quit-flag} and quit normally.
Dave Love <fx@gnu.org>
parents:
diff changeset
405 If not, and you type another @kbd{C-g}, it is suspended again.
Dave Love <fx@gnu.org>
parents:
diff changeset
406
Dave Love <fx@gnu.org>
parents:
diff changeset
407 If Emacs is not really hung, just slow, you may invoke the double
Dave Love <fx@gnu.org>
parents:
diff changeset
408 @kbd{C-g} feature without really meaning to. Then just resume and answer
Dave Love <fx@gnu.org>
parents:
diff changeset
409 @kbd{n} to both questions, and you will arrive at your former state.
Dave Love <fx@gnu.org>
parents:
diff changeset
410 Presumably the quit you requested will happen soon.
Dave Love <fx@gnu.org>
parents:
diff changeset
411
37869
3f26bbf930e8 Minor fixes.
Richard M. Stallman <rms@gnu.org>
parents: 37580
diff changeset
412 The double @kbd{C-g} feature is turned off when Emacs is running under
25829
Dave Love <fx@gnu.org>
parents:
diff changeset
413 the X Window System, since you can use the window manager to kill Emacs
Dave Love <fx@gnu.org>
parents:
diff changeset
414 or to create another window and run another program.
Dave Love <fx@gnu.org>
parents:
diff changeset
415
Dave Love <fx@gnu.org>
parents:
diff changeset
416 On MS-DOS and compatible systems, the emergency escape feature is
Dave Love <fx@gnu.org>
parents:
diff changeset
417 sometimes unavailable, even if you press @kbd{C-@key{BREAK}} twice, when
Dave Love <fx@gnu.org>
parents:
diff changeset
418 some system call (MS-DOS or BIOS) hangs, or when Emacs is stuck in a
Dave Love <fx@gnu.org>
parents:
diff changeset
419 very tight endless loop (in C code, @strong{not} in Lisp code).
Dave Love <fx@gnu.org>
parents:
diff changeset
420
Dave Love <fx@gnu.org>
parents:
diff changeset
421 @node Total Frustration
Dave Love <fx@gnu.org>
parents:
diff changeset
422 @subsection Help for Total Frustration
Dave Love <fx@gnu.org>
parents:
diff changeset
423 @cindex Eliza
Dave Love <fx@gnu.org>
parents:
diff changeset
424 @cindex doctor
Dave Love <fx@gnu.org>
parents:
diff changeset
425
Dave Love <fx@gnu.org>
parents:
diff changeset
426 If using Emacs (or something else) becomes terribly frustrating and none
Dave Love <fx@gnu.org>
parents:
diff changeset
427 of the techniques described above solve the problem, Emacs can still help
Dave Love <fx@gnu.org>
parents:
diff changeset
428 you.
Dave Love <fx@gnu.org>
parents:
diff changeset
429
Dave Love <fx@gnu.org>
parents:
diff changeset
430 First, if the Emacs you are using is not responding to commands, type
Dave Love <fx@gnu.org>
parents:
diff changeset
431 @kbd{C-g C-g} to get out of it and then start a new one.
Dave Love <fx@gnu.org>
parents:
diff changeset
432
Dave Love <fx@gnu.org>
parents:
diff changeset
433 @findex doctor
Dave Love <fx@gnu.org>
parents:
diff changeset
434 Second, type @kbd{M-x doctor @key{RET}}.
Dave Love <fx@gnu.org>
parents:
diff changeset
435
Dave Love <fx@gnu.org>
parents:
diff changeset
436 The doctor will help you feel better. Each time you say something to
Dave Love <fx@gnu.org>
parents:
diff changeset
437 the doctor, you must end it by typing @key{RET} @key{RET}. This lets
Dave Love <fx@gnu.org>
parents:
diff changeset
438 the doctor know you are finished.
Dave Love <fx@gnu.org>
parents:
diff changeset
439
Dave Love <fx@gnu.org>
parents:
diff changeset
440 @node Bugs, Contributing, Lossage, Top
Dave Love <fx@gnu.org>
parents:
diff changeset
441 @section Reporting Bugs
Dave Love <fx@gnu.org>
parents:
diff changeset
442
Dave Love <fx@gnu.org>
parents:
diff changeset
443 @cindex bugs
Dave Love <fx@gnu.org>
parents:
diff changeset
444 Sometimes you will encounter a bug in Emacs. Although we cannot
Dave Love <fx@gnu.org>
parents:
diff changeset
445 promise we can or will fix the bug, and we might not even agree that it
Dave Love <fx@gnu.org>
parents:
diff changeset
446 is a bug, we want to hear about problems you encounter. Often we agree
Dave Love <fx@gnu.org>
parents:
diff changeset
447 they are bugs and want to fix them.
Dave Love <fx@gnu.org>
parents:
diff changeset
448
Dave Love <fx@gnu.org>
parents:
diff changeset
449 To make it possible for us to fix a bug, you must report it. In order
Dave Love <fx@gnu.org>
parents:
diff changeset
450 to do so effectively, you must know when and how to do it.
Dave Love <fx@gnu.org>
parents:
diff changeset
451
38686
0d3019db87ac (Lossage, Bugs): Mention etc/PROBLEMS and the Bugs section of the FAQ.
Eli Zaretskii <eliz@gnu.org>
parents: 38245
diff changeset
452 Before reporting a bug, it is a good idea to see if it is already
0d3019db87ac (Lossage, Bugs): Mention etc/PROBLEMS and the Bugs section of the FAQ.
Eli Zaretskii <eliz@gnu.org>
parents: 38245
diff changeset
453 known. You can find the list of known problems in the file
54478
c0b7b601058f Fix help key bindings.
Juri Linkov <juri@jurta.org>
parents: 52979
diff changeset
454 @file{etc/PROBLEMS} in the Emacs distribution; type @kbd{C-h C-e} to read
38691
5c9ec2d0b570 (Lossage, Bugs): Mention the keys which display PROBLEMS and FAQ.
Eli Zaretskii <eliz@gnu.org>
parents: 38686
diff changeset
455 it. Some additional user-level problems can be found in @ref{Bugs and
5c9ec2d0b570 (Lossage, Bugs): Mention the keys which display PROBLEMS and FAQ.
Eli Zaretskii <eliz@gnu.org>
parents: 38686
diff changeset
456 problems, , Bugs and problems, efaq, GNU Emacs FAQ}. Looking up your
5c9ec2d0b570 (Lossage, Bugs): Mention the keys which display PROBLEMS and FAQ.
Eli Zaretskii <eliz@gnu.org>
parents: 38686
diff changeset
457 problem in these two documents might provide you with a solution or a
5c9ec2d0b570 (Lossage, Bugs): Mention the keys which display PROBLEMS and FAQ.
Eli Zaretskii <eliz@gnu.org>
parents: 38686
diff changeset
458 work-around, or give you additional information about related issues.
38686
0d3019db87ac (Lossage, Bugs): Mention etc/PROBLEMS and the Bugs section of the FAQ.
Eli Zaretskii <eliz@gnu.org>
parents: 38245
diff changeset
459
25829
Dave Love <fx@gnu.org>
parents:
diff changeset
460 @menu
Dave Love <fx@gnu.org>
parents:
diff changeset
461 * Criteria: Bug Criteria. Have you really found a bug?
Dave Love <fx@gnu.org>
parents:
diff changeset
462 * Understanding Bug Reporting:: How to report a bug effectively.
Dave Love <fx@gnu.org>
parents:
diff changeset
463 * Checklist:: Steps to follow for a good bug report.
Dave Love <fx@gnu.org>
parents:
diff changeset
464 * Sending Patches:: How to send a patch for GNU Emacs.
Dave Love <fx@gnu.org>
parents:
diff changeset
465 @end menu
Dave Love <fx@gnu.org>
parents:
diff changeset
466
Dave Love <fx@gnu.org>
parents:
diff changeset
467 @node Bug Criteria
Dave Love <fx@gnu.org>
parents:
diff changeset
468 @subsection When Is There a Bug
Dave Love <fx@gnu.org>
parents:
diff changeset
469
Dave Love <fx@gnu.org>
parents:
diff changeset
470 If Emacs executes an illegal instruction, or dies with an operating
Dave Love <fx@gnu.org>
parents:
diff changeset
471 system error message that indicates a problem in the program (as opposed to
Dave Love <fx@gnu.org>
parents:
diff changeset
472 something like ``disk full''), then it is certainly a bug.
Dave Love <fx@gnu.org>
parents:
diff changeset
473
Dave Love <fx@gnu.org>
parents:
diff changeset
474 If Emacs updates the display in a way that does not correspond to what is
Dave Love <fx@gnu.org>
parents:
diff changeset
475 in the buffer, then it is certainly a bug. If a command seems to do the
Dave Love <fx@gnu.org>
parents:
diff changeset
476 wrong thing but the problem corrects itself if you type @kbd{C-l}, it is a
Dave Love <fx@gnu.org>
parents:
diff changeset
477 case of incorrect display updating.
Dave Love <fx@gnu.org>
parents:
diff changeset
478
Dave Love <fx@gnu.org>
parents:
diff changeset
479 Taking forever to complete a command can be a bug, but you must make
Dave Love <fx@gnu.org>
parents:
diff changeset
480 certain that it was really Emacs's fault. Some commands simply take a
Dave Love <fx@gnu.org>
parents:
diff changeset
481 long time. Type @kbd{C-g} (@kbd{C-@key{BREAK}} on MS-DOS) and then @kbd{C-h l}
Dave Love <fx@gnu.org>
parents:
diff changeset
482 to see whether the input Emacs received was what you intended to type;
Dave Love <fx@gnu.org>
parents:
diff changeset
483 if the input was such that you @emph{know} it should have been processed
Dave Love <fx@gnu.org>
parents:
diff changeset
484 quickly, report a bug. If you don't know whether the command should
Dave Love <fx@gnu.org>
parents:
diff changeset
485 take a long time, find out by looking in the manual or by asking for
Dave Love <fx@gnu.org>
parents:
diff changeset
486 assistance.
Dave Love <fx@gnu.org>
parents:
diff changeset
487
Dave Love <fx@gnu.org>
parents:
diff changeset
488 If a command you are familiar with causes an Emacs error message in a
Dave Love <fx@gnu.org>
parents:
diff changeset
489 case where its usual definition ought to be reasonable, it is probably a
Dave Love <fx@gnu.org>
parents:
diff changeset
490 bug.
Dave Love <fx@gnu.org>
parents:
diff changeset
491
Dave Love <fx@gnu.org>
parents:
diff changeset
492 If a command does the wrong thing, that is a bug. But be sure you know
Dave Love <fx@gnu.org>
parents:
diff changeset
493 for certain what it ought to have done. If you aren't familiar with the
Dave Love <fx@gnu.org>
parents:
diff changeset
494 command, or don't know for certain how the command is supposed to work,
Dave Love <fx@gnu.org>
parents:
diff changeset
495 then it might actually be working right. Rather than jumping to
Dave Love <fx@gnu.org>
parents:
diff changeset
496 conclusions, show the problem to someone who knows for certain.
Dave Love <fx@gnu.org>
parents:
diff changeset
497
36388
5835d43dcf93 (Bug Criteria): Reword a sentence.
Gerd Moellmann <gerd@gnu.org>
parents: 36294
diff changeset
498 Finally, a command's intended definition may not be the best
5835d43dcf93 (Bug Criteria): Reword a sentence.
Gerd Moellmann <gerd@gnu.org>
parents: 36294
diff changeset
499 possible definition for editing with. This is a very important sort
5835d43dcf93 (Bug Criteria): Reword a sentence.
Gerd Moellmann <gerd@gnu.org>
parents: 36294
diff changeset
500 of problem, but it is also a matter of judgment. Also, it is easy to
5835d43dcf93 (Bug Criteria): Reword a sentence.
Gerd Moellmann <gerd@gnu.org>
parents: 36294
diff changeset
501 come to such a conclusion out of ignorance of some of the existing
5835d43dcf93 (Bug Criteria): Reword a sentence.
Gerd Moellmann <gerd@gnu.org>
parents: 36294
diff changeset
502 features. It is probably best not to complain about such a problem
5835d43dcf93 (Bug Criteria): Reword a sentence.
Gerd Moellmann <gerd@gnu.org>
parents: 36294
diff changeset
503 until you have checked the documentation in the usual ways, feel
5835d43dcf93 (Bug Criteria): Reword a sentence.
Gerd Moellmann <gerd@gnu.org>
parents: 36294
diff changeset
504 confident that you understand it, and know for certain that what you
5835d43dcf93 (Bug Criteria): Reword a sentence.
Gerd Moellmann <gerd@gnu.org>
parents: 36294
diff changeset
505 want is not available. If you are not sure what the command is
5835d43dcf93 (Bug Criteria): Reword a sentence.
Gerd Moellmann <gerd@gnu.org>
parents: 36294
diff changeset
506 supposed to do after a careful reading of the manual, check the index
5835d43dcf93 (Bug Criteria): Reword a sentence.
Gerd Moellmann <gerd@gnu.org>
parents: 36294
diff changeset
507 and glossary for any terms that may be unclear.
25829
Dave Love <fx@gnu.org>
parents:
diff changeset
508
Dave Love <fx@gnu.org>
parents:
diff changeset
509 If after careful rereading of the manual you still do not understand
Dave Love <fx@gnu.org>
parents:
diff changeset
510 what the command should do, that indicates a bug in the manual, which
Dave Love <fx@gnu.org>
parents:
diff changeset
511 you should report. The manual's job is to make everything clear to
Dave Love <fx@gnu.org>
parents:
diff changeset
512 people who are not Emacs experts---including you. It is just as
Dave Love <fx@gnu.org>
parents:
diff changeset
513 important to report documentation bugs as program bugs.
Dave Love <fx@gnu.org>
parents:
diff changeset
514
Dave Love <fx@gnu.org>
parents:
diff changeset
515 If the on-line documentation string of a function or variable disagrees
Dave Love <fx@gnu.org>
parents:
diff changeset
516 with the manual, one of them must be wrong; that is a bug.
Dave Love <fx@gnu.org>
parents:
diff changeset
517
Dave Love <fx@gnu.org>
parents:
diff changeset
518 @node Understanding Bug Reporting
Dave Love <fx@gnu.org>
parents:
diff changeset
519 @subsection Understanding Bug Reporting
Dave Love <fx@gnu.org>
parents:
diff changeset
520
Dave Love <fx@gnu.org>
parents:
diff changeset
521 @findex emacs-version
Dave Love <fx@gnu.org>
parents:
diff changeset
522 When you decide that there is a bug, it is important to report it and to
Dave Love <fx@gnu.org>
parents:
diff changeset
523 report it in a way which is useful. What is most useful is an exact
Dave Love <fx@gnu.org>
parents:
diff changeset
524 description of what commands you type, starting with the shell command to
Dave Love <fx@gnu.org>
parents:
diff changeset
525 run Emacs, until the problem happens.
Dave Love <fx@gnu.org>
parents:
diff changeset
526
Dave Love <fx@gnu.org>
parents:
diff changeset
527 The most important principle in reporting a bug is to report
Dave Love <fx@gnu.org>
parents:
diff changeset
528 @emph{facts}. Hypotheses and verbal descriptions are no substitute for
Dave Love <fx@gnu.org>
parents:
diff changeset
529 the detailed raw data. Reporting the facts is straightforward, but many
Dave Love <fx@gnu.org>
parents:
diff changeset
530 people strain to posit explanations and report them instead of the
Dave Love <fx@gnu.org>
parents:
diff changeset
531 facts. If the explanations are based on guesses about how Emacs is
Dave Love <fx@gnu.org>
parents:
diff changeset
532 implemented, they will be useless; meanwhile, lacking the facts, we will
Dave Love <fx@gnu.org>
parents:
diff changeset
533 have no real information about the bug.
Dave Love <fx@gnu.org>
parents:
diff changeset
534
Dave Love <fx@gnu.org>
parents:
diff changeset
535 For example, suppose that you type @kbd{C-x C-f /glorp/baz.ugh
Dave Love <fx@gnu.org>
parents:
diff changeset
536 @key{RET}}, visiting a file which (you know) happens to be rather large,
Dave Love <fx@gnu.org>
parents:
diff changeset
537 and Emacs displayed @samp{I feel pretty today}. The best way to report
Dave Love <fx@gnu.org>
parents:
diff changeset
538 the bug is with a sentence like the preceding one, because it gives all
Dave Love <fx@gnu.org>
parents:
diff changeset
539 the facts.
Dave Love <fx@gnu.org>
parents:
diff changeset
540
Dave Love <fx@gnu.org>
parents:
diff changeset
541 A bad way would be to assume that the problem is due to the size of
Dave Love <fx@gnu.org>
parents:
diff changeset
542 the file and say, ``I visited a large file, and Emacs displayed @samp{I
Dave Love <fx@gnu.org>
parents:
diff changeset
543 feel pretty today}.'' This is what we mean by ``guessing
Dave Love <fx@gnu.org>
parents:
diff changeset
544 explanations.'' The problem is just as likely to be due to the fact
Dave Love <fx@gnu.org>
parents:
diff changeset
545 that there is a @samp{z} in the file name. If this is so, then when we
Dave Love <fx@gnu.org>
parents:
diff changeset
546 got your report, we would try out the problem with some ``large file,''
Dave Love <fx@gnu.org>
parents:
diff changeset
547 probably with no @samp{z} in its name, and not see any problem. There
Dave Love <fx@gnu.org>
parents:
diff changeset
548 is no way in the world that we could guess that we should try visiting a
Dave Love <fx@gnu.org>
parents:
diff changeset
549 file with a @samp{z} in its name.
Dave Love <fx@gnu.org>
parents:
diff changeset
550
Dave Love <fx@gnu.org>
parents:
diff changeset
551 Alternatively, the problem might be due to the fact that the file starts
Dave Love <fx@gnu.org>
parents:
diff changeset
552 with exactly 25 spaces. For this reason, you should make sure that you
Dave Love <fx@gnu.org>
parents:
diff changeset
553 inform us of the exact contents of any file that is needed to reproduce the
Dave Love <fx@gnu.org>
parents:
diff changeset
554 bug. What if the problem only occurs when you have typed the @kbd{C-x C-a}
Dave Love <fx@gnu.org>
parents:
diff changeset
555 command previously? This is why we ask you to give the exact sequence of
Dave Love <fx@gnu.org>
parents:
diff changeset
556 characters you typed since starting the Emacs session.
Dave Love <fx@gnu.org>
parents:
diff changeset
557
Dave Love <fx@gnu.org>
parents:
diff changeset
558 You should not even say ``visit a file'' instead of @kbd{C-x C-f} unless
Dave Love <fx@gnu.org>
parents:
diff changeset
559 you @emph{know} that it makes no difference which visiting command is used.
Dave Love <fx@gnu.org>
parents:
diff changeset
560 Similarly, rather than saying ``if I have three characters on the line,''
Dave Love <fx@gnu.org>
parents:
diff changeset
561 say ``after I type @kbd{@key{RET} A B C @key{RET} C-p},'' if that is
Dave Love <fx@gnu.org>
parents:
diff changeset
562 the way you entered the text.@refill
Dave Love <fx@gnu.org>
parents:
diff changeset
563
Dave Love <fx@gnu.org>
parents:
diff changeset
564 So please don't guess any explanations when you report a bug. If you
Dave Love <fx@gnu.org>
parents:
diff changeset
565 want to actually @emph{debug} the problem, and report explanations that
Dave Love <fx@gnu.org>
parents:
diff changeset
566 are more than guesses, that is useful---but please include the facts as
Dave Love <fx@gnu.org>
parents:
diff changeset
567 well.
Dave Love <fx@gnu.org>
parents:
diff changeset
568
Dave Love <fx@gnu.org>
parents:
diff changeset
569 @node Checklist
Dave Love <fx@gnu.org>
parents:
diff changeset
570 @subsection Checklist for Bug Reports
Dave Love <fx@gnu.org>
parents:
diff changeset
571
Dave Love <fx@gnu.org>
parents:
diff changeset
572 @cindex reporting bugs
Dave Love <fx@gnu.org>
parents:
diff changeset
573 The best way to send a bug report is to mail it electronically to the
36180
252e21b04fb1 Suggest copying problematical manual text into the bug report.
Richard M. Stallman <rms@gnu.org>
parents: 35874
diff changeset
574 Emacs maintainers at @email{bug-gnu-emacs@@gnu.org}, or to
252e21b04fb1 Suggest copying problematical manual text into the bug report.
Richard M. Stallman <rms@gnu.org>
parents: 35874
diff changeset
575 @email{emacs-pretest-bug@@gnu.org} if you are pretesting an Emacs beta
26021
4f5e4ec69f6a Add emacs-prestest-bug@gnu.org analogous to bug-gnu-emacs@gnu.org.
Gerd Moellmann <gerd@gnu.org>
parents: 25829
diff changeset
576 release. (If you want to suggest a change as an improvement, use the
4f5e4ec69f6a Add emacs-prestest-bug@gnu.org analogous to bug-gnu-emacs@gnu.org.
Gerd Moellmann <gerd@gnu.org>
parents: 25829
diff changeset
577 same address.)
25829
Dave Love <fx@gnu.org>
parents:
diff changeset
578
Dave Love <fx@gnu.org>
parents:
diff changeset
579 If you'd like to read the bug reports, you can find them on the
Dave Love <fx@gnu.org>
parents:
diff changeset
580 newsgroup @samp{gnu.emacs.bug}; keep in mind, however, that as a
Dave Love <fx@gnu.org>
parents:
diff changeset
581 spectator you should not criticize anything about what you see there.
Dave Love <fx@gnu.org>
parents:
diff changeset
582 The purpose of bug reports is to give information to the Emacs
Dave Love <fx@gnu.org>
parents:
diff changeset
583 maintainers. Spectators are welcome only as long as they do not
38245
9ada58a02f7e Don't include data bigger than 500,000 bytes directly in the bug
Richard M. Stallman <rms@gnu.org>
parents: 38230
diff changeset
584 interfere with this. In particular, some bug reports contain fairly
9ada58a02f7e Don't include data bigger than 500,000 bytes directly in the bug
Richard M. Stallman <rms@gnu.org>
parents: 38230
diff changeset
585 large amounts of data; spectators should not complain about this.
25829
Dave Love <fx@gnu.org>
parents:
diff changeset
586
Dave Love <fx@gnu.org>
parents:
diff changeset
587 Please do not post bug reports using netnews; mail is more reliable
38245
9ada58a02f7e Don't include data bigger than 500,000 bytes directly in the bug
Richard M. Stallman <rms@gnu.org>
parents: 38230
diff changeset
588 than netnews about reporting your correct address, which we may need
9ada58a02f7e Don't include data bigger than 500,000 bytes directly in the bug
Richard M. Stallman <rms@gnu.org>
parents: 38230
diff changeset
589 in order to ask you for more information. If your data is more than
9ada58a02f7e Don't include data bigger than 500,000 bytes directly in the bug
Richard M. Stallman <rms@gnu.org>
parents: 38230
diff changeset
590 500,000 bytes, please don't include it directly in the bug report;
9ada58a02f7e Don't include data bigger than 500,000 bytes directly in the bug
Richard M. Stallman <rms@gnu.org>
parents: 38230
diff changeset
591 instead, offer to send it on request, or make it available by ftp and
9ada58a02f7e Don't include data bigger than 500,000 bytes directly in the bug
Richard M. Stallman <rms@gnu.org>
parents: 38230
diff changeset
592 say where.
25829
Dave Love <fx@gnu.org>
parents:
diff changeset
593
Dave Love <fx@gnu.org>
parents:
diff changeset
594 If you can't send electronic mail, then mail the bug report on paper
Dave Love <fx@gnu.org>
parents:
diff changeset
595 or machine-readable media to this address:
Dave Love <fx@gnu.org>
parents:
diff changeset
596
Dave Love <fx@gnu.org>
parents:
diff changeset
597 @format
Dave Love <fx@gnu.org>
parents:
diff changeset
598 GNU Emacs Bugs
Dave Love <fx@gnu.org>
parents:
diff changeset
599 Free Software Foundation
64083
23a17af379b1 Update FSF's address.
Lute Kamstra <lute@gnu.org>
parents: 62991
diff changeset
600 51 Franklin Street, Fifth Floor
23a17af379b1 Update FSF's address.
Lute Kamstra <lute@gnu.org>
parents: 62991
diff changeset
601 Boston, MA 02110-1301 USA
25829
Dave Love <fx@gnu.org>
parents:
diff changeset
602 @end format
Dave Love <fx@gnu.org>
parents:
diff changeset
603
Dave Love <fx@gnu.org>
parents:
diff changeset
604 We do not promise to fix the bug; but if the bug is serious,
Dave Love <fx@gnu.org>
parents:
diff changeset
605 or ugly, or easy to fix, chances are we will want to.
Dave Love <fx@gnu.org>
parents:
diff changeset
606
Dave Love <fx@gnu.org>
parents:
diff changeset
607 @findex report-emacs-bug
Dave Love <fx@gnu.org>
parents:
diff changeset
608 A convenient way to send a bug report for Emacs is to use the command
Dave Love <fx@gnu.org>
parents:
diff changeset
609 @kbd{M-x report-emacs-bug}. This sets up a mail buffer (@pxref{Sending
Dave Love <fx@gnu.org>
parents:
diff changeset
610 Mail}) and automatically inserts @emph{some} of the essential
Dave Love <fx@gnu.org>
parents:
diff changeset
611 information. However, it cannot supply all the necessary information;
Dave Love <fx@gnu.org>
parents:
diff changeset
612 you should still read and follow the guidelines below, so you can enter
Dave Love <fx@gnu.org>
parents:
diff changeset
613 the other crucial information by hand before you send the message.
Dave Love <fx@gnu.org>
parents:
diff changeset
614
Dave Love <fx@gnu.org>
parents:
diff changeset
615 To enable maintainers to investigate a bug, your report
Dave Love <fx@gnu.org>
parents:
diff changeset
616 should include all these things:
Dave Love <fx@gnu.org>
parents:
diff changeset
617
Dave Love <fx@gnu.org>
parents:
diff changeset
618 @itemize @bullet
Dave Love <fx@gnu.org>
parents:
diff changeset
619 @item
Dave Love <fx@gnu.org>
parents:
diff changeset
620 The version number of Emacs. Without this, we won't know whether there
Dave Love <fx@gnu.org>
parents:
diff changeset
621 is any point in looking for the bug in the current version of GNU
Dave Love <fx@gnu.org>
parents:
diff changeset
622 Emacs.
Dave Love <fx@gnu.org>
parents:
diff changeset
623
Dave Love <fx@gnu.org>
parents:
diff changeset
624 You can get the version number by typing @kbd{M-x emacs-version
Dave Love <fx@gnu.org>
parents:
diff changeset
625 @key{RET}}. If that command does not work, you probably have something
Dave Love <fx@gnu.org>
parents:
diff changeset
626 other than GNU Emacs, so you will have to report the bug somewhere
Dave Love <fx@gnu.org>
parents:
diff changeset
627 else.
Dave Love <fx@gnu.org>
parents:
diff changeset
628
Dave Love <fx@gnu.org>
parents:
diff changeset
629 @item
Dave Love <fx@gnu.org>
parents:
diff changeset
630 The type of machine you are using, and the operating system name and
Dave Love <fx@gnu.org>
parents:
diff changeset
631 version number. @kbd{M-x emacs-version @key{RET}} provides this
Dave Love <fx@gnu.org>
parents:
diff changeset
632 information too. Copy its output from the @samp{*Messages*} buffer, so
Dave Love <fx@gnu.org>
parents:
diff changeset
633 that you get it all and get it accurately.
Dave Love <fx@gnu.org>
parents:
diff changeset
634
Dave Love <fx@gnu.org>
parents:
diff changeset
635 @item
Dave Love <fx@gnu.org>
parents:
diff changeset
636 The operands given to the @code{configure} command when Emacs was
Dave Love <fx@gnu.org>
parents:
diff changeset
637 installed.
Dave Love <fx@gnu.org>
parents:
diff changeset
638
Dave Love <fx@gnu.org>
parents:
diff changeset
639 @item
Dave Love <fx@gnu.org>
parents:
diff changeset
640 A complete list of any modifications you have made to the Emacs source.
Dave Love <fx@gnu.org>
parents:
diff changeset
641 (We may not have time to investigate the bug unless it happens in an
Dave Love <fx@gnu.org>
parents:
diff changeset
642 unmodified Emacs. But if you've made modifications and you don't tell
Dave Love <fx@gnu.org>
parents:
diff changeset
643 us, you are sending us on a wild goose chase.)
Dave Love <fx@gnu.org>
parents:
diff changeset
644
Dave Love <fx@gnu.org>
parents:
diff changeset
645 Be precise about these changes. A description in English is not
Dave Love <fx@gnu.org>
parents:
diff changeset
646 enough---send a context diff for them.
Dave Love <fx@gnu.org>
parents:
diff changeset
647
Dave Love <fx@gnu.org>
parents:
diff changeset
648 Adding files of your own, or porting to another machine, is a
Dave Love <fx@gnu.org>
parents:
diff changeset
649 modification of the source.
Dave Love <fx@gnu.org>
parents:
diff changeset
650
Dave Love <fx@gnu.org>
parents:
diff changeset
651 @item
Dave Love <fx@gnu.org>
parents:
diff changeset
652 Details of any other deviations from the standard procedure for installing
Dave Love <fx@gnu.org>
parents:
diff changeset
653 GNU Emacs.
Dave Love <fx@gnu.org>
parents:
diff changeset
654
Dave Love <fx@gnu.org>
parents:
diff changeset
655 @item
Dave Love <fx@gnu.org>
parents:
diff changeset
656 The complete text of any files needed to reproduce the bug.
Dave Love <fx@gnu.org>
parents:
diff changeset
657
Dave Love <fx@gnu.org>
parents:
diff changeset
658 If you can tell us a way to cause the problem without visiting any files,
Dave Love <fx@gnu.org>
parents:
diff changeset
659 please do so. This makes it much easier to debug. If you do need files,
Dave Love <fx@gnu.org>
parents:
diff changeset
660 make sure you arrange for us to see their exact contents. For example, it
Dave Love <fx@gnu.org>
parents:
diff changeset
661 can often matter whether there are spaces at the ends of lines, or a
Dave Love <fx@gnu.org>
parents:
diff changeset
662 newline after the last line in the buffer (nothing ought to care whether
Dave Love <fx@gnu.org>
parents:
diff changeset
663 the last line is terminated, but try telling the bugs that).
Dave Love <fx@gnu.org>
parents:
diff changeset
664
Dave Love <fx@gnu.org>
parents:
diff changeset
665 @item
Dave Love <fx@gnu.org>
parents:
diff changeset
666 The precise commands we need to type to reproduce the bug.
Dave Love <fx@gnu.org>
parents:
diff changeset
667
Dave Love <fx@gnu.org>
parents:
diff changeset
668 @findex open-dribble-file
Dave Love <fx@gnu.org>
parents:
diff changeset
669 @cindex dribble file
35705
6c05ec832ecc (Checklist): Add index entry for logging keystrokes.
Eli Zaretskii <eliz@gnu.org>
parents: 35239
diff changeset
670 @cindex logging keystrokes
25829
Dave Love <fx@gnu.org>
parents:
diff changeset
671 The easy way to record the input to Emacs precisely is to write a
Dave Love <fx@gnu.org>
parents:
diff changeset
672 dribble file. To start the file, execute the Lisp expression
Dave Love <fx@gnu.org>
parents:
diff changeset
673
Dave Love <fx@gnu.org>
parents:
diff changeset
674 @example
Dave Love <fx@gnu.org>
parents:
diff changeset
675 (open-dribble-file "~/dribble")
Dave Love <fx@gnu.org>
parents:
diff changeset
676 @end example
Dave Love <fx@gnu.org>
parents:
diff changeset
677
Dave Love <fx@gnu.org>
parents:
diff changeset
678 @noindent
Dave Love <fx@gnu.org>
parents:
diff changeset
679 using @kbd{M-:} or from the @samp{*scratch*} buffer just after
Dave Love <fx@gnu.org>
parents:
diff changeset
680 starting Emacs. From then on, Emacs copies all your input to the
Dave Love <fx@gnu.org>
parents:
diff changeset
681 specified dribble file until the Emacs process is killed.
Dave Love <fx@gnu.org>
parents:
diff changeset
682
Dave Love <fx@gnu.org>
parents:
diff changeset
683 @item
Dave Love <fx@gnu.org>
parents:
diff changeset
684 @findex open-termscript
Dave Love <fx@gnu.org>
parents:
diff changeset
685 @cindex termscript file
29107
203ba1f77b7b *** empty log message ***
Gerd Moellmann <gerd@gnu.org>
parents: 27729
diff changeset
686 @cindex @env{TERM} environment variable
25829
Dave Love <fx@gnu.org>
parents:
diff changeset
687 For possible display bugs, the terminal type (the value of environment
29107
203ba1f77b7b *** empty log message ***
Gerd Moellmann <gerd@gnu.org>
parents: 27729
diff changeset
688 variable @env{TERM}), the complete termcap entry for the terminal from
25829
Dave Love <fx@gnu.org>
parents:
diff changeset
689 @file{/etc/termcap} (since that file is not identical on all machines),
Dave Love <fx@gnu.org>
parents:
diff changeset
690 and the output that Emacs actually sent to the terminal.
Dave Love <fx@gnu.org>
parents:
diff changeset
691
Dave Love <fx@gnu.org>
parents:
diff changeset
692 The way to collect the terminal output is to execute the Lisp expression
Dave Love <fx@gnu.org>
parents:
diff changeset
693
Dave Love <fx@gnu.org>
parents:
diff changeset
694 @example
Dave Love <fx@gnu.org>
parents:
diff changeset
695 (open-termscript "~/termscript")
Dave Love <fx@gnu.org>
parents:
diff changeset
696 @end example
Dave Love <fx@gnu.org>
parents:
diff changeset
697
Dave Love <fx@gnu.org>
parents:
diff changeset
698 @noindent
Dave Love <fx@gnu.org>
parents:
diff changeset
699 using @kbd{M-:} or from the @samp{*scratch*} buffer just after
Dave Love <fx@gnu.org>
parents:
diff changeset
700 starting Emacs. From then on, Emacs copies all terminal output to the
Dave Love <fx@gnu.org>
parents:
diff changeset
701 specified termscript file as well, until the Emacs process is killed.
Dave Love <fx@gnu.org>
parents:
diff changeset
702 If the problem happens when Emacs starts up, put this expression into
Dave Love <fx@gnu.org>
parents:
diff changeset
703 your @file{.emacs} file so that the termscript file will be open when
Dave Love <fx@gnu.org>
parents:
diff changeset
704 Emacs displays the screen for the first time.
Dave Love <fx@gnu.org>
parents:
diff changeset
705
Dave Love <fx@gnu.org>
parents:
diff changeset
706 Be warned: it is often difficult, and sometimes impossible, to fix a
Dave Love <fx@gnu.org>
parents:
diff changeset
707 terminal-dependent bug without access to a terminal of the type that
Dave Love <fx@gnu.org>
parents:
diff changeset
708 stimulates the bug.@refill
Dave Love <fx@gnu.org>
parents:
diff changeset
709
Dave Love <fx@gnu.org>
parents:
diff changeset
710 @item
52979
3649390c0f91 Replace @sc{ascii} and ASCII with @acronym{ASCII}.
Eli Zaretskii <eliz@gnu.org>
parents: 52401
diff changeset
711 If non-@acronym{ASCII} text or internationalization is relevant, the locale that
36497
1ba3f8033b3a (Checklist): Say that the example with LC_ALL and such is for a Unix shell.
Eli Zaretskii <eliz@gnu.org>
parents: 36388
diff changeset
712 was current when you started Emacs. On GNU/Linux and Unix systems, or
38865
62e02f5ae533 Avoid saying "Unix" in a way that includes GNU.
Richard M. Stallman <rms@gnu.org>
parents: 38767
diff changeset
713 if you use a Posix-style shell such as Bash, you can use this shell
36497
1ba3f8033b3a (Checklist): Say that the example with LC_ALL and such is for a Unix shell.
Eli Zaretskii <eliz@gnu.org>
parents: 36388
diff changeset
714 command to view the relevant values:
35239
a4e73c75cbca Ask for locale info in bug reports.
Richard M. Stallman <rms@gnu.org>
parents: 35188
diff changeset
715
37580
ac2f45ecf299 Use @smallexample for the echo LC... command.
Richard M. Stallman <rms@gnu.org>
parents: 37508
diff changeset
716 @smallexample
42117
bdf2f34631aa Finish previous change.
Richard M. Stallman <rms@gnu.org>
parents: 42110
diff changeset
717 echo LC_ALL=$LC_ALL LC_COLLATE=$LC_COLLATE LC_CTYPE=$LC_CTYPE \
37119
a4f474cb3812 (Checklist): Include more LC_* variables in the list, as suggested
Eli Zaretskii <eliz@gnu.org>
parents: 37087
diff changeset
718 LC_MESSAGES=$LC_MESSAGES LC_TIME=$LC_TIME LANG=$LANG
37580
ac2f45ecf299 Use @smallexample for the echo LC... command.
Richard M. Stallman <rms@gnu.org>
parents: 37508
diff changeset
719 @end smallexample
35239
a4e73c75cbca Ask for locale info in bug reports.
Richard M. Stallman <rms@gnu.org>
parents: 35188
diff changeset
720
37087
f4039f11318f (Checklist): Mention the `locale' command as an alternative method of
Eli Zaretskii <eliz@gnu.org>
parents: 36791
diff changeset
721 Alternatively, use the @command{locale} command, if your system has it,
f4039f11318f (Checklist): Mention the `locale' command as an alternative method of
Eli Zaretskii <eliz@gnu.org>
parents: 36791
diff changeset
722 to display your locale settings.
f4039f11318f (Checklist): Mention the `locale' command as an alternative method of
Eli Zaretskii <eliz@gnu.org>
parents: 36791
diff changeset
723
f4039f11318f (Checklist): Mention the `locale' command as an alternative method of
Eli Zaretskii <eliz@gnu.org>
parents: 36791
diff changeset
724 You can use the @kbd{M-!} command to execute these commands from
35239
a4e73c75cbca Ask for locale info in bug reports.
Richard M. Stallman <rms@gnu.org>
parents: 35188
diff changeset
725 Emacs, and then copy the output from the @samp{*Messages*} buffer into
36620
639ad3d05eb6 (Checklist): Mention that `getenv' can be used to get at the value
Eli Zaretskii <eliz@gnu.org>
parents: 36497
diff changeset
726 the bug report. Alternatively, @kbd{M-x getenv @key{RET} LC_ALL
38870
d44abb4e68b2 Don't use "print" for displaying a message.
Richard M. Stallman <rms@gnu.org>
parents: 38865
diff changeset
727 @key{RET}} will display the value of @code{LC_ALL} in the echo area, and
36620
639ad3d05eb6 (Checklist): Mention that `getenv' can be used to get at the value
Eli Zaretskii <eliz@gnu.org>
parents: 36497
diff changeset
728 you can copy its output from the @samp{*Messages*} buffer.
35239
a4e73c75cbca Ask for locale info in bug reports.
Richard M. Stallman <rms@gnu.org>
parents: 35188
diff changeset
729
a4e73c75cbca Ask for locale info in bug reports.
Richard M. Stallman <rms@gnu.org>
parents: 35188
diff changeset
730 @item
25829
Dave Love <fx@gnu.org>
parents:
diff changeset
731 A description of what behavior you observe that you believe is
Dave Love <fx@gnu.org>
parents:
diff changeset
732 incorrect. For example, ``The Emacs process gets a fatal signal,'' or,
Dave Love <fx@gnu.org>
parents:
diff changeset
733 ``The resulting text is as follows, which I think is wrong.''
Dave Love <fx@gnu.org>
parents:
diff changeset
734
Dave Love <fx@gnu.org>
parents:
diff changeset
735 Of course, if the bug is that Emacs gets a fatal signal, then one can't
Dave Love <fx@gnu.org>
parents:
diff changeset
736 miss it. But if the bug is incorrect text, the maintainer might fail to
Dave Love <fx@gnu.org>
parents:
diff changeset
737 notice what is wrong. Why leave it to chance?
Dave Love <fx@gnu.org>
parents:
diff changeset
738
Dave Love <fx@gnu.org>
parents:
diff changeset
739 Even if the problem you experience is a fatal signal, you should still
Dave Love <fx@gnu.org>
parents:
diff changeset
740 say so explicitly. Suppose something strange is going on, such as, your
Dave Love <fx@gnu.org>
parents:
diff changeset
741 copy of the source is out of sync, or you have encountered a bug in the
Dave Love <fx@gnu.org>
parents:
diff changeset
742 C library on your system. (This has happened!) Your copy might crash
Dave Love <fx@gnu.org>
parents:
diff changeset
743 and the copy here might not. If you @emph{said} to expect a crash, then
Dave Love <fx@gnu.org>
parents:
diff changeset
744 when Emacs here fails to crash, we would know that the bug was not
Dave Love <fx@gnu.org>
parents:
diff changeset
745 happening. If you don't say to expect a crash, then we would not know
Dave Love <fx@gnu.org>
parents:
diff changeset
746 whether the bug was happening---we would not be able to draw any
Dave Love <fx@gnu.org>
parents:
diff changeset
747 conclusion from our observations.
Dave Love <fx@gnu.org>
parents:
diff changeset
748
Dave Love <fx@gnu.org>
parents:
diff changeset
749 @item
36180
252e21b04fb1 Suggest copying problematical manual text into the bug report.
Richard M. Stallman <rms@gnu.org>
parents: 35874
diff changeset
750 If the bug is that the Emacs Manual or the Emacs Lisp Reference Manual
252e21b04fb1 Suggest copying problematical manual text into the bug report.
Richard M. Stallman <rms@gnu.org>
parents: 35874
diff changeset
751 fails to describe the actual behavior of Emacs, or that the text is
252e21b04fb1 Suggest copying problematical manual text into the bug report.
Richard M. Stallman <rms@gnu.org>
parents: 35874
diff changeset
752 confusing, copy in the text from the online manual which you think is
252e21b04fb1 Suggest copying problematical manual text into the bug report.
Richard M. Stallman <rms@gnu.org>
parents: 35874
diff changeset
753 at fault. If the section is small, just the section name is enough.
252e21b04fb1 Suggest copying problematical manual text into the bug report.
Richard M. Stallman <rms@gnu.org>
parents: 35874
diff changeset
754
252e21b04fb1 Suggest copying problematical manual text into the bug report.
Richard M. Stallman <rms@gnu.org>
parents: 35874
diff changeset
755 @item
25829
Dave Love <fx@gnu.org>
parents:
diff changeset
756 If the manifestation of the bug is an Emacs error message, it is
Dave Love <fx@gnu.org>
parents:
diff changeset
757 important to report the precise text of the error message, and a
Dave Love <fx@gnu.org>
parents:
diff changeset
758 backtrace showing how the Lisp program in Emacs arrived at the error.
Dave Love <fx@gnu.org>
parents:
diff changeset
759
Dave Love <fx@gnu.org>
parents:
diff changeset
760 To get the error message text accurately, copy it from the
Dave Love <fx@gnu.org>
parents:
diff changeset
761 @samp{*Messages*} buffer into the bug report. Copy all of it, not just
Dave Love <fx@gnu.org>
parents:
diff changeset
762 part.
Dave Love <fx@gnu.org>
parents:
diff changeset
763
37347
bd817d6f9ba3 Minor clarifications regarding DEL key.
Richard M. Stallman <rms@gnu.org>
parents: 37126
diff changeset
764 @findex toggle-debug-on-error
37508
e2849d417d6d (Checklist): Mention Edebug.
Eli Zaretskii <eliz@gnu.org>
parents: 37498
diff changeset
765 @pindex Edebug
37347
bd817d6f9ba3 Minor clarifications regarding DEL key.
Richard M. Stallman <rms@gnu.org>
parents: 37126
diff changeset
766 To make a backtrace for the error, use @kbd{M-x toggle-debug-on-error}
bd817d6f9ba3 Minor clarifications regarding DEL key.
Richard M. Stallman <rms@gnu.org>
parents: 37126
diff changeset
767 before the error happens (that is to say, you must give that command
bd817d6f9ba3 Minor clarifications regarding DEL key.
Richard M. Stallman <rms@gnu.org>
parents: 37126
diff changeset
768 and then make the bug happen). This causes the error to run the Lisp
bd817d6f9ba3 Minor clarifications regarding DEL key.
Richard M. Stallman <rms@gnu.org>
parents: 37126
diff changeset
769 debugger, which shows you a backtrace. Copy the text of the
bd817d6f9ba3 Minor clarifications regarding DEL key.
Richard M. Stallman <rms@gnu.org>
parents: 37126
diff changeset
770 debugger's backtrace into the bug report. @xref{Debugger,, The Lisp
bd817d6f9ba3 Minor clarifications regarding DEL key.
Richard M. Stallman <rms@gnu.org>
parents: 37126
diff changeset
771 Debugger, elisp, the Emacs Lisp Reference Manual}, for information on
37508
e2849d417d6d (Checklist): Mention Edebug.
Eli Zaretskii <eliz@gnu.org>
parents: 37498
diff changeset
772 debugging Emacs Lisp programs with the Edebug package.
25829
Dave Love <fx@gnu.org>
parents:
diff changeset
773
Dave Love <fx@gnu.org>
parents:
diff changeset
774 This use of the debugger is possible only if you know how to make the
Dave Love <fx@gnu.org>
parents:
diff changeset
775 bug happen again. If you can't make it happen again, at least copy
Dave Love <fx@gnu.org>
parents:
diff changeset
776 the whole error message.
Dave Love <fx@gnu.org>
parents:
diff changeset
777
Dave Love <fx@gnu.org>
parents:
diff changeset
778 @item
Dave Love <fx@gnu.org>
parents:
diff changeset
779 Check whether any programs you have loaded into the Lisp world,
Dave Love <fx@gnu.org>
parents:
diff changeset
780 including your @file{.emacs} file, set any variables that may affect the
Dave Love <fx@gnu.org>
parents:
diff changeset
781 functioning of Emacs. Also, see whether the problem happens in a
Dave Love <fx@gnu.org>
parents:
diff changeset
782 freshly started Emacs without loading your @file{.emacs} file (start
Dave Love <fx@gnu.org>
parents:
diff changeset
783 Emacs with the @code{-q} switch to prevent loading the init file). If
Dave Love <fx@gnu.org>
parents:
diff changeset
784 the problem does @emph{not} occur then, you must report the precise
Dave Love <fx@gnu.org>
parents:
diff changeset
785 contents of any programs that you must load into the Lisp world in order
Dave Love <fx@gnu.org>
parents:
diff changeset
786 to cause the problem to occur.
Dave Love <fx@gnu.org>
parents:
diff changeset
787
Dave Love <fx@gnu.org>
parents:
diff changeset
788 @item
Dave Love <fx@gnu.org>
parents:
diff changeset
789 If the problem does depend on an init file or other Lisp programs that
Dave Love <fx@gnu.org>
parents:
diff changeset
790 are not part of the standard Emacs system, then you should make sure it
Dave Love <fx@gnu.org>
parents:
diff changeset
791 is not a bug in those programs by complaining to their maintainers
Dave Love <fx@gnu.org>
parents:
diff changeset
792 first. After they verify that they are using Emacs in a way that is
Dave Love <fx@gnu.org>
parents:
diff changeset
793 supposed to work, they should report the bug.
Dave Love <fx@gnu.org>
parents:
diff changeset
794
Dave Love <fx@gnu.org>
parents:
diff changeset
795 @item
Dave Love <fx@gnu.org>
parents:
diff changeset
796 If you wish to mention something in the GNU Emacs source, show the line
Dave Love <fx@gnu.org>
parents:
diff changeset
797 of code with a few lines of context. Don't just give a line number.
Dave Love <fx@gnu.org>
parents:
diff changeset
798
Dave Love <fx@gnu.org>
parents:
diff changeset
799 The line numbers in the development sources don't match those in your
Dave Love <fx@gnu.org>
parents:
diff changeset
800 sources. It would take extra work for the maintainers to determine what
Dave Love <fx@gnu.org>
parents:
diff changeset
801 code is in your version at a given line number, and we could not be
Dave Love <fx@gnu.org>
parents:
diff changeset
802 certain.
Dave Love <fx@gnu.org>
parents:
diff changeset
803
Dave Love <fx@gnu.org>
parents:
diff changeset
804 @item
Dave Love <fx@gnu.org>
parents:
diff changeset
805 Additional information from a C debugger such as GDB might enable
Dave Love <fx@gnu.org>
parents:
diff changeset
806 someone to find a problem on a machine which he does not have available.
Dave Love <fx@gnu.org>
parents:
diff changeset
807 If you don't know how to use GDB, please read the GDB manual---it is not
Dave Love <fx@gnu.org>
parents:
diff changeset
808 very long, and using GDB is easy. You can find the GDB distribution,
Dave Love <fx@gnu.org>
parents:
diff changeset
809 including the GDB manual in online form, in most of the same places you
Dave Love <fx@gnu.org>
parents:
diff changeset
810 can find the Emacs distribution. To run Emacs under GDB, you should
Dave Love <fx@gnu.org>
parents:
diff changeset
811 switch to the @file{src} subdirectory in which Emacs was compiled, then
Dave Love <fx@gnu.org>
parents:
diff changeset
812 do @samp{gdb emacs}. It is important for the directory @file{src} to be
Dave Love <fx@gnu.org>
parents:
diff changeset
813 current so that GDB will read the @file{.gdbinit} file in this
Dave Love <fx@gnu.org>
parents:
diff changeset
814 directory.
Dave Love <fx@gnu.org>
parents:
diff changeset
815
Dave Love <fx@gnu.org>
parents:
diff changeset
816 However, you need to think when you collect the additional information
Dave Love <fx@gnu.org>
parents:
diff changeset
817 if you want it to show what causes the bug.
Dave Love <fx@gnu.org>
parents:
diff changeset
818
Dave Love <fx@gnu.org>
parents:
diff changeset
819 @cindex backtrace for bug reports
Dave Love <fx@gnu.org>
parents:
diff changeset
820 For example, many people send just a backtrace, but that is not very
Dave Love <fx@gnu.org>
parents:
diff changeset
821 useful by itself. A simple backtrace with arguments often conveys
Dave Love <fx@gnu.org>
parents:
diff changeset
822 little about what is happening inside GNU Emacs, because most of the
Dave Love <fx@gnu.org>
parents:
diff changeset
823 arguments listed in the backtrace are pointers to Lisp objects. The
Dave Love <fx@gnu.org>
parents:
diff changeset
824 numeric values of these pointers have no significance whatever; all that
Dave Love <fx@gnu.org>
parents:
diff changeset
825 matters is the contents of the objects they point to (and most of the
Dave Love <fx@gnu.org>
parents:
diff changeset
826 contents are themselves pointers).
Dave Love <fx@gnu.org>
parents:
diff changeset
827
Dave Love <fx@gnu.org>
parents:
diff changeset
828 @findex debug_print
Dave Love <fx@gnu.org>
parents:
diff changeset
829 To provide useful information, you need to show the values of Lisp
Dave Love <fx@gnu.org>
parents:
diff changeset
830 objects in Lisp notation. Do this for each variable which is a Lisp
Dave Love <fx@gnu.org>
parents:
diff changeset
831 object, in several stack frames near the bottom of the stack. Look at
Dave Love <fx@gnu.org>
parents:
diff changeset
832 the source to see which variables are Lisp objects, because the debugger
Dave Love <fx@gnu.org>
parents:
diff changeset
833 thinks of them as integers.
Dave Love <fx@gnu.org>
parents:
diff changeset
834
Dave Love <fx@gnu.org>
parents:
diff changeset
835 To show a variable's value in Lisp syntax, first print its value, then
Dave Love <fx@gnu.org>
parents:
diff changeset
836 use the user-defined GDB command @code{pr} to print the Lisp object in
Dave Love <fx@gnu.org>
parents:
diff changeset
837 Lisp syntax. (If you must use another debugger, call the function
Dave Love <fx@gnu.org>
parents:
diff changeset
838 @code{debug_print} with the object as an argument.) The @code{pr}
Dave Love <fx@gnu.org>
parents:
diff changeset
839 command is defined by the file @file{.gdbinit}, and it works only if you
Dave Love <fx@gnu.org>
parents:
diff changeset
840 are debugging a running process (not with a core dump).
Dave Love <fx@gnu.org>
parents:
diff changeset
841
Dave Love <fx@gnu.org>
parents:
diff changeset
842 To make Lisp errors stop Emacs and return to GDB, put a breakpoint at
Dave Love <fx@gnu.org>
parents:
diff changeset
843 @code{Fsignal}.
Dave Love <fx@gnu.org>
parents:
diff changeset
844
27729
75463d908406 *** empty log message ***
Gerd Moellmann <gerd@gnu.org>
parents: 26021
diff changeset
845 For a short listing of Lisp functions running, type the GDB
49600
23a1cea22d13 Trailing whitespace deleted.
Juanma Barranquero <lekktu@gmail.com>
parents: 46235
diff changeset
846 command @code{xbacktrace}.
27729
75463d908406 *** empty log message ***
Gerd Moellmann <gerd@gnu.org>
parents: 26021
diff changeset
847
25829
Dave Love <fx@gnu.org>
parents:
diff changeset
848 The file @file{.gdbinit} defines several other commands that are useful
Dave Love <fx@gnu.org>
parents:
diff changeset
849 for examining the data types and contents of Lisp objects. Their names
Dave Love <fx@gnu.org>
parents:
diff changeset
850 begin with @samp{x}. These commands work at a lower level than
Dave Love <fx@gnu.org>
parents:
diff changeset
851 @code{pr}, and are less convenient, but they may work even when
Dave Love <fx@gnu.org>
parents:
diff changeset
852 @code{pr} does not, such as when debugging a core dump or when Emacs has
Dave Love <fx@gnu.org>
parents:
diff changeset
853 had a fatal signal.
Dave Love <fx@gnu.org>
parents:
diff changeset
854
35874
99572fa1c8c3 Remove the more arcane part of Emacs debug instructions. Replace
Eli Zaretskii <eliz@gnu.org>
parents: 35705
diff changeset
855 @cindex debugging Emacs, tricks and techniques
99572fa1c8c3 Remove the more arcane part of Emacs debug instructions. Replace
Eli Zaretskii <eliz@gnu.org>
parents: 35705
diff changeset
856 More detailed advice and other useful techniques for debugging Emacs
99572fa1c8c3 Remove the more arcane part of Emacs debug instructions. Replace
Eli Zaretskii <eliz@gnu.org>
parents: 35705
diff changeset
857 are available in the file @file{etc/DEBUG} in the Emacs distribution.
99572fa1c8c3 Remove the more arcane part of Emacs debug instructions. Replace
Eli Zaretskii <eliz@gnu.org>
parents: 35705
diff changeset
858 That file also includes instructions for investigating problems
99572fa1c8c3 Remove the more arcane part of Emacs debug instructions. Replace
Eli Zaretskii <eliz@gnu.org>
parents: 35705
diff changeset
859 whereby Emacs stops responding (many people assume that Emacs is
36180
252e21b04fb1 Suggest copying problematical manual text into the bug report.
Richard M. Stallman <rms@gnu.org>
parents: 35874
diff changeset
860 ``hung,'' whereas in fact it might be in an infinite loop).
25829
Dave Love <fx@gnu.org>
parents:
diff changeset
861
38130
7aad2fda759d Update how to find etc/DEBUG.
Richard M. Stallman <rms@gnu.org>
parents: 37976
diff changeset
862 To find the file @file{etc/DEBUG} in your Emacs installation, use the
7aad2fda759d Update how to find etc/DEBUG.
Richard M. Stallman <rms@gnu.org>
parents: 37976
diff changeset
863 directory name stored in the variable @code{data-directory}.
25829
Dave Love <fx@gnu.org>
parents:
diff changeset
864 @end itemize
Dave Love <fx@gnu.org>
parents:
diff changeset
865
Dave Love <fx@gnu.org>
parents:
diff changeset
866 Here are some things that are not necessary in a bug report:
Dave Love <fx@gnu.org>
parents:
diff changeset
867
Dave Love <fx@gnu.org>
parents:
diff changeset
868 @itemize @bullet
Dave Love <fx@gnu.org>
parents:
diff changeset
869 @item
Dave Love <fx@gnu.org>
parents:
diff changeset
870 A description of the envelope of the bug---this is not necessary for a
Dave Love <fx@gnu.org>
parents:
diff changeset
871 reproducible bug.
Dave Love <fx@gnu.org>
parents:
diff changeset
872
Dave Love <fx@gnu.org>
parents:
diff changeset
873 Often people who encounter a bug spend a lot of time investigating
Dave Love <fx@gnu.org>
parents:
diff changeset
874 which changes to the input file will make the bug go away and which
Dave Love <fx@gnu.org>
parents:
diff changeset
875 changes will not affect it.
Dave Love <fx@gnu.org>
parents:
diff changeset
876
Dave Love <fx@gnu.org>
parents:
diff changeset
877 This is often time-consuming and not very useful, because the way we
38130
7aad2fda759d Update how to find etc/DEBUG.
Richard M. Stallman <rms@gnu.org>
parents: 37976
diff changeset
878 will find the bug is by running a single example under the debugger
7aad2fda759d Update how to find etc/DEBUG.
Richard M. Stallman <rms@gnu.org>
parents: 37976
diff changeset
879 with breakpoints, not by pure deduction from a series of examples.
7aad2fda759d Update how to find etc/DEBUG.
Richard M. Stallman <rms@gnu.org>
parents: 37976
diff changeset
880 You might as well save time by not searching for additional examples.
7aad2fda759d Update how to find etc/DEBUG.
Richard M. Stallman <rms@gnu.org>
parents: 37976
diff changeset
881 It is better to send the bug report right away, go back to editing,
7aad2fda759d Update how to find etc/DEBUG.
Richard M. Stallman <rms@gnu.org>
parents: 37976
diff changeset
882 and find another bug to report.
25829
Dave Love <fx@gnu.org>
parents:
diff changeset
883
Dave Love <fx@gnu.org>
parents:
diff changeset
884 Of course, if you can find a simpler example to report @emph{instead} of
Dave Love <fx@gnu.org>
parents:
diff changeset
885 the original one, that is a convenience. Errors in the output will be
Dave Love <fx@gnu.org>
parents:
diff changeset
886 easier to spot, running under the debugger will take less time, etc.
Dave Love <fx@gnu.org>
parents:
diff changeset
887
Dave Love <fx@gnu.org>
parents:
diff changeset
888 However, simplification is not vital; if you can't do this or don't have
Dave Love <fx@gnu.org>
parents:
diff changeset
889 time to try, please report the bug with your original test case.
Dave Love <fx@gnu.org>
parents:
diff changeset
890
Dave Love <fx@gnu.org>
parents:
diff changeset
891 @item
38230
ec2015ba505d Explain why don't mail a core dump.
Richard M. Stallman <rms@gnu.org>
parents: 38130
diff changeset
892 A core dump file.
ec2015ba505d Explain why don't mail a core dump.
Richard M. Stallman <rms@gnu.org>
parents: 38130
diff changeset
893
ec2015ba505d Explain why don't mail a core dump.
Richard M. Stallman <rms@gnu.org>
parents: 38130
diff changeset
894 Debugging the core dump might be useful, but it can only be done on
ec2015ba505d Explain why don't mail a core dump.
Richard M. Stallman <rms@gnu.org>
parents: 38130
diff changeset
895 your machine, with your Emacs executable. Therefore, sending the core
ec2015ba505d Explain why don't mail a core dump.
Richard M. Stallman <rms@gnu.org>
parents: 38130
diff changeset
896 dump file to the Emacs maintainers won't be useful. Above all, don't
ec2015ba505d Explain why don't mail a core dump.
Richard M. Stallman <rms@gnu.org>
parents: 38130
diff changeset
897 include the core file in an email bug report! Such a large message
ec2015ba505d Explain why don't mail a core dump.
Richard M. Stallman <rms@gnu.org>
parents: 38130
diff changeset
898 can be extremely inconvenient.
ec2015ba505d Explain why don't mail a core dump.
Richard M. Stallman <rms@gnu.org>
parents: 38130
diff changeset
899
ec2015ba505d Explain why don't mail a core dump.
Richard M. Stallman <rms@gnu.org>
parents: 38130
diff changeset
900 @item
25829
Dave Love <fx@gnu.org>
parents:
diff changeset
901 A system-call trace of Emacs execution.
Dave Love <fx@gnu.org>
parents:
diff changeset
902
Dave Love <fx@gnu.org>
parents:
diff changeset
903 System-call traces are very useful for certain special kinds of
Dave Love <fx@gnu.org>
parents:
diff changeset
904 debugging, but in most cases they give little useful information. It is
Dave Love <fx@gnu.org>
parents:
diff changeset
905 therefore strange that many people seem to think that @emph{the} way to
Dave Love <fx@gnu.org>
parents:
diff changeset
906 report information about a crash is to send a system-call trace. Perhaps
Dave Love <fx@gnu.org>
parents:
diff changeset
907 this is a habit formed from experience debugging programs that don't
Dave Love <fx@gnu.org>
parents:
diff changeset
908 have source code or debugging symbols.
Dave Love <fx@gnu.org>
parents:
diff changeset
909
Dave Love <fx@gnu.org>
parents:
diff changeset
910 In most programs, a backtrace is normally far, far more informative than
Dave Love <fx@gnu.org>
parents:
diff changeset
911 a system-call trace. Even in Emacs, a simple backtrace is generally
Dave Love <fx@gnu.org>
parents:
diff changeset
912 more informative, though to give full information you should supplement
Dave Love <fx@gnu.org>
parents:
diff changeset
913 the backtrace by displaying variable values and printing them as Lisp
Dave Love <fx@gnu.org>
parents:
diff changeset
914 objects with @code{pr} (see above).
Dave Love <fx@gnu.org>
parents:
diff changeset
915
Dave Love <fx@gnu.org>
parents:
diff changeset
916 @item
Dave Love <fx@gnu.org>
parents:
diff changeset
917 A patch for the bug.
Dave Love <fx@gnu.org>
parents:
diff changeset
918
Dave Love <fx@gnu.org>
parents:
diff changeset
919 A patch for the bug is useful if it is a good one. But don't omit the
Dave Love <fx@gnu.org>
parents:
diff changeset
920 other information that a bug report needs, such as the test case, on the
Dave Love <fx@gnu.org>
parents:
diff changeset
921 assumption that a patch is sufficient. We might see problems with your
Dave Love <fx@gnu.org>
parents:
diff changeset
922 patch and decide to fix the problem another way, or we might not
Dave Love <fx@gnu.org>
parents:
diff changeset
923 understand it at all. And if we can't understand what bug you are
Dave Love <fx@gnu.org>
parents:
diff changeset
924 trying to fix, or why your patch should be an improvement, we mustn't
Dave Love <fx@gnu.org>
parents:
diff changeset
925 install it.
Dave Love <fx@gnu.org>
parents:
diff changeset
926
Dave Love <fx@gnu.org>
parents:
diff changeset
927 @ifinfo
Dave Love <fx@gnu.org>
parents:
diff changeset
928 @xref{Sending Patches}, for guidelines on how to make it easy for us to
Dave Love <fx@gnu.org>
parents:
diff changeset
929 understand and install your patches.
Dave Love <fx@gnu.org>
parents:
diff changeset
930 @end ifinfo
Dave Love <fx@gnu.org>
parents:
diff changeset
931
Dave Love <fx@gnu.org>
parents:
diff changeset
932 @item
Dave Love <fx@gnu.org>
parents:
diff changeset
933 A guess about what the bug is or what it depends on.
Dave Love <fx@gnu.org>
parents:
diff changeset
934
Dave Love <fx@gnu.org>
parents:
diff changeset
935 Such guesses are usually wrong. Even experts can't guess right about
Dave Love <fx@gnu.org>
parents:
diff changeset
936 such things without first using the debugger to find the facts.
Dave Love <fx@gnu.org>
parents:
diff changeset
937 @end itemize
Dave Love <fx@gnu.org>
parents:
diff changeset
938
Dave Love <fx@gnu.org>
parents:
diff changeset
939 @node Sending Patches
Dave Love <fx@gnu.org>
parents:
diff changeset
940 @subsection Sending Patches for GNU Emacs
Dave Love <fx@gnu.org>
parents:
diff changeset
941
Dave Love <fx@gnu.org>
parents:
diff changeset
942 @cindex sending patches for GNU Emacs
Dave Love <fx@gnu.org>
parents:
diff changeset
943 @cindex patches, sending
Dave Love <fx@gnu.org>
parents:
diff changeset
944 If you would like to write bug fixes or improvements for GNU Emacs,
Dave Love <fx@gnu.org>
parents:
diff changeset
945 that is very helpful. When you send your changes, please follow these
Dave Love <fx@gnu.org>
parents:
diff changeset
946 guidelines to make it easy for the maintainers to use them. If you
Dave Love <fx@gnu.org>
parents:
diff changeset
947 don't follow these guidelines, your information might still be useful,
Dave Love <fx@gnu.org>
parents:
diff changeset
948 but using it will take extra work. Maintaining GNU Emacs is a lot of
Dave Love <fx@gnu.org>
parents:
diff changeset
949 work in the best of circumstances, and we can't keep up unless you do
Dave Love <fx@gnu.org>
parents:
diff changeset
950 your best to help.
Dave Love <fx@gnu.org>
parents:
diff changeset
951
Dave Love <fx@gnu.org>
parents:
diff changeset
952 @itemize @bullet
Dave Love <fx@gnu.org>
parents:
diff changeset
953 @item
Dave Love <fx@gnu.org>
parents:
diff changeset
954 Send an explanation with your changes of what problem they fix or what
Dave Love <fx@gnu.org>
parents:
diff changeset
955 improvement they bring about. For a bug fix, just include a copy of the
Dave Love <fx@gnu.org>
parents:
diff changeset
956 bug report, and explain why the change fixes the bug.
Dave Love <fx@gnu.org>
parents:
diff changeset
957
Dave Love <fx@gnu.org>
parents:
diff changeset
958 (Referring to a bug report is not as good as including it, because then
Dave Love <fx@gnu.org>
parents:
diff changeset
959 we will have to look it up, and we have probably already deleted it if
Dave Love <fx@gnu.org>
parents:
diff changeset
960 we've already fixed the bug.)
Dave Love <fx@gnu.org>
parents:
diff changeset
961
Dave Love <fx@gnu.org>
parents:
diff changeset
962 @item
Dave Love <fx@gnu.org>
parents:
diff changeset
963 Always include a proper bug report for the problem you think you have
Dave Love <fx@gnu.org>
parents:
diff changeset
964 fixed. We need to convince ourselves that the change is right before
Dave Love <fx@gnu.org>
parents:
diff changeset
965 installing it. Even if it is correct, we might have trouble
Dave Love <fx@gnu.org>
parents:
diff changeset
966 understanding it if we don't have a way to reproduce the problem.
Dave Love <fx@gnu.org>
parents:
diff changeset
967
Dave Love <fx@gnu.org>
parents:
diff changeset
968 @item
Dave Love <fx@gnu.org>
parents:
diff changeset
969 Include all the comments that are appropriate to help people reading the
Dave Love <fx@gnu.org>
parents:
diff changeset
970 source in the future understand why this change was needed.
Dave Love <fx@gnu.org>
parents:
diff changeset
971
Dave Love <fx@gnu.org>
parents:
diff changeset
972 @item
Dave Love <fx@gnu.org>
parents:
diff changeset
973 Don't mix together changes made for different reasons.
Dave Love <fx@gnu.org>
parents:
diff changeset
974 Send them @emph{individually}.
Dave Love <fx@gnu.org>
parents:
diff changeset
975
Dave Love <fx@gnu.org>
parents:
diff changeset
976 If you make two changes for separate reasons, then we might not want to
Dave Love <fx@gnu.org>
parents:
diff changeset
977 install them both. We might want to install just one. If you send them
Dave Love <fx@gnu.org>
parents:
diff changeset
978 all jumbled together in a single set of diffs, we have to do extra work
Dave Love <fx@gnu.org>
parents:
diff changeset
979 to disentangle them---to figure out which parts of the change serve
Dave Love <fx@gnu.org>
parents:
diff changeset
980 which purpose. If we don't have time for this, we might have to ignore
Dave Love <fx@gnu.org>
parents:
diff changeset
981 your changes entirely.
Dave Love <fx@gnu.org>
parents:
diff changeset
982
Dave Love <fx@gnu.org>
parents:
diff changeset
983 If you send each change as soon as you have written it, with its own
Dave Love <fx@gnu.org>
parents:
diff changeset
984 explanation, then two changes never get tangled up, and we can consider
Dave Love <fx@gnu.org>
parents:
diff changeset
985 each one properly without any extra work to disentangle them.
Dave Love <fx@gnu.org>
parents:
diff changeset
986
Dave Love <fx@gnu.org>
parents:
diff changeset
987 @item
Dave Love <fx@gnu.org>
parents:
diff changeset
988 Send each change as soon as that change is finished. Sometimes people
Dave Love <fx@gnu.org>
parents:
diff changeset
989 think they are helping us by accumulating many changes to send them all
Dave Love <fx@gnu.org>
parents:
diff changeset
990 together. As explained above, this is absolutely the worst thing you
Dave Love <fx@gnu.org>
parents:
diff changeset
991 could do.
Dave Love <fx@gnu.org>
parents:
diff changeset
992
Dave Love <fx@gnu.org>
parents:
diff changeset
993 Since you should send each change separately, you might as well send it
Dave Love <fx@gnu.org>
parents:
diff changeset
994 right away. That gives us the option of installing it immediately if it
Dave Love <fx@gnu.org>
parents:
diff changeset
995 is important.
Dave Love <fx@gnu.org>
parents:
diff changeset
996
Dave Love <fx@gnu.org>
parents:
diff changeset
997 @item
Dave Love <fx@gnu.org>
parents:
diff changeset
998 Use @samp{diff -c} to make your diffs. Diffs without context are hard
Dave Love <fx@gnu.org>
parents:
diff changeset
999 to install reliably. More than that, they are hard to study; we must
Dave Love <fx@gnu.org>
parents:
diff changeset
1000 always study a patch to decide whether we want to install it. Unidiff
Dave Love <fx@gnu.org>
parents:
diff changeset
1001 format is better than contextless diffs, but not as easy to read as
Dave Love <fx@gnu.org>
parents:
diff changeset
1002 @samp{-c} format.
Dave Love <fx@gnu.org>
parents:
diff changeset
1003
Dave Love <fx@gnu.org>
parents:
diff changeset
1004 If you have GNU diff, use @samp{diff -c -F'^[_a-zA-Z0-9$]+ *('} when
Dave Love <fx@gnu.org>
parents:
diff changeset
1005 making diffs of C code. This shows the name of the function that each
Dave Love <fx@gnu.org>
parents:
diff changeset
1006 change occurs in.
Dave Love <fx@gnu.org>
parents:
diff changeset
1007
Dave Love <fx@gnu.org>
parents:
diff changeset
1008 @item
Dave Love <fx@gnu.org>
parents:
diff changeset
1009 Avoid any ambiguity as to which is the old version and which is the new.
Dave Love <fx@gnu.org>
parents:
diff changeset
1010 Please make the old version the first argument to diff, and the new
Dave Love <fx@gnu.org>
parents:
diff changeset
1011 version the second argument. And please give one version or the other a
Dave Love <fx@gnu.org>
parents:
diff changeset
1012 name that indicates whether it is the old version or your new changed
Dave Love <fx@gnu.org>
parents:
diff changeset
1013 one.
Dave Love <fx@gnu.org>
parents:
diff changeset
1014
Dave Love <fx@gnu.org>
parents:
diff changeset
1015 @item
Dave Love <fx@gnu.org>
parents:
diff changeset
1016 Write the change log entries for your changes. This is both to save us
Dave Love <fx@gnu.org>
parents:
diff changeset
1017 the extra work of writing them, and to help explain your changes so we
Dave Love <fx@gnu.org>
parents:
diff changeset
1018 can understand them.
Dave Love <fx@gnu.org>
parents:
diff changeset
1019
Dave Love <fx@gnu.org>
parents:
diff changeset
1020 The purpose of the change log is to show people where to find what was
Dave Love <fx@gnu.org>
parents:
diff changeset
1021 changed. So you need to be specific about what functions you changed;
Dave Love <fx@gnu.org>
parents:
diff changeset
1022 in large functions, it's often helpful to indicate where within the
Dave Love <fx@gnu.org>
parents:
diff changeset
1023 function the change was.
Dave Love <fx@gnu.org>
parents:
diff changeset
1024
Dave Love <fx@gnu.org>
parents:
diff changeset
1025 On the other hand, once you have shown people where to find the change,
Dave Love <fx@gnu.org>
parents:
diff changeset
1026 you need not explain its purpose in the change log. Thus, if you add a
Dave Love <fx@gnu.org>
parents:
diff changeset
1027 new function, all you need to say about it is that it is new. If you
Dave Love <fx@gnu.org>
parents:
diff changeset
1028 feel that the purpose needs explaining, it probably does---but put the
Dave Love <fx@gnu.org>
parents:
diff changeset
1029 explanation in comments in the code. It will be more useful there.
Dave Love <fx@gnu.org>
parents:
diff changeset
1030
Dave Love <fx@gnu.org>
parents:
diff changeset
1031 Please read the @file{ChangeLog} files in the @file{src} and @file{lisp}
Dave Love <fx@gnu.org>
parents:
diff changeset
1032 directories to see what sorts of information to put in, and to learn the
Dave Love <fx@gnu.org>
parents:
diff changeset
1033 style that we use. If you would like your name to appear in the header
Dave Love <fx@gnu.org>
parents:
diff changeset
1034 line, showing who made the change, send us the header line.
Dave Love <fx@gnu.org>
parents:
diff changeset
1035 @xref{Change Log}.
Dave Love <fx@gnu.org>
parents:
diff changeset
1036
Dave Love <fx@gnu.org>
parents:
diff changeset
1037 @item
Dave Love <fx@gnu.org>
parents:
diff changeset
1038 When you write the fix, keep in mind that we can't install a change that
Dave Love <fx@gnu.org>
parents:
diff changeset
1039 would break other systems. Please think about what effect your change
Dave Love <fx@gnu.org>
parents:
diff changeset
1040 will have if compiled on another type of system.
Dave Love <fx@gnu.org>
parents:
diff changeset
1041
Dave Love <fx@gnu.org>
parents:
diff changeset
1042 Sometimes people send fixes that @emph{might} be an improvement in
Dave Love <fx@gnu.org>
parents:
diff changeset
1043 general---but it is hard to be sure of this. It's hard to install
Dave Love <fx@gnu.org>
parents:
diff changeset
1044 such changes because we have to study them very carefully. Of course,
Dave Love <fx@gnu.org>
parents:
diff changeset
1045 a good explanation of the reasoning by which you concluded the change
Dave Love <fx@gnu.org>
parents:
diff changeset
1046 was correct can help convince us.
Dave Love <fx@gnu.org>
parents:
diff changeset
1047
Dave Love <fx@gnu.org>
parents:
diff changeset
1048 The safest changes are changes to the configuration files for a
Dave Love <fx@gnu.org>
parents:
diff changeset
1049 particular machine. These are safe because they can't create new bugs
Dave Love <fx@gnu.org>
parents:
diff changeset
1050 on other machines.
Dave Love <fx@gnu.org>
parents:
diff changeset
1051
Dave Love <fx@gnu.org>
parents:
diff changeset
1052 Please help us keep up with the workload by designing the patch in a
Dave Love <fx@gnu.org>
parents:
diff changeset
1053 form that is clearly safe to install.
Dave Love <fx@gnu.org>
parents:
diff changeset
1054 @end itemize
Dave Love <fx@gnu.org>
parents:
diff changeset
1055
Dave Love <fx@gnu.org>
parents:
diff changeset
1056 @node Contributing, Service, Bugs, Top
Dave Love <fx@gnu.org>
parents:
diff changeset
1057 @section Contributing to Emacs Development
Dave Love <fx@gnu.org>
parents:
diff changeset
1058
Dave Love <fx@gnu.org>
parents:
diff changeset
1059 If you would like to help pretest Emacs releases to assure they work
Dave Love <fx@gnu.org>
parents:
diff changeset
1060 well, or if you would like to work on improving Emacs, please contact
60342
0f12295e50a4 (Contributing): Mention Savannah. Direct users to
Nick Roberts <nickrob@snap.net.nz>
parents: 60121
diff changeset
1061 the maintainers at @email{emacs-devel@@gnu.org}. A pretester
25829
Dave Love <fx@gnu.org>
parents:
diff changeset
1062 should be prepared to investigate bugs as well as report them. If you'd
Dave Love <fx@gnu.org>
parents:
diff changeset
1063 like to work on improving Emacs, please ask for suggested projects or
Dave Love <fx@gnu.org>
parents:
diff changeset
1064 suggest your own ideas.
Dave Love <fx@gnu.org>
parents:
diff changeset
1065
Dave Love <fx@gnu.org>
parents:
diff changeset
1066 If you have already written an improvement, please tell us about it. If
Dave Love <fx@gnu.org>
parents:
diff changeset
1067 you have not yet started work, it is useful to contact
60342
0f12295e50a4 (Contributing): Mention Savannah. Direct users to
Nick Roberts <nickrob@snap.net.nz>
parents: 60121
diff changeset
1068 @email{emacs-devel@@gnu.org} before you start; it might be
25829
Dave Love <fx@gnu.org>
parents:
diff changeset
1069 possible to suggest ways to make your extension fit in better with the
Dave Love <fx@gnu.org>
parents:
diff changeset
1070 rest of Emacs.
Dave Love <fx@gnu.org>
parents:
diff changeset
1071
60342
0f12295e50a4 (Contributing): Mention Savannah. Direct users to
Nick Roberts <nickrob@snap.net.nz>
parents: 60121
diff changeset
1072 The development version of Emacs can be downloaded from the CVS
0f12295e50a4 (Contributing): Mention Savannah. Direct users to
Nick Roberts <nickrob@snap.net.nz>
parents: 60121
diff changeset
1073 repository where it is actively maintained by a group of developers.
0f12295e50a4 (Contributing): Mention Savannah. Direct users to
Nick Roberts <nickrob@snap.net.nz>
parents: 60121
diff changeset
1074 See the Emacs project page http://savannah.gnu.org/projects/emacs/ for
0f12295e50a4 (Contributing): Mention Savannah. Direct users to
Nick Roberts <nickrob@snap.net.nz>
parents: 60121
diff changeset
1075 details.
0f12295e50a4 (Contributing): Mention Savannah. Direct users to
Nick Roberts <nickrob@snap.net.nz>
parents: 60121
diff changeset
1076
56812
16152de85a64 Adapt sectioning in Info to the node structure.
Luc Teirlinck <teirllm@auburn.edu>
parents: 54478
diff changeset
1077 @node Service, Copying, Contributing, Top
25829
Dave Love <fx@gnu.org>
parents:
diff changeset
1078 @section How To Get Help with GNU Emacs
Dave Love <fx@gnu.org>
parents:
diff changeset
1079
Dave Love <fx@gnu.org>
parents:
diff changeset
1080 If you need help installing, using or changing GNU Emacs, there are two
Dave Love <fx@gnu.org>
parents:
diff changeset
1081 ways to find it:
Dave Love <fx@gnu.org>
parents:
diff changeset
1082
Dave Love <fx@gnu.org>
parents:
diff changeset
1083 @itemize @bullet
Dave Love <fx@gnu.org>
parents:
diff changeset
1084 @item
Dave Love <fx@gnu.org>
parents:
diff changeset
1085 Send a message to the mailing list
29107
203ba1f77b7b *** empty log message ***
Gerd Moellmann <gerd@gnu.org>
parents: 27729
diff changeset
1086 @email{help-gnu-emacs@@gnu.org}, or post your request on
25829
Dave Love <fx@gnu.org>
parents:
diff changeset
1087 newsgroup @code{gnu.emacs.help}. (This mailing list and newsgroup
Dave Love <fx@gnu.org>
parents:
diff changeset
1088 interconnect, so it does not matter which one you use.)
Dave Love <fx@gnu.org>
parents:
diff changeset
1089
Dave Love <fx@gnu.org>
parents:
diff changeset
1090 @item
Dave Love <fx@gnu.org>
parents:
diff changeset
1091 Look in the service directory for someone who might help you for a fee.
Dave Love <fx@gnu.org>
parents:
diff changeset
1092 The service directory is found in the file named @file{etc/SERVICE} in the
Dave Love <fx@gnu.org>
parents:
diff changeset
1093 Emacs distribution.
Dave Love <fx@gnu.org>
parents:
diff changeset
1094 @end itemize
52401
695cf19ef79e Add arch taglines
Miles Bader <miles@gnu.org>
parents: 49600
diff changeset
1095
56812
16152de85a64 Adapt sectioning in Info to the node structure.
Luc Teirlinck <teirllm@auburn.edu>
parents: 54478
diff changeset
1096 @ifnottex
16152de85a64 Adapt sectioning in Info to the node structure.
Luc Teirlinck <teirllm@auburn.edu>
parents: 54478
diff changeset
1097 @lowersections
16152de85a64 Adapt sectioning in Info to the node structure.
Luc Teirlinck <teirllm@auburn.edu>
parents: 54478
diff changeset
1098 @end ifnottex
16152de85a64 Adapt sectioning in Info to the node structure.
Luc Teirlinck <teirllm@auburn.edu>
parents: 54478
diff changeset
1099
52401
695cf19ef79e Add arch taglines
Miles Bader <miles@gnu.org>
parents: 49600
diff changeset
1100 @ignore
695cf19ef79e Add arch taglines
Miles Bader <miles@gnu.org>
parents: 49600
diff changeset
1101 arch-tag: c9cba76d-b2cb-4e0c-ae3f-19d5ef35817c
695cf19ef79e Add arch taglines
Miles Bader <miles@gnu.org>
parents: 49600
diff changeset
1102 @end ignore