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