Mercurial > emacs
comparison man/trouble.texi @ 37498:0b7a984464cf
Clarify when C-? is available as Help.
Explain that normal-erase-is-backspace-mode toggles between the two modes.
Describe the case where BACKSPACE has been remapped to DELETE
in the window system.
author | Richard M. Stallman <rms@gnu.org> |
---|---|
date | Thu, 26 Apr 2001 19:46:26 +0000 |
parents | ad563f9185fb |
children | e2849d417d6d |
comparison
equal
deleted
inserted
replaced
37497:b04b5ca14967 | 37498:0b7a984464cf |
---|---|
167 character, it means that key is actually sending the @key{BS} | 167 character, it means that key is actually sending the @key{BS} |
168 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 |
169 isn't. | 169 isn't. |
170 | 170 |
171 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 |
172 command @kbd{M-x normal-erase-is-backspace-mode}. That should make | 172 command @kbd{M-x normal-erase-is-backspace-mode}. This toggles |
173 the proper key work as @key{DEL}. On a text-only terminal, if you do | 173 between the two modes that Emacs supports for handling @key{DEL}, so |
174 want to ask for help, use @key{F1} or @kbd{C-?}. | 174 if Emacs starts in the wrong mode, it should switch to the right mode. |
175 On a text-only terminal, if you want to ask for help when @key{BS} is | |
176 treated as @key{DEL}, use @key{F1}; @kbd{C-?} may also work, if it | |
177 sends character code 127. | |
175 | 178 |
176 @findex normal-erase-is-backspace-mode | 179 @findex normal-erase-is-backspace-mode |
177 To fix the problem automatically for every Emacs session, you can | 180 To fix the problem automatically for every Emacs session, you can |
178 put one of the following lines into your @file{.emacs} file | 181 put one of the following lines into your @file{.emacs} file |
179 (@pxref{Init File}). For the first case above, where @key{DELETE} | 182 (@pxref{Init File}). For the first case above, where @key{DELETE} |
180 deletes forwards instead of backwards, use this line to make | 183 deletes forwards instead of backwards, use this line to make |
181 @key{DELETE} act as @key{DEL}: | 184 @key{DELETE} act as @key{DEL} (resulting in behavior compatible |
185 with Emacs 20 and previous versions): | |
182 | 186 |
183 @lisp | 187 @lisp |
184 (normal-erase-is-backspace-mode 0) | 188 (normal-erase-is-backspace-mode 0) |
185 @end lisp | 189 @end lisp |
186 | 190 |
196 Another way to fix the problem for every Emacs session is to | 200 Another way to fix the problem for every Emacs session is to |
197 customize the variable @code{normal-erase-is-backspace}: the value | 201 customize the variable @code{normal-erase-is-backspace}: the value |
198 @code{t} specifies the mode where @key{BS} or @key{BACKSPACE} is | 202 @code{t} specifies the mode where @key{BS} or @key{BACKSPACE} is |
199 @key{DEL}, and @code{nil} specifies the other mode. @xref{Easy | 203 @key{DEL}, and @code{nil} specifies the other mode. @xref{Easy |
200 Customization}. | 204 Customization}. |
205 | |
206 With a window system, it can also happen that the usual erasure key | |
207 is labeled @key{BACKSPACE}, there is a @key{DELETE} key elsewhere, and | |
208 both keys delete forward. This probably means that someone has | |
209 redefined your @key{BACKSPACE} key as a @key{DELETE} key. With X, | |
210 this is typically done with a command to the @code{xmodmap} program | |
211 when you start the server or log in. The most likely motive for this | |
212 customization was to support old versions of Emacs, so we recommend | |
213 you simply remove it now. | |
201 | 214 |
202 @node Stuck Recursive | 215 @node Stuck Recursive |
203 @subsection Recursive Editing Levels | 216 @subsection Recursive Editing Levels |
204 | 217 |
205 Recursive editing levels are important and useful features of Emacs, but | 218 Recursive editing levels are important and useful features of Emacs, but |