aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorRichard M. Stallman2001-04-14 14:48:01 +0000
committerRichard M. Stallman2001-04-14 14:48:01 +0000
commit50556a88a68a714bc5765dbbe3596f45d77790b8 (patch)
tree22e381ee98343ac15f9b9fd6fc0d12af21208ce6
parentd952abded113290aaff37d2cb092a7935d627382 (diff)
downloademacs-50556a88a68a714bc5765dbbe3596f45d77790b8.tar.gz
emacs-50556a88a68a714bc5765dbbe3596f45d77790b8.zip
Minor clarifications regarding DEL key.
Mention toggle-debug-on-error.
-rw-r--r--man/trouble.texi20
1 files changed, 12 insertions, 8 deletions
diff --git a/man/trouble.texi b/man/trouble.texi
index 276a7a74a98..52aaa242642 100644
--- a/man/trouble.texi
+++ b/man/trouble.texi
@@ -144,7 +144,9 @@ normally, and how to recognize them and correct them.
144 Every keyboard has a large key, a little ways above the @key{RET} or 144 Every keyboard has a large key, a little ways above the @key{RET} or
145@key{ENTER} key, which you normally use outside Emacs to erase the 145@key{ENTER} key, which you normally use outside Emacs to erase the
146last character that you typed. We call this key @dfn{the usual 146last character that you typed. We call this key @dfn{the usual
147erasure key}. In Emacs, it is supposed to be equivalent to @key{DEL}. 147erasure key}. In Emacs, it is supposed to be equivalent to @key{DEL},
148and when Emacs is properly configured for your terminal, it translates
149that key into the character @key{DEL}.
148 150
149 When Emacs starts up using a window system, it determines 151 When Emacs starts up using a window system, it determines
150automatically which key should be @key{DEL}. In some unusual cases 152automatically which key should be @key{DEL}. In some unusual cases
@@ -168,7 +170,7 @@ isn't.
168 170
169 In all of those cases, the immediate remedy is the same: use the 171 In all of those cases, the immediate remedy is the same: use the
170command @kbd{M-x normal-erase-is-backspace-mode}. That should make 172command @kbd{M-x normal-erase-is-backspace-mode}. That should make
171the proper @key{DEL} key work. On a text-only terminal, if you do 173the proper key work as @key{DEL}. On a text-only terminal, if you do
172want to ask for help, use @key{F1} or @kbd{C-?}. 174want to ask for help, use @key{F1} or @kbd{C-?}.
173 175
174@findex normal-erase-is-backspace-mode 176@findex normal-erase-is-backspace-mode
@@ -703,12 +705,14 @@ To get the error message text accurately, copy it from the
703@samp{*Messages*} buffer into the bug report. Copy all of it, not just 705@samp{*Messages*} buffer into the bug report. Copy all of it, not just
704part. 706part.
705 707
706To make a backtrace for the error, evaluate the Lisp expression 708@findex toggle-debug-on-error
707@code{(setq @w{debug-on-error t})} before the error happens (that is to 709To make a backtrace for the error, use @kbd{M-x toggle-debug-on-error}
708say, you must execute that expression and then make the bug happen). 710before the error happens (that is to say, you must give that command
709This causes the error to run the Lisp debugger, which shows you a 711and then make the bug happen). This causes the error to run the Lisp
710backtrace. Copy the text of the debugger's backtrace into the bug 712debugger, which shows you a backtrace. Copy the text of the
711report. 713debugger's backtrace into the bug report. @xref{Debugger,, The Lisp
714Debugger, elisp, the Emacs Lisp Reference Manual}, for information on
715debugging Emacs Lisp programs.
712 716
713This use of the debugger is possible only if you know how to make the 717This use of the debugger is possible only if you know how to make the
714bug happen again. If you can't make it happen again, at least copy 718bug happen again. If you can't make it happen again, at least copy