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