Mercurial > vim
annotate runtime/doc/term.txt @ 13927:ec54a202ad0c v8.0.1834
patch 8.0.1834: GUI: find/replace dialog does not handle some chars
commit https://github.com/vim/vim/commit/518bc174ed34dc79303488914aaaa3c238a85080
Author: Bram Moolenaar <Bram@vim.org>
Date: Sun May 13 17:05:30 2018 +0200
patch 8.0.1834: GUI: find/replace dialog does not handle some chars
Problem: GUI: find/replace dialog does not handle some chars properly.
Solution: Escape '?' when needed. Always escape backslash. (closes https://github.com/vim/vim/issues/2418,
closes #2435)
author | Christian Brabandt <cb@256bit.org> |
---|---|
date | Sun, 13 May 2018 17:15:05 +0200 |
parents | 3b26420fc639 |
children | 1174611ad715 |
rev | line source |
---|---|
12756
3b26420fc639
Long overdue runtime update.
Christian Brabandt <cb@256bit.org>
parents:
12499
diff
changeset
|
1 *term.txt* For Vim version 8.0. Last change: 2017 Oct 14 |
7 | 2 |
3 | |
4 VIM REFERENCE MANUAL by Bram Moolenaar | |
5 | |
6 | |
7 Terminal information *terminal-info* | |
8 | |
9 Vim uses information about the terminal you are using to fill the screen and | |
10 recognize what keys you hit. If this information is not correct, the screen | |
11 may be messed up or keys may not be recognized. The actions which have to be | |
12 performed on the screen are accomplished by outputting a string of | |
13 characters. Special keys produce a string of characters. These strings are | |
14 stored in the terminal options, see |terminal-options|. | |
15 | |
16 NOTE: Most of this is not used when running the |GUI|. | |
17 | |
18 1. Startup |startup-terminal| | |
19 2. Terminal options |terminal-options| | |
20 3. Window size |window-size| | |
21 4. Slow and fast terminals |slow-fast-terminal| | |
22 5. Using the mouse |mouse-using| | |
23 | |
24 ============================================================================== | |
25 1. Startup *startup-terminal* | |
26 | |
27 When Vim is started a default terminal type is assumed. For the Amiga this is | |
28 a standard CLI window, for MS-DOS the pc terminal, for Unix an ansi terminal. | |
29 A few other terminal types are always available, see below |builtin-terms|. | |
30 | |
31 You can give the terminal name with the '-T' Vim argument. If it is not given | |
32 Vim will try to get the name from the TERM environment variable. | |
33 | |
34 *termcap* *terminfo* *E557* *E558* *E559* | |
35 On Unix the terminfo database or termcap file is used. This is referred to as | |
36 "termcap" in all the documentation. At compile time, when running configure, | |
37 the choice whether to use terminfo or termcap is done automatically. When | |
38 running Vim the output of ":version" will show |+terminfo| if terminfo is | |
39 used. Also see |xterm-screens|. | |
40 | |
41 On non-Unix systems a termcap is only available if Vim was compiled with | |
42 TERMCAP defined. | |
43 | |
44 *builtin-terms* *builtin_terms* | |
45 Which builtin terminals are available depends on a few defines in feature.h, | |
46 which need to be set at compile time: | |
47 define output of ":version" terminals builtin ~ | |
48 NO_BUILTIN_TCAPS -builtin_terms none | |
49 SOME_BUILTIN_TCAPS +builtin_terms most common ones (default) | |
50 ALL_BUILTIN_TCAPS ++builtin_terms all available | |
51 | |
52 You can see a list of available builtin terminals with ":set term=xxx" (when | |
53 not running the GUI). Also see |+builtin_terms|. | |
54 | |
55 If the termcap code is included Vim will try to get the strings for the | |
56 terminal you are using from the termcap file and the builtin termcaps. Both | |
57 are always used, if an entry for the terminal you are using is present. Which | |
58 one is used first depends on the 'ttybuiltin' option: | |
59 | |
60 'ttybuiltin' on 1: builtin termcap 2: external termcap | |
61 'ttybuiltin' off 1: external termcap 2: builtin termcap | |
62 | |
63 If an option is missing in one of them, it will be obtained from the other | |
64 one. If an option is present in both, the one first encountered is used. | |
65 | |
66 Which external termcap file is used varies from system to system and may | |
67 depend on the environment variables "TERMCAP" and "TERMPATH". See "man | |
68 tgetent". | |
69 | |
70 Settings depending on terminal *term-dependent-settings* | |
71 | |
72 If you want to set options or mappings, depending on the terminal name, you | |
73 can do this best in your .vimrc. Example: > | |
74 | |
75 if &term == "xterm" | |
76 ... xterm maps and settings ... | |
77 elseif &term =~ "vt10." | |
78 ... vt100, vt102 maps and settings ... | |
79 endif | |
80 < | |
81 *raw-terminal-mode* | |
82 For normal editing the terminal will be put into "raw" mode. The strings | |
83 defined with 't_ti' and 't_ks' will be sent to the terminal. Normally this | |
84 puts the terminal in a state where the termcap codes are valid and activates | |
85 the cursor and function keys. When Vim exits the terminal will be put back | |
86 into the mode it was before Vim started. The strings defined with 't_te' and | |
87 't_ke' will be sent to the terminal. On the Amiga, with commands that execute | |
88 an external command (e.g., "!!"), the terminal will be put into Normal mode | |
89 for a moment. This means that you can stop the output to the screen by | |
90 hitting a printing key. Output resumes when you hit <BS>. | |
91 | |
10640
27be410d6d29
patch 8.0.0210: no support for bracketed paste
Christian Brabandt <cb@256bit.org>
parents:
10198
diff
changeset
|
92 *xterm-bracketed-paste* |
27be410d6d29
patch 8.0.0210: no support for bracketed paste
Christian Brabandt <cb@256bit.org>
parents:
10198
diff
changeset
|
93 When the 't_BE' option is set then 't_BE' will be sent to the |
27be410d6d29
patch 8.0.0210: no support for bracketed paste
Christian Brabandt <cb@256bit.org>
parents:
10198
diff
changeset
|
94 terminal when entering "raw" mode and 't_BD' when leaving "raw" mode. The |
27be410d6d29
patch 8.0.0210: no support for bracketed paste
Christian Brabandt <cb@256bit.org>
parents:
10198
diff
changeset
|
95 terminal is then expected to put 't_PS' before pasted text and 't_PE' after |
27be410d6d29
patch 8.0.0210: no support for bracketed paste
Christian Brabandt <cb@256bit.org>
parents:
10198
diff
changeset
|
96 pasted text. This way Vim can separate text that is pasted from characters |
27be410d6d29
patch 8.0.0210: no support for bracketed paste
Christian Brabandt <cb@256bit.org>
parents:
10198
diff
changeset
|
97 that are typed. The pasted text is handled like when the middle mouse button |
10813
09eb5fd275e0
patch 8.0.0296: bracketed paste can only append, not insert
Christian Brabandt <cb@256bit.org>
parents:
10734
diff
changeset
|
98 is used, it is inserted literally and not interpreted as commands. |
09eb5fd275e0
patch 8.0.0296: bracketed paste can only append, not insert
Christian Brabandt <cb@256bit.org>
parents:
10734
diff
changeset
|
99 |
09eb5fd275e0
patch 8.0.0296: bracketed paste can only append, not insert
Christian Brabandt <cb@256bit.org>
parents:
10734
diff
changeset
|
100 When the cursor is in the first column, the pasted text will be inserted |
09eb5fd275e0
patch 8.0.0296: bracketed paste can only append, not insert
Christian Brabandt <cb@256bit.org>
parents:
10734
diff
changeset
|
101 before it. Otherwise the pasted text is appended after the cursor position. |
09eb5fd275e0
patch 8.0.0296: bracketed paste can only append, not insert
Christian Brabandt <cb@256bit.org>
parents:
10734
diff
changeset
|
102 This means one cannot paste after the first column. Unfortunately Vim does |
09eb5fd275e0
patch 8.0.0296: bracketed paste can only append, not insert
Christian Brabandt <cb@256bit.org>
parents:
10734
diff
changeset
|
103 not have a way to tell where the mouse pointer was. |
10640
27be410d6d29
patch 8.0.0210: no support for bracketed paste
Christian Brabandt <cb@256bit.org>
parents:
10198
diff
changeset
|
104 |
27be410d6d29
patch 8.0.0210: no support for bracketed paste
Christian Brabandt <cb@256bit.org>
parents:
10198
diff
changeset
|
105 Note that in some situations Vim will not recognize the bracketed paste and |
27be410d6d29
patch 8.0.0210: no support for bracketed paste
Christian Brabandt <cb@256bit.org>
parents:
10198
diff
changeset
|
106 you will get the raw text. In other situations Vim will only get the first |
10734 | 107 pasted character and drop the rest, e.g. when using the "r" command. If you |
108 have a problem with this, disable bracketed paste by putting this in your | |
109 .vimrc: > | |
110 set t_BE= | |
111 If this is done while Vim is running the 't_BD' will be sent to the terminal | |
112 to disable bracketed paste. | |
10640
27be410d6d29
patch 8.0.0210: no support for bracketed paste
Christian Brabandt <cb@256bit.org>
parents:
10198
diff
changeset
|
113 |
7 | 114 *cs7-problem* |
115 Note: If the terminal settings are changed after running Vim, you might have | |
116 an illegal combination of settings. This has been reported on Solaris 2.5 | |
117 with "stty cs8 parenb", which is restored as "stty cs7 parenb". Use | |
118 "stty cs8 -parenb -istrip" instead, this is restored correctly. | |
119 | |
120 Some termcap entries are wrong in the sense that after sending 't_ks' the | |
121 cursor keys send codes different from the codes defined in the termcap. To | |
122 avoid this you can set 't_ks' (and 't_ke') to empty strings. This must be | |
123 done during initialization (see |initialization|), otherwise it's too late. | |
124 | |
125 Some termcap entries assume that the highest bit is always reset. For | |
126 example: The cursor-up entry for the Amiga could be ":ku=\E[A:". But the | |
127 Amiga really sends "\233A". This works fine if the highest bit is reset, | |
128 e.g., when using an Amiga over a serial line. If the cursor keys don't work, | |
129 try the entry ":ku=\233A:". | |
130 | |
131 Some termcap entries have the entry ":ku=\E[A:". But the Amiga really sends | |
132 "\233A". On output "\E[" and "\233" are often equivalent, on input they | |
133 aren't. You will have to change the termcap entry, or change the key code with | |
134 the :set command to fix this. | |
135 | |
136 Many cursor key codes start with an <Esc>. Vim must find out if this is a | |
137 single hit of the <Esc> key or the start of a cursor key sequence. It waits | |
138 for a next character to arrive. If it does not arrive within one second a | |
139 single <Esc> is assumed. On very slow systems this may fail, causing cursor | |
140 keys not to work sometimes. If you discover this problem reset the 'timeout' | |
141 option. Vim will wait for the next character to arrive after an <Esc>. If | |
142 you want to enter a single <Esc> you must type it twice. Resetting the | |
143 'esckeys' option avoids this problem in Insert mode, but you lose the | |
144 possibility to use cursor and function keys in Insert mode. | |
145 | |
146 On the Amiga the recognition of window resizing is activated only when the | |
147 terminal name is "amiga" or "builtin_amiga". | |
148 | |
149 Some terminals have confusing codes for the cursor keys. The televideo 925 is | |
150 such a terminal. It sends a CTRL-H for cursor-left. This would make it | |
151 impossible to distinguish a backspace and cursor-left. To avoid this problem | |
152 CTRL-H is never recognized as cursor-left. | |
153 | |
154 *vt100-cursor-keys* *xterm-cursor-keys* | |
155 Other terminals (e.g., vt100 and xterm) have cursor keys that send <Esc>OA, | |
156 <Esc>OB, etc. Unfortunately these are valid commands in insert mode: Stop | |
157 insert, Open a new line above the new one, start inserting 'A', 'B', etc. | |
158 Instead of performing these commands Vim will erroneously recognize this typed | |
159 key sequence as a cursor key movement. To avoid this and make Vim do what you | |
160 want in either case you could use these settings: > | |
161 :set notimeout " don't timeout on mappings | |
162 :set ttimeout " do timeout on terminal key codes | |
163 :set timeoutlen=100 " timeout after 100 msec | |
1621 | 164 This requires the key-codes to be sent within 100 msec in order to recognize |
7 | 165 them as a cursor key. When you type you normally are not that fast, so they |
166 are recognized as individual typed commands, even though Vim receives the same | |
167 sequence of bytes. | |
168 | |
169 *vt100-function-keys* *xterm-function-keys* | |
170 An xterm can send function keys F1 to F4 in two modes: vt100 compatible or | |
179 | 171 not. Because Vim may not know what the xterm is sending, both types of keys |
7 | 172 are recognized. The same happens for the <Home> and <End> keys. |
173 normal vt100 ~ | |
174 <F1> t_k1 <Esc>[11~ <xF1> <Esc>OP *<xF1>-xterm* | |
175 <F2> t_k2 <Esc>[12~ <xF2> <Esc>OQ *<xF2>-xterm* | |
176 <F3> t_k3 <Esc>[13~ <xF3> <Esc>OR *<xF3>-xterm* | |
177 <F4> t_k4 <Esc>[14~ <xF4> <Esc>OS *<xF4>-xterm* | |
178 <Home> t_kh <Esc>[7~ <xHome> <Esc>OH *<xHome>-xterm* | |
179 <End> t_@7 <Esc>[4~ <xEnd> <Esc>OF *<xEnd>-xterm* | |
180 | |
181 When Vim starts, <xF1> is mapped to <F1>, <xF2> to <F2> etc. This means that | |
182 by default both codes do the same thing. If you make a mapping for <xF2>, | |
183 because your terminal does have two keys, the default mapping is overwritten, | |
184 thus you can use the <F2> and <xF2> keys for something different. | |
185 | |
186 *xterm-shifted-keys* | |
187 Newer versions of xterm support shifted function keys and special keys. Vim | |
188 recognizes most of them. Use ":set termcap" to check which are supported and | |
189 what the codes are. Mostly these are not in a termcap, they are only | |
190 supported by the builtin_xterm termcap. | |
191 | |
179 | 192 *xterm-modifier-keys* |
193 Newer versions of xterm support Alt and Ctrl for most function keys. To avoid | |
194 having to add all combinations of Alt, Ctrl and Shift for every key a special | |
195 sequence is recognized at the end of a termcap entry: ";*X". The "X" can be | |
196 any character, often '~' is used. The ";*" stands for an optional modifier | |
197 argument. ";2" is Shift, ";3" is Alt, ";5" is Ctrl and ";9" is Meta (when | |
198 it's different from Alt). They can be combined. Examples: > | |
199 :set <F8>=^[[19;*~ | |
200 :set <Home>=^[[1;*H | |
201 Another speciality about these codes is that they are not overwritten by | |
202 another code. That is to avoid that the codes obtained from xterm directly | |
203 |t_RV| overwrite them. | |
7 | 204 *xterm-scroll-region* |
205 The default termcap entry for xterm on Sun and other platforms does not | |
206 contain the entry for scroll regions. Add ":cs=\E[%i%d;%dr:" to the xterm | |
207 entry in /etc/termcap and everything should work. | |
208 | |
209 *xterm-end-home-keys* | |
210 On some systems (at least on FreeBSD with XFree86 3.1.2) the codes that the | |
211 <End> and <Home> keys send contain a <Nul> character. To make these keys send | |
212 the proper key code, add these lines to your ~/.Xdefaults file: | |
213 | |
214 *VT100.Translations: #override \n\ | |
215 <Key>Home: string("0x1b") string("[7~") \n\ | |
216 <Key>End: string("0x1b") string("[8~") | |
217 | |
218 *xterm-8bit* *xterm-8-bit* | |
219 Xterm can be run in a mode where it uses 8-bit escape sequences. The CSI code | |
220 is used instead of <Esc>[. The advantage is that an <Esc> can quickly be | |
221 recognized in Insert mode, because it can't be confused with the start of a | |
222 special key. | |
223 For the builtin termcap entries, Vim checks if the 'term' option contains | |
224 "8bit" anywhere. It then uses 8-bit characters for the termcap entries, the | |
225 mouse and a few other things. You would normally set $TERM in your shell to | |
226 "xterm-8bit" and Vim picks this up and adjusts to the 8-bit setting | |
227 automatically. | |
228 When Vim receives a response to the |t_RV| (request version) sequence and it | |
229 starts with CSI, it assumes that the terminal is in 8-bit mode and will | |
230 convert all key sequences to their 8-bit variants. | |
231 | |
232 ============================================================================== | |
667 | 233 2. Terminal options *terminal-options* *termcap-options* *E436* |
7 | 234 |
235 The terminal options can be set just like normal options. But they are not | |
236 shown with the ":set all" command. Instead use ":set termcap". | |
237 | |
238 It is always possible to change individual strings by setting the | |
239 appropriate option. For example: > | |
240 :set t_ce=^V^[[K (CTRL-V, <Esc>, [, K) | |
241 | |
242 {Vi: no terminal options. You have to exit Vi, edit the termcap entry and | |
243 try again} | |
244 | |
245 The options are listed below. The associated termcap code is always equal to | |
246 the last two characters of the option name. Only one termcap code is | |
247 required: Cursor motion, 't_cm'. | |
248 | |
6602 | 249 The options 't_da', 't_db', 't_ms', 't_xs', 't_xn' represent flags in the |
250 termcap. When the termcap flag is present, the option will be set to "y". | |
251 But any non-empty string means that the flag is set. An empty string means | |
252 that the flag is not set. 't_CS' works like this too, but it isn't a termcap | |
253 flag. | |
7 | 254 |
11062 | 255 OUTPUT CODES *terminal-output-codes* |
7 | 256 option meaning ~ |
257 | |
258 t_AB set background color (ANSI) *t_AB* *'t_AB'* | |
259 t_AF set foreground color (ANSI) *t_AF* *'t_AF'* | |
260 t_AL add number of blank lines *t_AL* *'t_AL'* | |
261 t_al add new blank line *t_al* *'t_al'* | |
262 t_bc backspace character *t_bc* *'t_bc'* | |
263 t_cd clear to end of screen *t_cd* *'t_cd'* | |
264 t_ce clear to end of line *t_ce* *'t_ce'* | |
265 t_cl clear screen *t_cl* *'t_cl'* | |
266 t_cm cursor motion (required!) *E437* *t_cm* *'t_cm'* | |
267 t_Co number of colors *t_Co* *'t_Co'* | |
268 t_CS if non-empty, cursor relative to scroll region *t_CS* *'t_CS'* | |
269 t_cs define scrolling region *t_cs* *'t_cs'* | |
270 t_CV define vertical scrolling region *t_CV* *'t_CV'* | |
271 t_da if non-empty, lines from above scroll down *t_da* *'t_da'* | |
272 t_db if non-empty, lines from below scroll up *t_db* *'t_db'* | |
273 t_DL delete number of lines *t_DL* *'t_DL'* | |
274 t_dl delete line *t_dl* *'t_dl'* | |
275 t_fs set window title end (from status line) *t_fs* *'t_fs'* | |
276 t_ke exit "keypad transmit" mode *t_ke* *'t_ke'* | |
277 t_ks start "keypad transmit" mode *t_ks* *'t_ks'* | |
278 t_le move cursor one char left *t_le* *'t_le'* | |
279 t_mb blinking mode *t_mb* *'t_mb'* | |
280 t_md bold mode *t_md* *'t_md'* | |
281 t_me Normal mode (undoes t_mr, t_mb, t_md and color) *t_me* *'t_me'* | |
282 t_mr reverse (invert) mode *t_mr* *'t_mr'* | |
283 *t_ms* *'t_ms'* | |
284 t_ms if non-empty, cursor can be moved in standout/inverse mode | |
285 t_nd non destructive space character *t_nd* *'t_nd'* | |
286 t_op reset to original color pair *t_op* *'t_op'* | |
287 t_RI cursor number of chars right *t_RI* *'t_RI'* | |
288 t_Sb set background color *t_Sb* *'t_Sb'* | |
289 t_Sf set foreground color *t_Sf* *'t_Sf'* | |
290 t_se standout end *t_se* *'t_se'* | |
291 t_so standout mode *t_so* *'t_so'* | |
292 t_sr scroll reverse (backward) *t_sr* *'t_sr'* | |
293 t_te out of "termcap" mode *t_te* *'t_te'* | |
294 t_ti put terminal in "termcap" mode *t_ti* *'t_ti'* | |
295 t_ts set window title start (to status line) *t_ts* *'t_ts'* | |
296 t_ue underline end *t_ue* *'t_ue'* | |
297 t_us underline mode *t_us* *'t_us'* | |
298 t_ut clearing uses the current background color *t_ut* *'t_ut'* | |
299 t_vb visual bell *t_vb* *'t_vb'* | |
300 t_ve cursor visible *t_ve* *'t_ve'* | |
301 t_vi cursor invisible *t_vi* *'t_vi'* | |
12254 | 302 t_vs cursor very visible (blink) *t_vs* *'t_vs'* |
7 | 303 *t_xs* *'t_xs'* |
304 t_xs if non-empty, standout not erased by overwriting (hpterm) | |
6602 | 305 *t_xn* *'t_xn'* |
6647 | 306 t_xn if non-empty, writing a character at the last screen cell |
307 does not cause scrolling | |
7 | 308 t_ZH italics mode *t_ZH* *'t_ZH'* |
309 t_ZR italics end *t_ZR* *'t_ZR'* | |
310 | |
311 Added by Vim (there are no standard codes for these): | |
12499 | 312 t_Ce undercurl end *t_Ce* *'t_Ce'* |
313 t_Cs undercurl mode *t_Cs* *'t_Cs'* | |
314 t_Te strikethrough end *t_Te* *'t_Te'* | |
315 t_Ts strikethrough mode *t_Ts* *'t_Ts'* | |
7 | 316 t_IS set icon text start *t_IS* *'t_IS'* |
317 t_IE set icon text end *t_IE* *'t_IE'* | |
318 t_WP set window position (Y, X) in pixels *t_WP* *'t_WP'* | |
11400
0f8713fe20dc
Updated runtime files.
Christian Brabandt <cb@256bit.org>
parents:
11062
diff
changeset
|
319 t_GP get window position (Y, X) in pixels *t_GP* *'t_GP'* |
11763
21f3930dfe6e
Documentation updates.
Christian Brabandt <cb@256bit.org>
parents:
11400
diff
changeset
|
320 t_WS set window size (height, width in cells) *t_WS* *'t_WS'* |
12254 | 321 t_VS cursor normally visible (no blink) *t_VS* *'t_VS'* |
856 | 322 t_SI start insert mode (bar cursor shape) *t_SI* *'t_SI'* |
6727 | 323 t_SR start replace mode (underline cursor shape) *t_SR* *'t_SR'* |
324 t_EI end insert or replace mode (block cursor shape) *t_EI* *'t_EI'* | |
500 | 325 |termcap-cursor-shape| |
7 | 326 t_RV request terminal version string (for xterm) *t_RV* *'t_RV'* |
327 |xterm-8bit| |v:termresponse| |'ttymouse'| |xterm-codes| | |
4229 | 328 t_u7 request cursor position (for xterm) *t_u7* *'t_u7'* |
329 see |'ambiwidth'| | |
12756
3b26420fc639
Long overdue runtime update.
Christian Brabandt <cb@256bit.org>
parents:
12499
diff
changeset
|
330 t_RF request terminal foreground color *t_RF* *'t_RF'* |
6884 | 331 t_RB request terminal background color *t_RB* *'t_RB'* |
8969
c83e2c1e7f2b
commit https://github.com/vim/vim/commit/8a633e3427b47286869aa4b96f2bfc1fe65b25cd
Christian Brabandt <cb@256bit.org>
parents:
8951
diff
changeset
|
332 t_8f set foreground color (R, G, B) *t_8f* *'t_8f'* |
c83e2c1e7f2b
commit https://github.com/vim/vim/commit/8a633e3427b47286869aa4b96f2bfc1fe65b25cd
Christian Brabandt <cb@256bit.org>
parents:
8951
diff
changeset
|
333 |xterm-true-color| |
c83e2c1e7f2b
commit https://github.com/vim/vim/commit/8a633e3427b47286869aa4b96f2bfc1fe65b25cd
Christian Brabandt <cb@256bit.org>
parents:
8951
diff
changeset
|
334 t_8b set background color (R, G, B) *t_8b* *'t_8b'* |
c83e2c1e7f2b
commit https://github.com/vim/vim/commit/8a633e3427b47286869aa4b96f2bfc1fe65b25cd
Christian Brabandt <cb@256bit.org>
parents:
8951
diff
changeset
|
335 |xterm-true-color| |
10640
27be410d6d29
patch 8.0.0210: no support for bracketed paste
Christian Brabandt <cb@256bit.org>
parents:
10198
diff
changeset
|
336 t_BE enable bracketed paste mode *t_BE* *'t_BE'* |
27be410d6d29
patch 8.0.0210: no support for bracketed paste
Christian Brabandt <cb@256bit.org>
parents:
10198
diff
changeset
|
337 |xterm-bracketed-paste| |
27be410d6d29
patch 8.0.0210: no support for bracketed paste
Christian Brabandt <cb@256bit.org>
parents:
10198
diff
changeset
|
338 t_BD disable bracketed paste mode *t_BD* *'t_BD'* |
27be410d6d29
patch 8.0.0210: no support for bracketed paste
Christian Brabandt <cb@256bit.org>
parents:
10198
diff
changeset
|
339 |xterm-bracketed-paste| |
12254 | 340 t_SC set cursor color start *t_SC* *'t_SC'* |
341 t_EC set cursor color end *t_EC* *'t_EC'* | |
342 t_SH set cursor shape *t_SH* *'t_SH'* | |
12499 | 343 t_RC request terminal cursor blinking *t_RC* *'t_RC'* |
12254 | 344 t_RS request terminal cursor style *t_RS* *'t_RS'* |
345 | |
346 Some codes have a start, middle and end part. The start and end are defined | |
347 by the termcap option, the middle part is text. | |
348 set title text: t_ts {title text} t_fs | |
349 set icon text: t_IS {icon text} t_IE | |
350 set cursor color: t_SC {color name} t_EC | |
351 | |
352 t_SH must take one argument: | |
353 0, 1 or none blinking block cursor | |
354 2 block cursor | |
355 3 blinking underline cursor | |
356 4 underline cursor | |
357 5 blinking vertical bar cursor | |
358 6 vertical bar cursor | |
359 | |
360 t_RS is sent only if the response to t_RV has been received. It is not used | |
361 on Mac OS when Terminal.app could be recognized from the termresponse. | |
362 | |
7 | 363 |
11062 | 364 KEY CODES *terminal-key-codes* |
7 | 365 Note: Use the <> form if possible |
366 | |
367 option name meaning ~ | |
368 | |
369 t_ku <Up> arrow up *t_ku* *'t_ku'* | |
370 t_kd <Down> arrow down *t_kd* *'t_kd'* | |
371 t_kr <Right> arrow right *t_kr* *'t_kr'* | |
372 t_kl <Left> arrow left *t_kl* *'t_kl'* | |
180 | 373 <xUp> alternate arrow up *<xUp>* |
374 <xDown> alternate arrow down *<xDown>* | |
375 <xRight> alternate arrow right *<xRight>* | |
376 <xLeft> alternate arrow left *<xLeft>* | |
7 | 377 <S-Up> shift arrow up |
378 <S-Down> shift arrow down | |
379 t_%i <S-Right> shift arrow right *t_%i* *'t_%i'* | |
380 t_#4 <S-Left> shift arrow left *t_#4* *'t_#4'* | |
381 t_k1 <F1> function key 1 *t_k1* *'t_k1'* | |
382 <xF1> alternate F1 *<xF1>* | |
383 t_k2 <F2> function key 2 *<F2>* *t_k2* *'t_k2'* | |
384 <xF2> alternate F2 *<xF2>* | |
385 t_k3 <F3> function key 3 *<F3>* *t_k3* *'t_k3'* | |
386 <xF3> alternate F3 *<xF3>* | |
387 t_k4 <F4> function key 4 *<F4>* *t_k4* *'t_k4'* | |
388 <xF4> alternate F4 *<xF4>* | |
389 t_k5 <F5> function key 5 *<F5>* *t_k5* *'t_k5'* | |
390 t_k6 <F6> function key 6 *<F6>* *t_k6* *'t_k6'* | |
391 t_k7 <F7> function key 7 *<F7>* *t_k7* *'t_k7'* | |
392 t_k8 <F8> function key 8 *<F8>* *t_k8* *'t_k8'* | |
393 t_k9 <F9> function key 9 *<F9>* *t_k9* *'t_k9'* | |
394 t_k; <F10> function key 10 *<F10>* *t_k;* *'t_k;'* | |
4437 | 395 t_F1 <F11> function key 11 *<F11>* *t_F1* *'t_F1'* |
7 | 396 t_F2 <F12> function key 12 *<F12>* *t_F2* *'t_F2'* |
397 t_F3 <F13> function key 13 *<F13>* *t_F3* *'t_F3'* | |
398 t_F4 <F14> function key 14 *<F14>* *t_F4* *'t_F4'* | |
399 t_F5 <F15> function key 15 *<F15>* *t_F5* *'t_F5'* | |
400 t_F6 <F16> function key 16 *<F16>* *t_F6* *'t_F6'* | |
401 t_F7 <F17> function key 17 *<F17>* *t_F7* *'t_F7'* | |
402 t_F8 <F18> function key 18 *<F18>* *t_F8* *'t_F8'* | |
403 t_F9 <F19> function key 19 *<F19>* *t_F9* *'t_F9'* | |
404 <S-F1> shifted function key 1 | |
405 <S-xF1> alternate <S-F1> *<S-xF1>* | |
406 <S-F2> shifted function key 2 *<S-F2>* | |
407 <S-xF2> alternate <S-F2> *<S-xF2>* | |
408 <S-F3> shifted function key 3 *<S-F3>* | |
409 <S-xF3> alternate <S-F3> *<S-xF3>* | |
410 <S-F4> shifted function key 4 *<S-F4>* | |
411 <S-xF4> alternate <S-F4> *<S-xF4>* | |
412 <S-F5> shifted function key 5 *<S-F5>* | |
413 <S-F6> shifted function key 6 *<S-F6>* | |
414 <S-F7> shifted function key 7 *<S-F7>* | |
415 <S-F8> shifted function key 8 *<S-F8>* | |
416 <S-F9> shifted function key 9 *<S-F9>* | |
417 <S-F10> shifted function key 10 *<S-F10>* | |
418 <S-F11> shifted function key 11 *<S-F11>* | |
419 <S-F12> shifted function key 12 *<S-F12>* | |
420 t_%1 <Help> help key *t_%1* *'t_%1'* | |
421 t_&8 <Undo> undo key *t_&8* *'t_&8'* | |
422 t_kI <Insert> insert key *t_kI* *'t_kI'* | |
423 t_kD <Del> delete key *t_kD* *'t_kD'* | |
424 t_kb <BS> backspace key *t_kb* *'t_kb'* | |
4437 | 425 t_kB <S-Tab> back-tab (shift-tab) *<S-Tab>* *t_kB* *'t_kB'* |
7 | 426 t_kh <Home> home key *t_kh* *'t_kh'* |
4437 | 427 t_#2 <S-Home> shifted home key *<S-Home>* *t_#2* *'t_#2'* |
7 | 428 <xHome> alternate home key *<xHome>* |
429 t_@7 <End> end key *t_@7* *'t_@7'* | |
430 t_*7 <S-End> shifted end key *<S-End>* *t_star7* *'t_star7'* | |
431 <xEnd> alternate end key *<xEnd>* | |
432 t_kP <PageUp> page-up key *t_kP* *'t_kP'* | |
433 t_kN <PageDown> page-down key *t_kN* *'t_kN'* | |
434 t_K1 <kHome> keypad home key *t_K1* *'t_K1'* | |
435 t_K4 <kEnd> keypad end key *t_K4* *'t_K4'* | |
436 t_K3 <kPageUp> keypad page-up key *t_K3* *'t_K3'* | |
437 t_K5 <kPageDown> keypad page-down key *t_K5* *'t_K5'* | |
438 t_K6 <kPlus> keypad plus key *<kPlus>* *t_K6* *'t_K6'* | |
439 t_K7 <kMinus> keypad minus key *<kMinus>* *t_K7* *'t_K7'* | |
4437 | 440 t_K8 <kDivide> keypad divide *<kDivide>* *t_K8* *'t_K8'* |
441 t_K9 <kMultiply> keypad multiply *<kMultiply>* *t_K9* *'t_K9'* | |
7 | 442 t_KA <kEnter> keypad enter key *<kEnter>* *t_KA* *'t_KA'* |
443 t_KB <kPoint> keypad decimal point *<kPoint>* *t_KB* *'t_KB'* | |
444 t_KC <k0> keypad 0 *<k0>* *t_KC* *'t_KC'* | |
445 t_KD <k1> keypad 1 *<k1>* *t_KD* *'t_KD'* | |
446 t_KE <k2> keypad 2 *<k2>* *t_KE* *'t_KE'* | |
447 t_KF <k3> keypad 3 *<k3>* *t_KF* *'t_KF'* | |
448 t_KG <k4> keypad 4 *<k4>* *t_KG* *'t_KG'* | |
449 t_KH <k5> keypad 5 *<k5>* *t_KH* *'t_KH'* | |
450 t_KI <k6> keypad 6 *<k6>* *t_KI* *'t_KI'* | |
451 t_KJ <k7> keypad 7 *<k7>* *t_KJ* *'t_KJ'* | |
452 t_KK <k8> keypad 8 *<k8>* *t_KK* *'t_KK'* | |
453 t_KL <k9> keypad 9 *<k9>* *t_KL* *'t_KL'* | |
454 <Mouse> leader of mouse code *<Mouse>* | |
11062 | 455 *t_PS* *'t_PS'* |
456 t_PS start of bracketed paste |xterm-bracketed-paste| | |
457 t_PE end of bracketed paste |xterm-bracketed-paste| *t_PE* *'t_PE'* | |
7 | 458 |
459 Note about t_so and t_mr: When the termcap entry "so" is not present the | |
460 entry for "mr" is used. And vice versa. The same is done for "se" and "me". | |
461 If your terminal supports both inversion and standout mode, you can see two | |
462 different modes. If your terminal supports only one of the modes, both will | |
463 look the same. | |
464 | |
33 | 465 *keypad-comma* |
7 | 466 The keypad keys, when they are not mapped, behave like the equivalent normal |
33 | 467 key. There is one exception: if you have a comma on the keypad instead of a |
468 decimal point, Vim will use a dot anyway. Use these mappings to fix that: > | |
469 :noremap <kPoint> , | |
470 :noremap! <kPoint> , | |
471 < *xterm-codes* | |
7 | 472 There is a special trick to obtain the key codes which currently only works |
473 for xterm. When |t_RV| is defined and a response is received which indicates | |
474 an xterm with patchlevel 141 or higher, Vim uses special escape sequences to | |
475 request the key codes directly from the xterm. The responses are used to | |
476 adjust the various t_ codes. This avoids the problem that the xterm can | |
477 produce different codes, depending on the mode it is in (8-bit, VT102, | |
478 VT220, etc.). The result is that codes like <xF1> are no longer needed. | |
479 Note: This is only done on startup. If the xterm options are changed after | |
6530 | 480 Vim has started, the escape sequences may not be recognized anymore. |
7 | 481 |
8969
c83e2c1e7f2b
commit https://github.com/vim/vim/commit/8a633e3427b47286869aa4b96f2bfc1fe65b25cd
Christian Brabandt <cb@256bit.org>
parents:
8951
diff
changeset
|
482 *xterm-true-color* |
c83e2c1e7f2b
commit https://github.com/vim/vim/commit/8a633e3427b47286869aa4b96f2bfc1fe65b25cd
Christian Brabandt <cb@256bit.org>
parents:
8951
diff
changeset
|
483 Vim supports using true colors in the terminal (taken from |highlight-guifg| |
9027
773d627cac0b
commit https://github.com/vim/vim/commit/61be73bb0f965a895bfb064ea3e55476ac175162
Christian Brabandt <cb@256bit.org>
parents:
8969
diff
changeset
|
484 and |highlight-guibg|), given that the terminal supports this. To make this |
773d627cac0b
commit https://github.com/vim/vim/commit/61be73bb0f965a895bfb064ea3e55476ac175162
Christian Brabandt <cb@256bit.org>
parents:
8969
diff
changeset
|
485 work the 'termguicolors' option needs to be set. |
10140
b11ceef7116e
commit https://github.com/vim/vim/commit/64d8e25bf6efe5f18b032563521c3ce278c316ab
Christian Brabandt <cb@256bit.org>
parents:
9027
diff
changeset
|
486 See https://gist.github.com/XVilka/8346728 for a list of terminals that |
b11ceef7116e
commit https://github.com/vim/vim/commit/64d8e25bf6efe5f18b032563521c3ce278c316ab
Christian Brabandt <cb@256bit.org>
parents:
9027
diff
changeset
|
487 support true colors. |
8969
c83e2c1e7f2b
commit https://github.com/vim/vim/commit/8a633e3427b47286869aa4b96f2bfc1fe65b25cd
Christian Brabandt <cb@256bit.org>
parents:
8951
diff
changeset
|
488 |
9027
773d627cac0b
commit https://github.com/vim/vim/commit/61be73bb0f965a895bfb064ea3e55476ac175162
Christian Brabandt <cb@256bit.org>
parents:
8969
diff
changeset
|
489 Sometimes setting 'termguicolors' is not enough and one has to set the |t_8f| |
773d627cac0b
commit https://github.com/vim/vim/commit/61be73bb0f965a895bfb064ea3e55476ac175162
Christian Brabandt <cb@256bit.org>
parents:
8969
diff
changeset
|
490 and |t_8b| options explicitly. Default values of these options are |
773d627cac0b
commit https://github.com/vim/vim/commit/61be73bb0f965a895bfb064ea3e55476ac175162
Christian Brabandt <cb@256bit.org>
parents:
8969
diff
changeset
|
491 "^[[38;2;%lu;%lu;%lum" and "^[[48;2;%lu;%lu;%lum" respectively, but it is only |
773d627cac0b
commit https://github.com/vim/vim/commit/61be73bb0f965a895bfb064ea3e55476ac175162
Christian Brabandt <cb@256bit.org>
parents:
8969
diff
changeset
|
492 set when `$TERM` is `xterm`. Some terminals accept the same sequences, but |
773d627cac0b
commit https://github.com/vim/vim/commit/61be73bb0f965a895bfb064ea3e55476ac175162
Christian Brabandt <cb@256bit.org>
parents:
8969
diff
changeset
|
493 with all semicolons replaced by colons (this is actually more compatible, but |
773d627cac0b
commit https://github.com/vim/vim/commit/61be73bb0f965a895bfb064ea3e55476ac175162
Christian Brabandt <cb@256bit.org>
parents:
8969
diff
changeset
|
494 less widely supported): > |
10140
b11ceef7116e
commit https://github.com/vim/vim/commit/64d8e25bf6efe5f18b032563521c3ce278c316ab
Christian Brabandt <cb@256bit.org>
parents:
9027
diff
changeset
|
495 let &t_8f = "\<Esc>[38:2:%lu:%lu:%lum" |
b11ceef7116e
commit https://github.com/vim/vim/commit/64d8e25bf6efe5f18b032563521c3ce278c316ab
Christian Brabandt <cb@256bit.org>
parents:
9027
diff
changeset
|
496 let &t_8b = "\<Esc>[48:2:%lu:%lu:%lum" |
9027
773d627cac0b
commit https://github.com/vim/vim/commit/61be73bb0f965a895bfb064ea3e55476ac175162
Christian Brabandt <cb@256bit.org>
parents:
8969
diff
changeset
|
497 |
773d627cac0b
commit https://github.com/vim/vim/commit/61be73bb0f965a895bfb064ea3e55476ac175162
Christian Brabandt <cb@256bit.org>
parents:
8969
diff
changeset
|
498 These options contain printf strings, with |printf()| (actually, its C |
773d627cac0b
commit https://github.com/vim/vim/commit/61be73bb0f965a895bfb064ea3e55476ac175162
Christian Brabandt <cb@256bit.org>
parents:
8969
diff
changeset
|
499 equivalent hence `l` modifier) invoked with the t_ option value and three |
773d627cac0b
commit https://github.com/vim/vim/commit/61be73bb0f965a895bfb064ea3e55476ac175162
Christian Brabandt <cb@256bit.org>
parents:
8969
diff
changeset
|
500 unsigned long integers that may have any value between 0 and 255 (inclusive) |
773d627cac0b
commit https://github.com/vim/vim/commit/61be73bb0f965a895bfb064ea3e55476ac175162
Christian Brabandt <cb@256bit.org>
parents:
8969
diff
changeset
|
501 representing red, green and blue colors respectively. |
8969
c83e2c1e7f2b
commit https://github.com/vim/vim/commit/8a633e3427b47286869aa4b96f2bfc1fe65b25cd
Christian Brabandt <cb@256bit.org>
parents:
8951
diff
changeset
|
502 |
2033
de5a43c5eedc
Update documentation files.
Bram Moolenaar <bram@zimbu.org>
parents:
1702
diff
changeset
|
503 *xterm-resize* |
de5a43c5eedc
Update documentation files.
Bram Moolenaar <bram@zimbu.org>
parents:
1702
diff
changeset
|
504 Window resizing with xterm only works if the allowWindowOps resource is |
de5a43c5eedc
Update documentation files.
Bram Moolenaar <bram@zimbu.org>
parents:
1702
diff
changeset
|
505 enabled. On some systems and versions of xterm it's disabled by default |
de5a43c5eedc
Update documentation files.
Bram Moolenaar <bram@zimbu.org>
parents:
1702
diff
changeset
|
506 because someone thought it would be a security issue. It's not clear if this |
de5a43c5eedc
Update documentation files.
Bram Moolenaar <bram@zimbu.org>
parents:
1702
diff
changeset
|
507 is actually the case. |
de5a43c5eedc
Update documentation files.
Bram Moolenaar <bram@zimbu.org>
parents:
1702
diff
changeset
|
508 |
de5a43c5eedc
Update documentation files.
Bram Moolenaar <bram@zimbu.org>
parents:
1702
diff
changeset
|
509 To overrule the default, put this line in your ~/.Xdefaults or |
de5a43c5eedc
Update documentation files.
Bram Moolenaar <bram@zimbu.org>
parents:
1702
diff
changeset
|
510 ~/.Xresources: |
de5a43c5eedc
Update documentation files.
Bram Moolenaar <bram@zimbu.org>
parents:
1702
diff
changeset
|
511 > |
de5a43c5eedc
Update documentation files.
Bram Moolenaar <bram@zimbu.org>
parents:
1702
diff
changeset
|
512 XTerm*allowWindowOps: true |
de5a43c5eedc
Update documentation files.
Bram Moolenaar <bram@zimbu.org>
parents:
1702
diff
changeset
|
513 |
de5a43c5eedc
Update documentation files.
Bram Moolenaar <bram@zimbu.org>
parents:
1702
diff
changeset
|
514 And run "xrdb -merge .Xresources" to make it effective. You can check the |
de5a43c5eedc
Update documentation files.
Bram Moolenaar <bram@zimbu.org>
parents:
1702
diff
changeset
|
515 value with the context menu (right mouse button while CTRL key is pressed), |
de5a43c5eedc
Update documentation files.
Bram Moolenaar <bram@zimbu.org>
parents:
1702
diff
changeset
|
516 there should be a tick at allow-window-ops. |
de5a43c5eedc
Update documentation files.
Bram Moolenaar <bram@zimbu.org>
parents:
1702
diff
changeset
|
517 |
7 | 518 *termcap-colors* |
519 Note about colors: The 't_Co' option tells Vim the number of colors available. | |
520 When it is non-zero, the 't_AB' and 't_AF' options are used to set the color. | |
521 If one of these is not available, 't_Sb' and 't_Sf' are used. 't_me' is used | |
522 to reset to the default colors. | |
523 | |
36 | 524 *termcap-cursor-shape* *termcap-cursor-color* |
6727 | 525 When Vim enters Insert mode the 't_SI' escape sequence is sent. When Vim |
526 enters Replace mode the 't_SR' escape sequence is sent if it is set, otherwise | |
527 't_SI' is sent. When leaving Insert mode or Replace mode 't_EI' is used. This | |
528 can be used to change the shape or color of the cursor in Insert or Replace | |
529 mode. These are not standard termcap/terminfo entries, you need to set them | |
530 yourself. | |
36 | 531 Example for an xterm, this changes the color of the cursor: > |
532 if &term =~ "xterm" | |
533 let &t_SI = "\<Esc>]12;purple\x7" | |
6727 | 534 let &t_SR = "\<Esc>]12;red\x7" |
36 | 535 let &t_EI = "\<Esc>]12;blue\x7" |
536 endif | |
537 NOTE: When Vim exits the shape for Normal mode will remain. The shape from | |
538 before Vim started will not be restored. | |
2570
71b56b4e7785
Make the references to features in the help more consistent. (Sylvain Hitier)
Bram Moolenaar <bram@vim.org>
parents:
2561
diff
changeset
|
539 {not available when compiled without the |+cursorshape| feature} |
36 | 540 |
7 | 541 *termcap-title* |
542 The 't_ts' and 't_fs' options are used to set the window title if the terminal | |
543 allows title setting via sending strings. They are sent before and after the | |
544 title string, respectively. Similar 't_IS' and 't_IE' are used to set the | |
545 icon text. These are Vim-internal extensions of the Unix termcap, so they | |
546 cannot be obtained from an external termcap. However, the builtin termcap | |
547 contains suitable entries for xterm and iris-ansi, so you don't need to set | |
548 them here. | |
549 *hpterm* | |
550 If inversion or other highlighting does not work correctly, try setting the | |
551 't_xs' option to a non-empty string. This makes the 't_ce' code be used to | |
552 remove highlighting from a line. This is required for "hpterm". Setting the | |
553 'weirdinvert' option has the same effect as making 't_xs' non-empty, and vice | |
554 versa. | |
555 | |
556 *scroll-region* | |
557 Some termcaps do not include an entry for 'cs' (scroll region), although the | |
558 terminal does support it. For example: xterm on a Sun. You can use the | |
559 builtin_xterm or define t_cs yourself. For example: > | |
560 :set t_cs=^V^[[%i%d;%dr | |
561 Where ^V is CTRL-V and ^[ is <Esc>. | |
562 | |
563 The vertical scroll region t_CV is not a standard termcap code. Vim uses it | |
564 internally in the GUI. But it can also be defined for a terminal, if you can | |
565 find one that supports it. The two arguments are the left and right column of | |
566 the region which to restrict the scrolling to. Just like t_cs defines the top | |
567 and bottom lines. Defining t_CV will make scrolling in vertically split | |
568 windows a lot faster. Don't set t_CV when t_da or t_db is set (text isn't | |
569 cleared when scrolling). | |
570 | |
571 Unfortunately it is not possible to deduce from the termcap how cursor | |
572 positioning should be done when using a scrolling region: Relative to the | |
573 beginning of the screen or relative to the beginning of the scrolling region. | |
574 Most terminals use the first method. A known exception is the MS-DOS console | |
575 (pcterm). The 't_CS' option should be set to any string when cursor | |
576 positioning is relative to the start of the scrolling region. It should be | |
577 set to an empty string otherwise. It defaults to "yes" when 'term' is | |
578 "pcterm". | |
579 | |
580 Note for xterm users: The shifted cursor keys normally don't work. You can | |
581 make them work with the xmodmap command and some mappings in Vim. | |
582 | |
583 Give these commands in the xterm: | |
584 xmodmap -e "keysym Up = Up F13" | |
585 xmodmap -e "keysym Down = Down F16" | |
586 xmodmap -e "keysym Left = Left F18" | |
587 xmodmap -e "keysym Right = Right F19" | |
588 | |
589 And use these mappings in Vim: | |
590 :map <t_F3> <S-Up> | |
591 :map! <t_F3> <S-Up> | |
592 :map <t_F6> <S-Down> | |
593 :map! <t_F6> <S-Down> | |
594 :map <t_F8> <S-Left> | |
595 :map! <t_F8> <S-Left> | |
596 :map <t_F9> <S-Right> | |
597 :map! <t_F9> <S-Right> | |
598 | |
599 Instead of, say, <S-Up> you can use any other command that you want to use the | |
600 shift-cursor-up key for. (Note: To help people that have a Sun keyboard with | |
601 left side keys F14 is not used because it is confused with the undo key; F15 | |
602 is not used, because it does a window-to-front; F17 is not used, because it | |
603 closes the window. On other systems you can probably use them.) | |
604 | |
605 ============================================================================== | |
606 3. Window size *window-size* | |
607 | |
608 [This is about the size of the whole window Vim is using, not a window that is | |
609 created with the ":split" command.] | |
610 | |
611 If you are running Vim on an Amiga and the terminal name is "amiga" or | |
612 "builtin_amiga", the amiga-specific window resizing will be enabled. On Unix | |
613 systems three methods are tried to get the window size: | |
614 | |
615 - an ioctl call (TIOCGSIZE or TIOCGWINSZ, depends on your system) | |
616 - the environment variables "LINES" and "COLUMNS" | |
617 - from the termcap entries "li" and "co" | |
618 | |
619 If everything fails a default size of 24 lines and 80 columns is assumed. If | |
620 a window-resize signal is received the size will be set again. If the window | |
621 size is wrong you can use the 'lines' and 'columns' options to set the | |
622 correct values. | |
623 | |
624 One command can be used to set the screen size: | |
625 | |
8951
0bdeaf7092bc
commit https://github.com/vim/vim/commit/aa3b15dbebf333282503d6031e2f9ba6ee4398ed
Christian Brabandt <cb@256bit.org>
parents:
7272
diff
changeset
|
626 *:mod* *:mode* *E359* |
7 | 627 :mod[e] [mode] |
628 | |
629 Without argument this only detects the screen size and redraws the screen. | |
630 With MS-DOS it is possible to switch screen mode. [mode] can be one of these | |
631 values: | |
632 "bw40" 40 columns black&white | |
633 "c40" 40 columns color | |
634 "bw80" 80 columns black&white | |
635 "c80" 80 columns color (most people use this) | |
636 "mono" 80 columns monochrome | |
637 "c4350" 43 or 50 lines EGA/VGA mode | |
638 number mode number to use, depends on your video card | |
639 | |
640 ============================================================================== | |
641 4. Slow and fast terminals *slow-fast-terminal* | |
642 *slow-terminal* | |
643 | |
644 If you have a fast terminal you may like to set the 'ruler' option. The | |
645 cursor position is shown in the status line. If you are using horizontal | |
646 scrolling ('wrap' option off) consider setting 'sidescroll' to a small | |
647 number. | |
648 | |
649 If you have a slow terminal you may want to reset the 'showcmd' option. | |
650 The command characters will not be shown in the status line. If the terminal | |
651 scrolls very slowly, set the 'scrolljump' to 5 or so. If the cursor is moved | |
652 off the screen (e.g., with "j") Vim will scroll 5 lines at a time. Another | |
653 possibility is to reduce the number of lines that Vim uses with the command | |
654 "z{height}<CR>". | |
655 | |
656 If the characters from the terminal are arriving with more than 1 second | |
657 between them you might want to set the 'timeout' and/or 'ttimeout' option. | |
658 See the "Options" chapter |options|. | |
659 | |
660 If your terminal does not support a scrolling region, but it does support | |
661 insert/delete line commands, scrolling with multiple windows may make the | |
662 lines jump up and down. If you don't want this set the 'ttyfast' option. | |
663 This will redraw the window instead of scroll it. | |
664 | |
665 If your terminal scrolls very slowly, but redrawing is not slow, set the | |
666 'ttyscroll' option to a small number, e.g., 3. This will make Vim redraw the | |
667 screen instead of scrolling, when there are more than 3 lines to be scrolled. | |
668 | |
669 If you are using a color terminal that is slow, use this command: > | |
670 hi NonText cterm=NONE ctermfg=NONE | |
671 This avoids that spaces are sent when they have different attributes. On most | |
672 terminals you can't see this anyway. | |
673 | |
674 If you are using Vim over a slow serial line, you might want to try running | |
675 Vim inside the "screen" program. Screen will optimize the terminal I/O quite | |
676 a bit. | |
677 | |
678 If you are testing termcap options, but you cannot see what is happening, | |
679 you might want to set the 'writedelay' option. When non-zero, one character | |
680 is sent to the terminal at a time (does not work for MS-DOS). This makes the | |
681 screen updating a lot slower, making it possible to see what is happening. | |
682 | |
683 ============================================================================== | |
684 5. Using the mouse *mouse-using* | |
685 | |
686 This section is about using the mouse on a terminal or a terminal window. How | |
687 to use the mouse in a GUI window is explained in |gui-mouse|. For scrolling | |
688 with a mouse wheel see |scroll-mouse-wheel|. | |
689 | |
2207
b17bbfa96fa0
Add the settabvar() and gettabvar() functions.
Bram Moolenaar <bram@vim.org>
parents:
2154
diff
changeset
|
690 Don't forget to enable the mouse with this command: > |
7 | 691 :set mouse=a |
692 Otherwise Vim won't recognize the mouse in all modes (See 'mouse'). | |
693 | |
1621 | 694 Currently the mouse is supported for Unix in an xterm window, in a *BSD |
695 console with |sysmouse|, in a Linux console (with GPM |gpm-mouse|), for | |
696 MS-DOS and in a Windows console. | |
7 | 697 Mouse clicks can be used to position the cursor, select an area and paste. |
698 | |
699 These characters in the 'mouse' option tell in which situations the mouse will | |
700 be used by Vim: | |
701 n Normal mode | |
702 v Visual mode | |
703 i Insert mode | |
704 c Command-line mode | |
705 h all previous modes when in a help file | |
706 a all previous modes | |
707 r for |hit-enter| prompt | |
708 | |
709 The default for 'mouse' is empty, the mouse is not used. Normally you would | |
710 do: > | |
711 :set mouse=a | |
712 to start using the mouse (this is equivalent to setting 'mouse' to "nvich"). | |
713 If you only want to use the mouse in a few modes or also want to use it for | |
714 the two questions you will have to concatenate the letters for those modes. | |
715 For example: > | |
716 :set mouse=nv | |
717 Will make the mouse work in Normal mode and Visual mode. > | |
718 :set mouse=h | |
719 Will make the mouse work in help files only (so you can use "g<LeftMouse>" to | |
720 jump to tags). | |
721 | |
722 Whether the selection that is started with the mouse is in Visual mode or | |
723 Select mode depends on whether "mouse" is included in the 'selectmode' | |
724 option. | |
725 | |
726 In an xterm, with the currently active mode included in the 'mouse' option, | |
727 normal mouse clicks are used by Vim, mouse clicks with the shift or ctrl key | |
728 pressed go to the xterm. With the currently active mode not included in | |
729 'mouse' all mouse clicks go to the xterm. | |
730 | |
731 *xterm-clipboard* | |
732 In the Athena and Motif GUI versions, when running in a terminal and there is | |
733 access to the X-server (DISPLAY is set), the copy and paste will behave like | |
734 in the GUI. If not, the middle mouse button will insert the unnamed register. | |
735 In that case, here is how you copy and paste a piece of text: | |
736 | |
737 Copy/paste with the mouse and Visual mode ('mouse' option must be set, see | |
738 above): | |
739 1. Press left mouse button on first letter of text, move mouse pointer to last | |
740 letter of the text and release the button. This will start Visual mode and | |
741 highlight the selected area. | |
742 2. Press "y" to yank the Visual text in the unnamed register. | |
743 3. Click the left mouse button at the insert position. | |
744 4. Click the middle mouse button. | |
745 | |
746 Shortcut: If the insert position is on the screen at the same time as the | |
747 Visual text, you can do 2, 3 and 4 all in one: Click the middle mouse button | |
748 at the insert position. | |
749 | |
750 Note: When the |-X| command line argument is used, Vim will not connect to the | |
751 X server and copy/paste to the X clipboard (selection) will not work. Use the | |
752 shift key with the mouse buttons to let the xterm do the selection. | |
753 | |
754 *xterm-command-server* | |
755 When the X-server clipboard is available, the command server described in | |
756 |x11-clientserver| can be enabled with the --servername command line argument. | |
757 | |
758 *xterm-copy-paste* | |
759 NOTE: In some (older) xterms, it's not possible to move the cursor past column | |
5908 | 760 95 or 223. This is an xterm problem, not Vim's. Get a newer xterm |
761 |color-xterm|. Also see |'ttymouse'|. | |
7 | 762 |
763 Copy/paste in xterm with (current mode NOT included in 'mouse'): | |
764 1. Press left mouse button on first letter of text, move mouse pointer to last | |
765 letter of the text and release the button. | |
766 2. Use normal Vim commands to put the cursor at the insert position. | |
767 3. Press "a" to start Insert mode. | |
768 4. Click the middle mouse button. | |
769 5. Press ESC to end Insert mode. | |
770 (The same can be done with anything in 'mouse' if you keep the shift key | |
771 pressed while using the mouse.) | |
772 | |
773 Note: if you lose the 8th bit when pasting (special characters are translated | |
774 into other characters), you may have to do "stty cs8 -istrip -parenb" in your | |
775 shell before starting Vim. | |
776 | |
777 Thus in an xterm the shift and ctrl keys cannot be used with the mouse. Mouse | |
778 commands requiring the CTRL modifier can be simulated by typing the "g" key | |
779 before using the mouse: | |
780 "g<LeftMouse>" is "<C-LeftMouse> (jump to tag under mouse click) | |
781 "g<RightMouse>" is "<C-RightMouse> ("CTRL-T") | |
782 | |
783 *mouse-mode-table* *mouse-overview* | |
784 A short overview of what the mouse buttons do, when 'mousemodel' is "extend": | |
785 | |
786 Normal Mode: | |
787 event position selection change action ~ | |
788 cursor window ~ | |
789 <LeftMouse> yes end yes | |
790 <C-LeftMouse> yes end yes "CTRL-]" (2) | |
791 <S-LeftMouse> yes no change yes "*" (2) *<S-LeftMouse>* | |
792 <LeftDrag> yes start or extend (1) no *<LeftDrag>* | |
793 <LeftRelease> yes start or extend (1) no | |
794 <MiddleMouse> yes if not active no put | |
795 <MiddleMouse> yes if active no yank and put | |
796 <RightMouse> yes start or extend yes | |
600 | 797 <A-RightMouse> yes start or extend blockw. yes *<A-RightMouse>* |
7 | 798 <S-RightMouse> yes no change yes "#" (2) *<S-RightMouse>* |
799 <C-RightMouse> no no change no "CTRL-T" | |
800 <RightDrag> yes extend no *<RightDrag>* | |
801 <RightRelease> yes extend no *<RightRelease>* | |
802 | |
803 Insert or Replace Mode: | |
804 event position selection change action ~ | |
805 cursor window ~ | |
806 <LeftMouse> yes (cannot be active) yes | |
807 <C-LeftMouse> yes (cannot be active) yes "CTRL-O^]" (2) | |
808 <S-LeftMouse> yes (cannot be active) yes "CTRL-O*" (2) | |
809 <LeftDrag> yes start or extend (1) no like CTRL-O (1) | |
810 <LeftRelease> yes start or extend (1) no like CTRL-O (1) | |
811 <MiddleMouse> no (cannot be active) no put register | |
812 <RightMouse> yes start or extend yes like CTRL-O | |
600 | 813 <A-RightMouse> yes start or extend blockw. yes |
7 | 814 <S-RightMouse> yes (cannot be active) yes "CTRL-O#" (2) |
815 <C-RightMouse> no (cannot be active) no "CTRL-O CTRL-T" | |
816 | |
817 In a help window: | |
818 event position selection change action ~ | |
819 cursor window ~ | |
820 <2-LeftMouse> yes (cannot be active) no "^]" (jump to help tag) | |
821 | |
822 When 'mousemodel' is "popup", these are different: | |
823 | |
824 Normal Mode: | |
825 event position selection change action ~ | |
826 cursor window ~ | |
827 <S-LeftMouse> yes start or extend (1) no | |
600 | 828 <A-LeftMouse> yes start or extend blockw. no *<A-LeftMouse>* |
7 | 829 <RightMouse> no popup menu no |
830 | |
831 Insert or Replace Mode: | |
832 event position selection change action ~ | |
833 cursor window ~ | |
834 <S-LeftMouse> yes start or extend (1) no like CTRL-O (1) | |
600 | 835 <A-LeftMouse> yes start or extend blockw. no |
7 | 836 <RightMouse> no popup menu no |
837 | |
838 (1) only if mouse pointer moved since press | |
839 (2) only if click is in same buffer | |
840 | |
841 Clicking the left mouse button causes the cursor to be positioned. If the | |
842 click is in another window that window is made the active window. When | |
843 editing the command-line the cursor can only be positioned on the | |
844 command-line. When in Insert mode Vim remains in Insert mode. If 'scrolloff' | |
845 is set, and the cursor is positioned within 'scrolloff' lines from the window | |
846 border, the text is scrolled. | |
847 | |
848 A selection can be started by pressing the left mouse button on the first | |
849 character, moving the mouse to the last character, then releasing the mouse | |
850 button. You will not always see the selection until you release the button, | |
851 only in some versions (GUI, MS-DOS, WIN32) will the dragging be shown | |
852 immediately. Note that you can make the text scroll by moving the mouse at | |
853 least one character in the first/last line in the window when 'scrolloff' is | |
854 non-zero. | |
855 | |
856 In Normal, Visual and Select mode clicking the right mouse button causes the | |
857 Visual area to be extended. When 'mousemodel' is "popup", the left button has | |
858 to be used while keeping the shift key pressed. When clicking in a window | |
859 which is editing another buffer, the Visual or Select mode is stopped. | |
860 | |
600 | 861 In Normal, Visual and Select mode clicking the right mouse button with the alt |
1121 | 862 key pressed causes the Visual area to become blockwise. When 'mousemodel' is |
600 | 863 "popup" the left button has to be used with the alt key. Note that this won't |
853 | 864 work on systems where the window manager consumes the mouse events when the |
865 alt key is pressed (it may move the window). | |
600 | 866 |
7 | 867 *double-click* |
868 Double, triple and quadruple clicks are supported when the GUI is active, | |
869 for MS-DOS and Win32, and for an xterm (if the gettimeofday() function is | |
870 available). For selecting text, extra clicks extend the selection: | |
871 click select ~ | |
872 double word or % match *<2-LeftMouse>* | |
873 triple line *<3-LeftMouse>* | |
874 quadruple rectangular block *<4-LeftMouse>* | |
875 Exception: In a Help window a double click jumps to help for the word that is | |
876 clicked on. | |
877 A double click on a word selects that word. 'iskeyword' is used to specify | |
878 which characters are included in a word. A double click on a character | |
879 that has a match selects until that match (like using "v%"). If the match is | |
880 an #if/#else/#endif block, the selection becomes linewise. | |
881 For MS-DOS and xterm the time for double clicking can be set with the | |
882 'mousetime' option. For the other systems this time is defined outside of | |
883 Vim. | |
884 An example, for using a double click to jump to the tag under the cursor: > | |
885 :map <2-LeftMouse> :exe "tag ". expand("<cword>")<CR> | |
886 | |
887 Dragging the mouse with a double click (button-down, button-up, button-down | |
888 and then drag) will result in whole words to be selected. This continues | |
889 until the button is released, at which point the selection is per character | |
890 again. | |
891 | |
892 *gpm-mouse* | |
893 The GPM mouse is only supported when the |+mouse_gpm| feature was enabled at | |
894 compile time. The GPM mouse driver (Linux console) does not support quadruple | |
895 clicks. | |
896 | |
897 In Insert mode, when a selection is started, Vim goes into Normal mode | |
898 temporarily. When Visual or Select mode ends, it returns to Insert mode. | |
899 This is like using CTRL-O in Insert mode. Select mode is used when the | |
900 'selectmode' option contains "mouse". | |
1621 | 901 *sysmouse* |
902 The sysmouse is only supported when the |+mouse_sysmouse| feature was enabled | |
903 at compile time. The sysmouse driver (*BSD console) does not support keyboard | |
904 modifiers. | |
7 | 905 |
906 *drag-status-line* | |
907 When working with several windows, the size of the windows can be changed by | |
908 dragging the status line with the mouse. Point the mouse at a status line, | |
909 press the left button, move the mouse to the new position of the status line, | |
910 release the button. Just clicking the mouse in a status line makes that window | |
911 the current window, without moving the cursor. If by selecting a window it | |
912 will change position or size, the dragging of the status line will look | |
913 confusing, but it will work (just try it). | |
914 | |
915 *<MiddleRelease>* *<MiddleDrag>* | |
916 Mouse clicks can be mapped. The codes for mouse clicks are: | |
917 code mouse button normal action ~ | |
918 <LeftMouse> left pressed set cursor position | |
919 <LeftDrag> left moved while pressed extend selection | |
920 <LeftRelease> left released set selection end | |
921 <MiddleMouse> middle pressed paste text at cursor position | |
922 <MiddleDrag> middle moved while pressed - | |
923 <MiddleRelease> middle released - | |
924 <RightMouse> right pressed extend selection | |
925 <RightDrag> right moved while pressed extend selection | |
926 <RightRelease> right released set selection end | |
927 <X1Mouse> X1 button pressed - *X1Mouse* | |
928 <X1Drag> X1 moved while pressed - *X1Drag* | |
929 <X1Release> X1 button release - *X1Release* | |
930 <X2Mouse> X2 button pressed - *X2Mouse* | |
931 <X2Drag> X2 moved while pressed - *X2Drag* | |
932 <X2Release> X2 button release - *X2Release* | |
933 | |
934 The X1 and X2 buttons refer to the extra buttons found on some mice. The | |
935 'Microsoft Explorer' mouse has these buttons available to the right thumb. | |
7272
17333ebd2bbd
commit https://github.com/vim/vim/commit/d042dc825c9b97dacd84d4728f88300da4d5b6b9
Christian Brabandt <cb@256bit.org>
parents:
6884
diff
changeset
|
936 Currently X1 and X2 only work on Win32 and X11 environments. |
7 | 937 |
938 Examples: > | |
939 :noremap <MiddleMouse> <LeftMouse><MiddleMouse> | |
940 Paste at the position of the middle mouse button click (otherwise the paste | |
941 would be done at the cursor position). > | |
942 | |
943 :noremap <LeftRelease> <LeftRelease>y | |
944 Immediately yank the selection, when using Visual mode. | |
945 | |
946 Note the use of ":noremap" instead of "map" to avoid a recursive mapping. | |
947 > | |
948 :map <X1Mouse> <C-O> | |
949 :map <X2Mouse> <C-I> | |
950 Map the X1 and X2 buttons to go forwards and backwards in the jump list, see | |
951 |CTRL-O| and |CTRL-I|. | |
952 | |
953 *mouse-swap-buttons* | |
954 To swap the meaning of the left and right mouse buttons: > | |
955 :noremap <LeftMouse> <RightMouse> | |
956 :noremap <LeftDrag> <RightDrag> | |
957 :noremap <LeftRelease> <RightRelease> | |
958 :noremap <RightMouse> <LeftMouse> | |
959 :noremap <RightDrag> <LeftDrag> | |
960 :noremap <RightRelease> <LeftRelease> | |
961 :noremap g<LeftMouse> <C-RightMouse> | |
962 :noremap g<RightMouse> <C-LeftMouse> | |
963 :noremap! <LeftMouse> <RightMouse> | |
964 :noremap! <LeftDrag> <RightDrag> | |
965 :noremap! <LeftRelease> <RightRelease> | |
966 :noremap! <RightMouse> <LeftMouse> | |
967 :noremap! <RightDrag> <LeftDrag> | |
968 :noremap! <RightRelease> <LeftRelease> | |
969 < | |
970 vim:tw=78:ts=8:ft=help:norl: |