aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorEli Zaretskii2014-05-02 15:28:10 +0300
committerEli Zaretskii2014-05-02 15:28:10 +0300
commita419eaa751695009cc4048b0efd97ad67bb84614 (patch)
tree7d17c29bd8ce049e6027ca68d6635d44639d935a
parent157e8cfdd80c31850b70b0c286d421a1c2094e5c (diff)
downloademacs-a419eaa751695009cc4048b0efd97ad67bb84614.tar.gz
emacs-a419eaa751695009cc4048b0efd97ad67bb84614.zip
Improve indexing in trouble-related sections of Emacs User manual.
doc/emacs/trouble.texi (Lossage, DEL Does Not Delete, Stuck Recursive) (Screen Garbled, Text Garbled, After a Crash, Emergency Escape) (Bug Criteria, Understanding Bug Reporting, Checklist, Service): Improve indexing.
-rw-r--r--doc/emacs/ChangeLog7
-rw-r--r--doc/emacs/trouble.texi22
2 files changed, 27 insertions, 2 deletions
diff --git a/doc/emacs/ChangeLog b/doc/emacs/ChangeLog
index 4aeac464208..a1e6dd8903f 100644
--- a/doc/emacs/ChangeLog
+++ b/doc/emacs/ChangeLog
@@ -1,3 +1,10 @@
12014-05-02 Eli Zaretskii <eliz@gnu.org>
2
3 * trouble.texi (Lossage, DEL Does Not Delete, Stuck Recursive)
4 (Screen Garbled, Text Garbled, After a Crash, Emergency Escape)
5 (Bug Criteria, Understanding Bug Reporting, Checklist, Service):
6 Improve indexing.
7
12014-04-29 Eli Zaretskii <eliz@gnu.org> 82014-04-29 Eli Zaretskii <eliz@gnu.org>
2 9
3 * trouble.texi (Quitting, DEL Does Not Delete, Emergency Escape) 10 * trouble.texi (Quitting, DEL Does Not Delete, Emergency Escape)
diff --git a/doc/emacs/trouble.texi b/doc/emacs/trouble.texi
index bf7c6175dcb..f0cbbcc5721 100644
--- a/doc/emacs/trouble.texi
+++ b/doc/emacs/trouble.texi
@@ -135,6 +135,7 @@ facility.
135 135
136@node Lossage 136@node Lossage
137@section Dealing with Emacs Trouble 137@section Dealing with Emacs Trouble
138@cindex troubleshooting Emacs
138 139
139 This section describes how to recognize and deal with situations in 140 This section describes how to recognize and deal with situations in
140which Emacs does not work as you expect, such as keyboard code mixups, 141which Emacs does not work as you expect, such as keyboard code mixups,
@@ -158,6 +159,7 @@ Emacs.
158@subsection If @key{DEL} Fails to Delete 159@subsection If @key{DEL} Fails to Delete
159@cindex @key{DEL} vs @key{BACKSPACE} 160@cindex @key{DEL} vs @key{BACKSPACE}
160@cindex @key{BACKSPACE} vs @key{DEL} 161@cindex @key{BACKSPACE} vs @key{DEL}
162@cindex @key{DEL} does not delete
161 163
162 Every keyboard has a large key, usually labeled @key{BACKSPACE}, 164 Every keyboard has a large key, usually labeled @key{BACKSPACE},
163which is ordinarily used to erase the last character that you typed. 165which is ordinarily used to erase the last character that you typed.
@@ -212,6 +214,8 @@ Customization}.
212 214
213@node Stuck Recursive 215@node Stuck Recursive
214@subsection Recursive Editing Levels 216@subsection Recursive Editing Levels
217@cindex stuck in recursive editing
218@cindex recursive editing, cannot exit
215 219
216 Recursive editing levels are important and useful features of Emacs, but 220 Recursive editing levels are important and useful features of Emacs, but
217they can seem like malfunctions if you do not understand them. 221they can seem like malfunctions if you do not understand them.
@@ -225,6 +229,9 @@ top-level}. @xref{Recursive Edit}.
225 229
226@node Screen Garbled 230@node Screen Garbled
227@subsection Garbage on the Screen 231@subsection Garbage on the Screen
232@cindex garbled display
233@cindex display, incorrect
234@cindex screen display, wrong
228 235
229 If the text on a text terminal looks wrong, the first thing to do is 236 If the text on a text terminal looks wrong, the first thing to do is
230see whether it is wrong in the buffer. Type @kbd{C-l} to redisplay 237see whether it is wrong in the buffer. Type @kbd{C-l} to redisplay
@@ -242,6 +249,8 @@ bug in Emacs that appears for certain terminal types.
242 249
243@node Text Garbled 250@node Text Garbled
244@subsection Garbage in the Text 251@subsection Garbage in the Text
252@cindex garbled text
253@cindex buffer text garbled
245 254
246 If @kbd{C-l} shows that the text is wrong, first type @kbd{C-h l} to 255 If @kbd{C-l} shows that the text is wrong, first type @kbd{C-h l} to
247see what commands you typed to produce the observed results. Then try 256see what commands you typed to produce the observed results. Then try
@@ -348,6 +357,7 @@ enable them by running the shell command @samp{ulimit -c unlimited}
348 357
349@node After a Crash 358@node After a Crash
350@subsection Recovery After a Crash 359@subsection Recovery After a Crash
360@cindex recovering crashed session
351 361
352 If Emacs or the computer crashes, you can recover the files you were 362 If Emacs or the computer crashes, you can recover the files you were
353editing at the time of the crash from their auto-save files. To do 363editing at the time of the crash from their auto-save files. To do
@@ -394,6 +404,7 @@ not make a backup of its old contents.
394 404
395@node Emergency Escape 405@node Emergency Escape
396@subsection Emergency Escape 406@subsection Emergency Escape
407@cindex emergency escape
397 408
398 On text terminals, the @dfn{emergency escape} feature suspends Emacs 409 On text terminals, the @dfn{emergency escape} feature suspends Emacs
399immediately if you type @kbd{C-g} a second time before Emacs can 410immediately if you type @kbd{C-g} a second time before Emacs can
@@ -528,6 +539,8 @@ not feel obliged to read this list before reporting a bug.
528 539
529@node Bug Criteria 540@node Bug Criteria
530@subsection When Is There a Bug 541@subsection When Is There a Bug
542@cindex bug criteria
543@cindex what constitutes an Emacs bug
531 544
532 If Emacs accesses an invalid memory location (``segmentation 545 If Emacs accesses an invalid memory location (``segmentation
533fault''), or exits with an operating system error message that 546fault''), or exits with an operating system error message that
@@ -580,6 +593,8 @@ with the manual, one of them must be wrong; that is a bug.
580 593
581@node Understanding Bug Reporting 594@node Understanding Bug Reporting
582@subsection Understanding Bug Reporting 595@subsection Understanding Bug Reporting
596@cindex bug reporting
597@cindex report an Emacs bug, how to
583 598
584@findex emacs-version 599@findex emacs-version
585 When you decide that there is a bug, it is important to report it 600 When you decide that there is a bug, it is important to report it
@@ -636,8 +651,8 @@ separate bug report for each.
636 651
637@node Checklist 652@node Checklist
638@subsection Checklist for Bug Reports 653@subsection Checklist for Bug Reports
639 654@cindex checklist before reporting a bug
640@cindex reporting bugs 655@cindex bug reporting, checklist
641 656
642 Before reporting a bug, first try to see if the problem has already 657 Before reporting a bug, first try to see if the problem has already
643been reported (@pxref{Known Problems}). 658been reported (@pxref{Known Problems}).
@@ -1192,6 +1207,9 @@ file in the Emacs distribution.
1192 1207
1193@node Service 1208@node Service
1194@section How To Get Help with GNU Emacs 1209@section How To Get Help with GNU Emacs
1210@cindex help in using Emacs
1211@cindex help-gnu-emacs mailing list
1212@cindex gnu.emacs.help newsgroup
1195 1213
1196If you need help installing, using or changing GNU Emacs, there are two 1214If you need help installing, using or changing GNU Emacs, there are two
1197ways to find it: 1215ways to find it: