Mercurial > vim
comparison runtime/doc/term.txt @ 179:7fd70926e2e1 v7.0055
updated for version 7.0055
author | vimboss |
---|---|
date | Fri, 04 Mar 2005 23:39:37 +0000 |
parents | 125e80798a85 |
children | 7e70fc748752 |
comparison
equal
deleted
inserted
replaced
178:4d53c2a2af94 | 179:7fd70926e2e1 |
---|---|
1 *term.txt* For Vim version 7.0aa. Last change: 2004 Dec 07 | 1 *term.txt* For Vim version 7.0aa. Last change: 2005 Mar 04 |
2 | 2 |
3 | 3 |
4 VIM REFERENCE MANUAL by Bram Moolenaar | 4 VIM REFERENCE MANUAL by Bram Moolenaar |
5 | 5 |
6 | 6 |
144 are recognized as individual typed commands, even though Vim receives the same | 144 are recognized as individual typed commands, even though Vim receives the same |
145 sequence of bytes. | 145 sequence of bytes. |
146 | 146 |
147 *vt100-function-keys* *xterm-function-keys* | 147 *vt100-function-keys* *xterm-function-keys* |
148 An xterm can send function keys F1 to F4 in two modes: vt100 compatible or | 148 An xterm can send function keys F1 to F4 in two modes: vt100 compatible or |
149 not. Because Vim cannot know what the xterm is sending, both types of keys | 149 not. Because Vim may not know what the xterm is sending, both types of keys |
150 are recognized. The same happens for the <Home> and <End> keys. | 150 are recognized. The same happens for the <Home> and <End> keys. |
151 normal vt100 ~ | 151 normal vt100 ~ |
152 <F1> t_k1 <Esc>[11~ <xF1> <Esc>OP *<xF1>-xterm* | 152 <F1> t_k1 <Esc>[11~ <xF1> <Esc>OP *<xF1>-xterm* |
153 <F2> t_k2 <Esc>[12~ <xF2> <Esc>OQ *<xF2>-xterm* | 153 <F2> t_k2 <Esc>[12~ <xF2> <Esc>OQ *<xF2>-xterm* |
154 <F3> t_k3 <Esc>[13~ <xF3> <Esc>OR *<xF3>-xterm* | 154 <F3> t_k3 <Esc>[13~ <xF3> <Esc>OR *<xF3>-xterm* |
165 Newer versions of xterm support shifted function keys and special keys. Vim | 165 Newer versions of xterm support shifted function keys and special keys. Vim |
166 recognizes most of them. Use ":set termcap" to check which are supported and | 166 recognizes most of them. Use ":set termcap" to check which are supported and |
167 what the codes are. Mostly these are not in a termcap, they are only | 167 what the codes are. Mostly these are not in a termcap, they are only |
168 supported by the builtin_xterm termcap. | 168 supported by the builtin_xterm termcap. |
169 | 169 |
170 *xterm-modifier-keys* | |
171 Newer versions of xterm support Alt and Ctrl for most function keys. To avoid | |
172 having to add all combinations of Alt, Ctrl and Shift for every key a special | |
173 sequence is recognized at the end of a termcap entry: ";*X". The "X" can be | |
174 any character, often '~' is used. The ";*" stands for an optional modifier | |
175 argument. ";2" is Shift, ";3" is Alt, ";5" is Ctrl and ";9" is Meta (when | |
176 it's different from Alt). They can be combined. Examples: > | |
177 :set <F8>=^[[19;*~ | |
178 :set <Home>=^[[1;*H | |
179 Another speciality about these codes is that they are not overwritten by | |
180 another code. That is to avoid that the codes obtained from xterm directly | |
181 |t_RV| overwrite them. | |
170 *xterm-scroll-region* | 182 *xterm-scroll-region* |
171 The default termcap entry for xterm on Sun and other platforms does not | 183 The default termcap entry for xterm on Sun and other platforms does not |
172 contain the entry for scroll regions. Add ":cs=\E[%i%d;%dr:" to the xterm | 184 contain the entry for scroll regions. Add ":cs=\E[%i%d;%dr:" to the xterm |
173 entry in /etc/termcap and everything should work. | 185 entry in /etc/termcap and everything should work. |
174 | 186 |