Mercurial > emacs
comparison man/trouble.texi @ 37347:bd817d6f9ba3
Minor clarifications regarding DEL key.
Mention toggle-debug-on-error.
author | Richard M. Stallman <rms@gnu.org> |
---|---|
date | Sat, 14 Apr 2001 14:48:01 +0000 |
parents | 6a2d75e45a87 |
children | ad563f9185fb |
comparison
equal
deleted
inserted
replaced
37346:e80fc3e25af8 | 37347:bd817d6f9ba3 |
---|---|
142 @cindex usual erasure key | 142 @cindex usual erasure key |
143 | 143 |
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 |
146 last character that you typed. We call this key @dfn{the usual | 146 last character that you typed. We call this key @dfn{the usual |
147 erasure key}. In Emacs, it is supposed to be equivalent to @key{DEL}. | 147 erasure key}. In Emacs, it is supposed to be equivalent to @key{DEL}, |
148 and when Emacs is properly configured for your terminal, it translates | |
149 that 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 |
150 automatically which key should be @key{DEL}. In some unusual cases | 152 automatically which key should be @key{DEL}. In some unusual cases |
151 Emacs gets the wrong information from the system. If the usual | 153 Emacs gets the wrong information from the system. If the usual |
152 erasure key deletes forwards instead of backwards, that is probably | 154 erasure key deletes forwards instead of backwards, that is probably |
166 character. Emacs ought to be treating @key{BS} as @key{DEL}, but it | 168 character. Emacs ought to be treating @key{BS} as @key{DEL}, but it |
167 isn't. | 169 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 |
170 command @kbd{M-x normal-erase-is-backspace-mode}. That should make | 172 command @kbd{M-x normal-erase-is-backspace-mode}. That should make |
171 the proper @key{DEL} key work. On a text-only terminal, if you do | 173 the proper key work as @key{DEL}. On a text-only terminal, if you do |
172 want to ask for help, use @key{F1} or @kbd{C-?}. | 174 want 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 |
175 To fix the problem automatically for every Emacs session, you can | 177 To fix the problem automatically for every Emacs session, you can |
176 put one of the following lines into your @file{.emacs} file | 178 put one of the following lines into your @file{.emacs} file |
701 | 703 |
702 To get the error message text accurately, copy it from the | 704 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 |
704 part. | 706 part. |
705 | 707 |
706 To 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 | 709 To make a backtrace for the error, use @kbd{M-x toggle-debug-on-error} |
708 say, you must execute that expression and then make the bug happen). | 710 before the error happens (that is to say, you must give that command |
709 This causes the error to run the Lisp debugger, which shows you a | 711 and then make the bug happen). This causes the error to run the Lisp |
710 backtrace. Copy the text of the debugger's backtrace into the bug | 712 debugger, which shows you a backtrace. Copy the text of the |
711 report. | 713 debugger's backtrace into the bug report. @xref{Debugger,, The Lisp |
714 Debugger, elisp, the Emacs Lisp Reference Manual}, for information on | |
715 debugging Emacs Lisp programs. | |
712 | 716 |
713 This use of the debugger is possible only if you know how to make the | 717 This use of the debugger is possible only if you know how to make the |
714 bug happen again. If you can't make it happen again, at least copy | 718 bug happen again. If you can't make it happen again, at least copy |
715 the whole error message. | 719 the whole error message. |
716 | 720 |