diff options
| -rw-r--r-- | man/killing.texi | 25 | ||||
| -rw-r--r-- | man/trouble.texi | 12 |
2 files changed, 20 insertions, 17 deletions
diff --git a/man/killing.texi b/man/killing.texi index 2f36a0907d5..fb4c15077cf 100644 --- a/man/killing.texi +++ b/man/killing.texi | |||
| @@ -121,27 +121,28 @@ kill instead, since they can erase more than one character this way. | |||
| 121 | have typed. Regardless of the actual name on the key, in Emacs it is | 121 | have typed. Regardless of the actual name on the key, in Emacs it is |
| 122 | equivalent to @key{DEL}---or it should be. | 122 | equivalent to @key{DEL}---or it should be. |
| 123 | 123 | ||
| 124 | Many keyboards have a @key{BACKSPACE} key a short ways above | 124 | Many keyboards (including standard PC keyboards) have a |
| 125 | @key{RET} or @key{ENTER}, and a @key{DELETE} key elsewhere. In that | 125 | @key{BACKSPACE} key a short ways above @key{RET} or @key{ENTER}, and a |
| 126 | case, the @key{BACKSPACE} key is @key{DEL}, and the @key{DELETE} key | 126 | @key{DELETE} key elsewhere. In that case, the @key{BACKSPACE} key is |
| 127 | is equivalent to @kbd{C-d}---or it should be. | 127 | @key{DEL}, and the @key{DELETE} key is equivalent to @kbd{C-d}---or it |
| 128 | should be. | ||
| 128 | 129 | ||
| 129 | Why do we say ``or it should be''? When Emacs starts up using a | 130 | Why do we say ``or it should be''? When Emacs starts up using a |
| 130 | window system, it determines automatically which key or keys should be | 131 | window system, it determines automatically which key or keys should be |
| 131 | equivalent to @key{DEL}. So the @key{BACKSPACE} and/or @key{DELETE} | 132 | equivalent to @key{DEL}. So the @key{BACKSPACE} and/or @key{DELETE} |
| 132 | keys normally do the right things. But in some unusual cases Emacs | 133 | keys normally do the right things. But in some unusual cases Emacs |
| 133 | gets the wrong information from the system. If these keys don't do | 134 | gets the wrong information from the system. If these keys don't do |
| 134 | what they ought to do, you should tell Emacs which key to use for | 135 | what they ought to do, you need to tell Emacs which key to use for |
| 135 | @key{DEL}. @xref{DEL Gets Help}, for how to do this. | 136 | @key{DEL}. @xref{DEL Gets Help}, for how to do this. |
| 136 | 137 | ||
| 137 | @findex normal-erase-is-backspace-mode | 138 | @findex normal-erase-is-backspace-mode |
| 138 | On most text-only terminals, Emacs cannot tell which key is where, | 139 | On most text-only terminals, Emacs cannot tell which keys the |
| 139 | so it follows a uniform plan which may or may not fit your keyboard. | 140 | keyboard really has, so it follows a uniform plan which may or may not |
| 140 | The uniform plan is that the ASCII @key{DEL} character deletes, and | 141 | fit your keyboard. The uniform plan is that the ASCII @key{DEL} |
| 141 | the ASCII @key{BS} (backspace) character asks for help (it is the same | 142 | character deletes, and the ASCII @key{BS} (backspace) character asks |
| 142 | as @kbd{C-h}). If this is not right for your keyboard, if you find | 143 | for help (it is the same as @kbd{C-h}). If this is not right for your |
| 143 | that the key which ought to delete backwards enters Help instead, see | 144 | keyboard, if you find that the key which ought to delete backwards |
| 144 | @ref{DEL Gets Help}. | 145 | enters Help instead, see @ref{DEL Gets Help}. |
| 145 | 146 | ||
| 146 | @kindex M-\ | 147 | @kindex M-\ |
| 147 | @findex delete-horizontal-space | 148 | @findex delete-horizontal-space |
diff --git a/man/trouble.texi b/man/trouble.texi index 52aaa242642..7a9c942c604 100644 --- a/man/trouble.texi +++ b/man/trouble.texi | |||
| @@ -159,8 +159,8 @@ what happened---Emacs ought to be treating the @key{DELETE} key as | |||
| 159 | @key{BACKSPACE} and there is a @key{DELETE} key elsewhere, but the | 159 | @key{BACKSPACE} and there is a @key{DELETE} key elsewhere, but the |
| 160 | @key{DELETE} key deletes backward instead of forward, that too | 160 | @key{DELETE} key deletes backward instead of forward, that too |
| 161 | suggests Emacs got the wrong information---but in the opposite sense. | 161 | suggests Emacs got the wrong information---but in the opposite sense. |
| 162 | It ought to be treating the @key{BACKSPACE} key as @key{DEL}, but it | 162 | It ought to be treating the @key{BACKSPACE} key as @key{DEL}, and |
| 163 | isn't. | 163 | treating @key{DELETE} differently, but it isn't. |
| 164 | 164 | ||
| 165 | On a text-only terminal, if you find the usual erasure key prompts | 165 | On a text-only terminal, if you find the usual erasure key prompts |
| 166 | for a Help command, like @kbd{Control-h}, instead of deleting a | 166 | for a Help command, like @kbd{Control-h}, instead of deleting a |
| @@ -176,15 +176,17 @@ want to ask for help, use @key{F1} or @kbd{C-?}. | |||
| 176 | @findex normal-erase-is-backspace-mode | 176 | @findex normal-erase-is-backspace-mode |
| 177 | To fix the problem automatically for every Emacs session, you can | 177 | To fix the problem automatically for every Emacs session, you can |
| 178 | put one of the following lines into your @file{.emacs} file | 178 | put one of the following lines into your @file{.emacs} file |
| 179 | (@pxref{Init File}). For the first case above, where @key{DEL} | 179 | (@pxref{Init File}). For the first case above, where @key{DELETE} |
| 180 | deletes forwards instead of backwards, use this line: | 180 | deletes forwards instead of backwards, use this line to make |
| 181 | @key{DELETE} act as @key{DEL}: | ||
| 181 | 182 | ||
| 182 | @lisp | 183 | @lisp |
| 183 | (normal-erase-is-backspace-mode 0) | 184 | (normal-erase-is-backspace-mode 0) |
| 184 | @end lisp | 185 | @end lisp |
| 185 | 186 | ||
| 186 | @noindent | 187 | @noindent |
| 187 | For the other two cases, use this line: | 188 | For the other two cases, where @key{BACKSPACE} ought to act as |
| 189 | @key{DEL}, use this line: | ||
| 188 | 190 | ||
| 189 | @lisp | 191 | @lisp |
| 190 | (normal-erase-is-backspace-mode 1) | 192 | (normal-erase-is-backspace-mode 1) |