Mercurial > vim
annotate runtime/doc/term.txt @ 10925:965446be9760
Added tag v8.0.0351 for changeset 053d4ad16f37ce482fbd1b612dc336e8947ccaab
| author | Christian Brabandt <cb@256bit.org> |
|---|---|
| date | Thu, 23 Feb 2017 14:00:06 +0100 |
| parents | 09eb5fd275e0 |
| children | 1218c5353e2b |
| rev | line source |
|---|---|
|
10813
09eb5fd275e0
patch 8.0.0296: bracketed paste can only append, not insert
Christian Brabandt <cb@256bit.org>
parents:
10734
diff
changeset
|
1 *term.txt* For Vim version 8.0. Last change: 2017 Feb 02 |
| 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 |
| 255 OUTPUT CODES | |
| 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'* | |
| 204 | 298 t_Ce undercurl end *t_Ce* *'t_Ce'* |
| 299 t_Cs undercurl mode *t_Cs* *'t_Cs'* | |
| 7 | 300 t_ut clearing uses the current background color *t_ut* *'t_ut'* |
| 301 t_vb visual bell *t_vb* *'t_vb'* | |
| 302 t_ve cursor visible *t_ve* *'t_ve'* | |
| 303 t_vi cursor invisible *t_vi* *'t_vi'* | |
| 304 t_vs cursor very visible *t_vs* *'t_vs'* | |
| 305 *t_xs* *'t_xs'* | |
| 306 t_xs if non-empty, standout not erased by overwriting (hpterm) | |
| 6602 | 307 *t_xn* *'t_xn'* |
| 6647 | 308 t_xn if non-empty, writing a character at the last screen cell |
| 309 does not cause scrolling | |
| 7 | 310 t_ZH italics mode *t_ZH* *'t_ZH'* |
| 311 t_ZR italics end *t_ZR* *'t_ZR'* | |
| 312 | |
| 313 Added by Vim (there are no standard codes for these): | |
| 314 t_IS set icon text start *t_IS* *'t_IS'* | |
| 315 t_IE set icon text end *t_IE* *'t_IE'* | |
| 316 t_WP set window position (Y, X) in pixels *t_WP* *'t_WP'* | |
| 317 t_WS set window size (height, width) in characters *t_WS* *'t_WS'* | |
| 856 | 318 t_SI start insert mode (bar cursor shape) *t_SI* *'t_SI'* |
| 6727 | 319 t_SR start replace mode (underline cursor shape) *t_SR* *'t_SR'* |
| 320 t_EI end insert or replace mode (block cursor shape) *t_EI* *'t_EI'* | |
| 500 | 321 |termcap-cursor-shape| |
| 7 | 322 t_RV request terminal version string (for xterm) *t_RV* *'t_RV'* |
| 323 |xterm-8bit| |v:termresponse| |'ttymouse'| |xterm-codes| | |
| 4229 | 324 t_u7 request cursor position (for xterm) *t_u7* *'t_u7'* |
| 325 see |'ambiwidth'| | |
| 6884 | 326 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
|
327 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
|
328 |xterm-true-color| |
|
c83e2c1e7f2b
commit https://github.com/vim/vim/commit/8a633e3427b47286869aa4b96f2bfc1fe65b25cd
Christian Brabandt <cb@256bit.org>
parents:
8951
diff
changeset
|
329 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
|
330 |xterm-true-color| |
|
10640
27be410d6d29
patch 8.0.0210: no support for bracketed paste
Christian Brabandt <cb@256bit.org>
parents:
10198
diff
changeset
|
331 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
|
332 |xterm-bracketed-paste| |
|
27be410d6d29
patch 8.0.0210: no support for bracketed paste
Christian Brabandt <cb@256bit.org>
parents:
10198
diff
changeset
|
333 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
|
334 |xterm-bracketed-paste| |
| 7 | 335 |
| 336 KEY CODES | |
| 337 Note: Use the <> form if possible | |
| 338 | |
| 339 option name meaning ~ | |
| 340 | |
| 341 t_ku <Up> arrow up *t_ku* *'t_ku'* | |
| 342 t_kd <Down> arrow down *t_kd* *'t_kd'* | |
| 343 t_kr <Right> arrow right *t_kr* *'t_kr'* | |
| 344 t_kl <Left> arrow left *t_kl* *'t_kl'* | |
| 180 | 345 <xUp> alternate arrow up *<xUp>* |
| 346 <xDown> alternate arrow down *<xDown>* | |
| 347 <xRight> alternate arrow right *<xRight>* | |
| 348 <xLeft> alternate arrow left *<xLeft>* | |
| 7 | 349 <S-Up> shift arrow up |
| 350 <S-Down> shift arrow down | |
| 351 t_%i <S-Right> shift arrow right *t_%i* *'t_%i'* | |
| 352 t_#4 <S-Left> shift arrow left *t_#4* *'t_#4'* | |
| 353 t_k1 <F1> function key 1 *t_k1* *'t_k1'* | |
| 354 <xF1> alternate F1 *<xF1>* | |
| 355 t_k2 <F2> function key 2 *<F2>* *t_k2* *'t_k2'* | |
| 356 <xF2> alternate F2 *<xF2>* | |
| 357 t_k3 <F3> function key 3 *<F3>* *t_k3* *'t_k3'* | |
| 358 <xF3> alternate F3 *<xF3>* | |
| 359 t_k4 <F4> function key 4 *<F4>* *t_k4* *'t_k4'* | |
| 360 <xF4> alternate F4 *<xF4>* | |
| 361 t_k5 <F5> function key 5 *<F5>* *t_k5* *'t_k5'* | |
| 362 t_k6 <F6> function key 6 *<F6>* *t_k6* *'t_k6'* | |
| 363 t_k7 <F7> function key 7 *<F7>* *t_k7* *'t_k7'* | |
| 364 t_k8 <F8> function key 8 *<F8>* *t_k8* *'t_k8'* | |
| 365 t_k9 <F9> function key 9 *<F9>* *t_k9* *'t_k9'* | |
| 366 t_k; <F10> function key 10 *<F10>* *t_k;* *'t_k;'* | |
| 4437 | 367 t_F1 <F11> function key 11 *<F11>* *t_F1* *'t_F1'* |
| 7 | 368 t_F2 <F12> function key 12 *<F12>* *t_F2* *'t_F2'* |
| 369 t_F3 <F13> function key 13 *<F13>* *t_F3* *'t_F3'* | |
| 370 t_F4 <F14> function key 14 *<F14>* *t_F4* *'t_F4'* | |
| 371 t_F5 <F15> function key 15 *<F15>* *t_F5* *'t_F5'* | |
| 372 t_F6 <F16> function key 16 *<F16>* *t_F6* *'t_F6'* | |
| 373 t_F7 <F17> function key 17 *<F17>* *t_F7* *'t_F7'* | |
| 374 t_F8 <F18> function key 18 *<F18>* *t_F8* *'t_F8'* | |
| 375 t_F9 <F19> function key 19 *<F19>* *t_F9* *'t_F9'* | |
| 376 <S-F1> shifted function key 1 | |
| 377 <S-xF1> alternate <S-F1> *<S-xF1>* | |
| 378 <S-F2> shifted function key 2 *<S-F2>* | |
| 379 <S-xF2> alternate <S-F2> *<S-xF2>* | |
| 380 <S-F3> shifted function key 3 *<S-F3>* | |
| 381 <S-xF3> alternate <S-F3> *<S-xF3>* | |
| 382 <S-F4> shifted function key 4 *<S-F4>* | |
| 383 <S-xF4> alternate <S-F4> *<S-xF4>* | |
| 384 <S-F5> shifted function key 5 *<S-F5>* | |
| 385 <S-F6> shifted function key 6 *<S-F6>* | |
| 386 <S-F7> shifted function key 7 *<S-F7>* | |
| 387 <S-F8> shifted function key 8 *<S-F8>* | |
| 388 <S-F9> shifted function key 9 *<S-F9>* | |
| 389 <S-F10> shifted function key 10 *<S-F10>* | |
| 390 <S-F11> shifted function key 11 *<S-F11>* | |
| 391 <S-F12> shifted function key 12 *<S-F12>* | |
| 392 t_%1 <Help> help key *t_%1* *'t_%1'* | |
| 393 t_&8 <Undo> undo key *t_&8* *'t_&8'* | |
| 394 t_kI <Insert> insert key *t_kI* *'t_kI'* | |
| 395 t_kD <Del> delete key *t_kD* *'t_kD'* | |
| 396 t_kb <BS> backspace key *t_kb* *'t_kb'* | |
| 4437 | 397 t_kB <S-Tab> back-tab (shift-tab) *<S-Tab>* *t_kB* *'t_kB'* |
| 7 | 398 t_kh <Home> home key *t_kh* *'t_kh'* |
| 4437 | 399 t_#2 <S-Home> shifted home key *<S-Home>* *t_#2* *'t_#2'* |
| 7 | 400 <xHome> alternate home key *<xHome>* |
| 401 t_@7 <End> end key *t_@7* *'t_@7'* | |
| 402 t_*7 <S-End> shifted end key *<S-End>* *t_star7* *'t_star7'* | |
| 403 <xEnd> alternate end key *<xEnd>* | |
| 404 t_kP <PageUp> page-up key *t_kP* *'t_kP'* | |
| 405 t_kN <PageDown> page-down key *t_kN* *'t_kN'* | |
| 406 t_K1 <kHome> keypad home key *t_K1* *'t_K1'* | |
| 407 t_K4 <kEnd> keypad end key *t_K4* *'t_K4'* | |
| 408 t_K3 <kPageUp> keypad page-up key *t_K3* *'t_K3'* | |
| 409 t_K5 <kPageDown> keypad page-down key *t_K5* *'t_K5'* | |
| 410 t_K6 <kPlus> keypad plus key *<kPlus>* *t_K6* *'t_K6'* | |
| 411 t_K7 <kMinus> keypad minus key *<kMinus>* *t_K7* *'t_K7'* | |
| 4437 | 412 t_K8 <kDivide> keypad divide *<kDivide>* *t_K8* *'t_K8'* |
| 413 t_K9 <kMultiply> keypad multiply *<kMultiply>* *t_K9* *'t_K9'* | |
| 7 | 414 t_KA <kEnter> keypad enter key *<kEnter>* *t_KA* *'t_KA'* |
| 415 t_KB <kPoint> keypad decimal point *<kPoint>* *t_KB* *'t_KB'* | |
| 416 t_KC <k0> keypad 0 *<k0>* *t_KC* *'t_KC'* | |
| 417 t_KD <k1> keypad 1 *<k1>* *t_KD* *'t_KD'* | |
| 418 t_KE <k2> keypad 2 *<k2>* *t_KE* *'t_KE'* | |
| 419 t_KF <k3> keypad 3 *<k3>* *t_KF* *'t_KF'* | |
| 420 t_KG <k4> keypad 4 *<k4>* *t_KG* *'t_KG'* | |
| 421 t_KH <k5> keypad 5 *<k5>* *t_KH* *'t_KH'* | |
| 422 t_KI <k6> keypad 6 *<k6>* *t_KI* *'t_KI'* | |
| 423 t_KJ <k7> keypad 7 *<k7>* *t_KJ* *'t_KJ'* | |
| 424 t_KK <k8> keypad 8 *<k8>* *t_KK* *'t_KK'* | |
| 425 t_KL <k9> keypad 9 *<k9>* *t_KL* *'t_KL'* | |
| 426 <Mouse> leader of mouse code *<Mouse>* | |
| 10734 | 427 t_PS start of bracketed paste |xterm-bracketed-paste| *t_PS* 't_PS' |
|
10640
27be410d6d29
patch 8.0.0210: no support for bracketed paste
Christian Brabandt <cb@256bit.org>
parents:
10198
diff
changeset
|
428 t_PE end of bracketed paste |xterm-bracketed-paste| *t_PE* 't_PE' |
| 7 | 429 |
| 430 Note about t_so and t_mr: When the termcap entry "so" is not present the | |
| 431 entry for "mr" is used. And vice versa. The same is done for "se" and "me". | |
| 432 If your terminal supports both inversion and standout mode, you can see two | |
| 433 different modes. If your terminal supports only one of the modes, both will | |
| 434 look the same. | |
| 435 | |
| 33 | 436 *keypad-comma* |
| 7 | 437 The keypad keys, when they are not mapped, behave like the equivalent normal |
| 33 | 438 key. There is one exception: if you have a comma on the keypad instead of a |
| 439 decimal point, Vim will use a dot anyway. Use these mappings to fix that: > | |
| 440 :noremap <kPoint> , | |
| 441 :noremap! <kPoint> , | |
| 442 < *xterm-codes* | |
| 7 | 443 There is a special trick to obtain the key codes which currently only works |
| 444 for xterm. When |t_RV| is defined and a response is received which indicates | |
| 445 an xterm with patchlevel 141 or higher, Vim uses special escape sequences to | |
| 446 request the key codes directly from the xterm. The responses are used to | |
| 447 adjust the various t_ codes. This avoids the problem that the xterm can | |
| 448 produce different codes, depending on the mode it is in (8-bit, VT102, | |
| 449 VT220, etc.). The result is that codes like <xF1> are no longer needed. | |
| 450 Note: This is only done on startup. If the xterm options are changed after | |
| 6530 | 451 Vim has started, the escape sequences may not be recognized anymore. |
| 7 | 452 |
|
8969
c83e2c1e7f2b
commit https://github.com/vim/vim/commit/8a633e3427b47286869aa4b96f2bfc1fe65b25cd
Christian Brabandt <cb@256bit.org>
parents:
8951
diff
changeset
|
453 *xterm-true-color* |
|
c83e2c1e7f2b
commit https://github.com/vim/vim/commit/8a633e3427b47286869aa4b96f2bfc1fe65b25cd
Christian Brabandt <cb@256bit.org>
parents:
8951
diff
changeset
|
454 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
|
455 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
|
456 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
|
457 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
|
458 support true colors. |
|
8969
c83e2c1e7f2b
commit https://github.com/vim/vim/commit/8a633e3427b47286869aa4b96f2bfc1fe65b25cd
Christian Brabandt <cb@256bit.org>
parents:
8951
diff
changeset
|
459 |
|
9027
773d627cac0b
commit https://github.com/vim/vim/commit/61be73bb0f965a895bfb064ea3e55476ac175162
Christian Brabandt <cb@256bit.org>
parents:
8969
diff
changeset
|
460 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
|
461 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
|
462 "^[[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
|
463 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
|
464 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
|
465 less widely supported): > |
|
10140
b11ceef7116e
commit https://github.com/vim/vim/commit/64d8e25bf6efe5f18b032563521c3ce278c316ab
Christian Brabandt <cb@256bit.org>
parents:
9027
diff
changeset
|
466 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
|
467 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
|
468 |
|
773d627cac0b
commit https://github.com/vim/vim/commit/61be73bb0f965a895bfb064ea3e55476ac175162
Christian Brabandt <cb@256bit.org>
parents:
8969
diff
changeset
|
469 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
|
470 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
|
471 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
|
472 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
|
473 |
|
2033
de5a43c5eedc
Update documentation files.
Bram Moolenaar <bram@zimbu.org>
parents:
1702
diff
changeset
|
474 *xterm-resize* |
|
de5a43c5eedc
Update documentation files.
Bram Moolenaar <bram@zimbu.org>
parents:
1702
diff
changeset
|
475 Window resizing with xterm only works if the allowWindowOps resource is |
|
de5a43c5eedc
Update documentation files.
Bram Moolenaar <bram@zimbu.org>
parents:
1702
diff
changeset
|
476 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
|
477 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
|
478 is actually the case. |
|
de5a43c5eedc
Update documentation files.
Bram Moolenaar <bram@zimbu.org>
parents:
1702
diff
changeset
|
479 |
|
de5a43c5eedc
Update documentation files.
Bram Moolenaar <bram@zimbu.org>
parents:
1702
diff
changeset
|
480 To overrule the default, put this line in your ~/.Xdefaults or |
|
de5a43c5eedc
Update documentation files.
Bram Moolenaar <bram@zimbu.org>
parents:
1702
diff
changeset
|
481 ~/.Xresources: |
|
de5a43c5eedc
Update documentation files.
Bram Moolenaar <bram@zimbu.org>
parents:
1702
diff
changeset
|
482 > |
|
de5a43c5eedc
Update documentation files.
Bram Moolenaar <bram@zimbu.org>
parents:
1702
diff
changeset
|
483 XTerm*allowWindowOps: true |
|
de5a43c5eedc
Update documentation files.
Bram Moolenaar <bram@zimbu.org>
parents:
1702
diff
changeset
|
484 |
|
de5a43c5eedc
Update documentation files.
Bram Moolenaar <bram@zimbu.org>
parents:
1702
diff
changeset
|
485 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
|
486 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
|
487 there should be a tick at allow-window-ops. |
|
de5a43c5eedc
Update documentation files.
Bram Moolenaar <bram@zimbu.org>
parents:
1702
diff
changeset
|
488 |
| 7 | 489 *termcap-colors* |
| 490 Note about colors: The 't_Co' option tells Vim the number of colors available. | |
| 491 When it is non-zero, the 't_AB' and 't_AF' options are used to set the color. | |
| 492 If one of these is not available, 't_Sb' and 't_Sf' are used. 't_me' is used | |
| 493 to reset to the default colors. | |
| 494 | |
| 36 | 495 *termcap-cursor-shape* *termcap-cursor-color* |
| 6727 | 496 When Vim enters Insert mode the 't_SI' escape sequence is sent. When Vim |
| 497 enters Replace mode the 't_SR' escape sequence is sent if it is set, otherwise | |
| 498 't_SI' is sent. When leaving Insert mode or Replace mode 't_EI' is used. This | |
| 499 can be used to change the shape or color of the cursor in Insert or Replace | |
| 500 mode. These are not standard termcap/terminfo entries, you need to set them | |
| 501 yourself. | |
| 36 | 502 Example for an xterm, this changes the color of the cursor: > |
| 503 if &term =~ "xterm" | |
| 504 let &t_SI = "\<Esc>]12;purple\x7" | |
| 6727 | 505 let &t_SR = "\<Esc>]12;red\x7" |
| 36 | 506 let &t_EI = "\<Esc>]12;blue\x7" |
| 507 endif | |
| 508 NOTE: When Vim exits the shape for Normal mode will remain. The shape from | |
| 509 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
|
510 {not available when compiled without the |+cursorshape| feature} |
| 36 | 511 |
| 7 | 512 *termcap-title* |
| 513 The 't_ts' and 't_fs' options are used to set the window title if the terminal | |
| 514 allows title setting via sending strings. They are sent before and after the | |
| 515 title string, respectively. Similar 't_IS' and 't_IE' are used to set the | |
| 516 icon text. These are Vim-internal extensions of the Unix termcap, so they | |
| 517 cannot be obtained from an external termcap. However, the builtin termcap | |
| 518 contains suitable entries for xterm and iris-ansi, so you don't need to set | |
| 519 them here. | |
| 520 *hpterm* | |
| 521 If inversion or other highlighting does not work correctly, try setting the | |
| 522 't_xs' option to a non-empty string. This makes the 't_ce' code be used to | |
| 523 remove highlighting from a line. This is required for "hpterm". Setting the | |
| 524 'weirdinvert' option has the same effect as making 't_xs' non-empty, and vice | |
| 525 versa. | |
| 526 | |
| 527 *scroll-region* | |
| 528 Some termcaps do not include an entry for 'cs' (scroll region), although the | |
| 529 terminal does support it. For example: xterm on a Sun. You can use the | |
| 530 builtin_xterm or define t_cs yourself. For example: > | |
| 531 :set t_cs=^V^[[%i%d;%dr | |
| 532 Where ^V is CTRL-V and ^[ is <Esc>. | |
| 533 | |
| 534 The vertical scroll region t_CV is not a standard termcap code. Vim uses it | |
| 535 internally in the GUI. But it can also be defined for a terminal, if you can | |
| 536 find one that supports it. The two arguments are the left and right column of | |
| 537 the region which to restrict the scrolling to. Just like t_cs defines the top | |
| 538 and bottom lines. Defining t_CV will make scrolling in vertically split | |
| 539 windows a lot faster. Don't set t_CV when t_da or t_db is set (text isn't | |
| 540 cleared when scrolling). | |
| 541 | |
| 542 Unfortunately it is not possible to deduce from the termcap how cursor | |
| 543 positioning should be done when using a scrolling region: Relative to the | |
| 544 beginning of the screen or relative to the beginning of the scrolling region. | |
| 545 Most terminals use the first method. A known exception is the MS-DOS console | |
| 546 (pcterm). The 't_CS' option should be set to any string when cursor | |
| 547 positioning is relative to the start of the scrolling region. It should be | |
| 548 set to an empty string otherwise. It defaults to "yes" when 'term' is | |
| 549 "pcterm". | |
| 550 | |
| 551 Note for xterm users: The shifted cursor keys normally don't work. You can | |
| 552 make them work with the xmodmap command and some mappings in Vim. | |
| 553 | |
| 554 Give these commands in the xterm: | |
| 555 xmodmap -e "keysym Up = Up F13" | |
| 556 xmodmap -e "keysym Down = Down F16" | |
| 557 xmodmap -e "keysym Left = Left F18" | |
| 558 xmodmap -e "keysym Right = Right F19" | |
| 559 | |
| 560 And use these mappings in Vim: | |
| 561 :map <t_F3> <S-Up> | |
| 562 :map! <t_F3> <S-Up> | |
| 563 :map <t_F6> <S-Down> | |
| 564 :map! <t_F6> <S-Down> | |
| 565 :map <t_F8> <S-Left> | |
| 566 :map! <t_F8> <S-Left> | |
| 567 :map <t_F9> <S-Right> | |
| 568 :map! <t_F9> <S-Right> | |
| 569 | |
| 570 Instead of, say, <S-Up> you can use any other command that you want to use the | |
| 571 shift-cursor-up key for. (Note: To help people that have a Sun keyboard with | |
| 572 left side keys F14 is not used because it is confused with the undo key; F15 | |
| 573 is not used, because it does a window-to-front; F17 is not used, because it | |
| 574 closes the window. On other systems you can probably use them.) | |
| 575 | |
| 576 ============================================================================== | |
| 577 3. Window size *window-size* | |
| 578 | |
| 579 [This is about the size of the whole window Vim is using, not a window that is | |
| 580 created with the ":split" command.] | |
| 581 | |
| 582 If you are running Vim on an Amiga and the terminal name is "amiga" or | |
| 583 "builtin_amiga", the amiga-specific window resizing will be enabled. On Unix | |
| 584 systems three methods are tried to get the window size: | |
| 585 | |
| 586 - an ioctl call (TIOCGSIZE or TIOCGWINSZ, depends on your system) | |
| 587 - the environment variables "LINES" and "COLUMNS" | |
| 588 - from the termcap entries "li" and "co" | |
| 589 | |
| 590 If everything fails a default size of 24 lines and 80 columns is assumed. If | |
| 591 a window-resize signal is received the size will be set again. If the window | |
| 592 size is wrong you can use the 'lines' and 'columns' options to set the | |
| 593 correct values. | |
| 594 | |
| 595 One command can be used to set the screen size: | |
| 596 | |
|
8951
0bdeaf7092bc
commit https://github.com/vim/vim/commit/aa3b15dbebf333282503d6031e2f9ba6ee4398ed
Christian Brabandt <cb@256bit.org>
parents:
7272
diff
changeset
|
597 *:mod* *:mode* *E359* |
| 7 | 598 :mod[e] [mode] |
| 599 | |
| 600 Without argument this only detects the screen size and redraws the screen. | |
| 601 With MS-DOS it is possible to switch screen mode. [mode] can be one of these | |
| 602 values: | |
| 603 "bw40" 40 columns black&white | |
| 604 "c40" 40 columns color | |
| 605 "bw80" 80 columns black&white | |
| 606 "c80" 80 columns color (most people use this) | |
| 607 "mono" 80 columns monochrome | |
| 608 "c4350" 43 or 50 lines EGA/VGA mode | |
| 609 number mode number to use, depends on your video card | |
| 610 | |
| 611 ============================================================================== | |
| 612 4. Slow and fast terminals *slow-fast-terminal* | |
| 613 *slow-terminal* | |
| 614 | |
| 615 If you have a fast terminal you may like to set the 'ruler' option. The | |
| 616 cursor position is shown in the status line. If you are using horizontal | |
| 617 scrolling ('wrap' option off) consider setting 'sidescroll' to a small | |
| 618 number. | |
| 619 | |
| 620 If you have a slow terminal you may want to reset the 'showcmd' option. | |
| 621 The command characters will not be shown in the status line. If the terminal | |
| 622 scrolls very slowly, set the 'scrolljump' to 5 or so. If the cursor is moved | |
| 623 off the screen (e.g., with "j") Vim will scroll 5 lines at a time. Another | |
| 624 possibility is to reduce the number of lines that Vim uses with the command | |
| 625 "z{height}<CR>". | |
| 626 | |
| 627 If the characters from the terminal are arriving with more than 1 second | |
| 628 between them you might want to set the 'timeout' and/or 'ttimeout' option. | |
| 629 See the "Options" chapter |options|. | |
| 630 | |
| 631 If your terminal does not support a scrolling region, but it does support | |
| 632 insert/delete line commands, scrolling with multiple windows may make the | |
| 633 lines jump up and down. If you don't want this set the 'ttyfast' option. | |
| 634 This will redraw the window instead of scroll it. | |
| 635 | |
| 636 If your terminal scrolls very slowly, but redrawing is not slow, set the | |
| 637 'ttyscroll' option to a small number, e.g., 3. This will make Vim redraw the | |
| 638 screen instead of scrolling, when there are more than 3 lines to be scrolled. | |
| 639 | |
| 640 If you are using a color terminal that is slow, use this command: > | |
| 641 hi NonText cterm=NONE ctermfg=NONE | |
| 642 This avoids that spaces are sent when they have different attributes. On most | |
| 643 terminals you can't see this anyway. | |
| 644 | |
| 645 If you are using Vim over a slow serial line, you might want to try running | |
| 646 Vim inside the "screen" program. Screen will optimize the terminal I/O quite | |
| 647 a bit. | |
| 648 | |
| 649 If you are testing termcap options, but you cannot see what is happening, | |
| 650 you might want to set the 'writedelay' option. When non-zero, one character | |
| 651 is sent to the terminal at a time (does not work for MS-DOS). This makes the | |
| 652 screen updating a lot slower, making it possible to see what is happening. | |
| 653 | |
| 654 ============================================================================== | |
| 655 5. Using the mouse *mouse-using* | |
| 656 | |
| 657 This section is about using the mouse on a terminal or a terminal window. How | |
| 658 to use the mouse in a GUI window is explained in |gui-mouse|. For scrolling | |
| 659 with a mouse wheel see |scroll-mouse-wheel|. | |
| 660 | |
|
2207
b17bbfa96fa0
Add the settabvar() and gettabvar() functions.
Bram Moolenaar <bram@vim.org>
parents:
2154
diff
changeset
|
661 Don't forget to enable the mouse with this command: > |
| 7 | 662 :set mouse=a |
| 663 Otherwise Vim won't recognize the mouse in all modes (See 'mouse'). | |
| 664 | |
| 1621 | 665 Currently the mouse is supported for Unix in an xterm window, in a *BSD |
| 666 console with |sysmouse|, in a Linux console (with GPM |gpm-mouse|), for | |
| 667 MS-DOS and in a Windows console. | |
| 7 | 668 Mouse clicks can be used to position the cursor, select an area and paste. |
| 669 | |
| 670 These characters in the 'mouse' option tell in which situations the mouse will | |
| 671 be used by Vim: | |
| 672 n Normal mode | |
| 673 v Visual mode | |
| 674 i Insert mode | |
| 675 c Command-line mode | |
| 676 h all previous modes when in a help file | |
| 677 a all previous modes | |
| 678 r for |hit-enter| prompt | |
| 679 | |
| 680 The default for 'mouse' is empty, the mouse is not used. Normally you would | |
| 681 do: > | |
| 682 :set mouse=a | |
| 683 to start using the mouse (this is equivalent to setting 'mouse' to "nvich"). | |
| 684 If you only want to use the mouse in a few modes or also want to use it for | |
| 685 the two questions you will have to concatenate the letters for those modes. | |
| 686 For example: > | |
| 687 :set mouse=nv | |
| 688 Will make the mouse work in Normal mode and Visual mode. > | |
| 689 :set mouse=h | |
| 690 Will make the mouse work in help files only (so you can use "g<LeftMouse>" to | |
| 691 jump to tags). | |
| 692 | |
| 693 Whether the selection that is started with the mouse is in Visual mode or | |
| 694 Select mode depends on whether "mouse" is included in the 'selectmode' | |
| 695 option. | |
| 696 | |
| 697 In an xterm, with the currently active mode included in the 'mouse' option, | |
| 698 normal mouse clicks are used by Vim, mouse clicks with the shift or ctrl key | |
| 699 pressed go to the xterm. With the currently active mode not included in | |
| 700 'mouse' all mouse clicks go to the xterm. | |
| 701 | |
| 702 *xterm-clipboard* | |
| 703 In the Athena and Motif GUI versions, when running in a terminal and there is | |
| 704 access to the X-server (DISPLAY is set), the copy and paste will behave like | |
| 705 in the GUI. If not, the middle mouse button will insert the unnamed register. | |
| 706 In that case, here is how you copy and paste a piece of text: | |
| 707 | |
| 708 Copy/paste with the mouse and Visual mode ('mouse' option must be set, see | |
| 709 above): | |
| 710 1. Press left mouse button on first letter of text, move mouse pointer to last | |
| 711 letter of the text and release the button. This will start Visual mode and | |
| 712 highlight the selected area. | |
| 713 2. Press "y" to yank the Visual text in the unnamed register. | |
| 714 3. Click the left mouse button at the insert position. | |
| 715 4. Click the middle mouse button. | |
| 716 | |
| 717 Shortcut: If the insert position is on the screen at the same time as the | |
| 718 Visual text, you can do 2, 3 and 4 all in one: Click the middle mouse button | |
| 719 at the insert position. | |
| 720 | |
| 721 Note: When the |-X| command line argument is used, Vim will not connect to the | |
| 722 X server and copy/paste to the X clipboard (selection) will not work. Use the | |
| 723 shift key with the mouse buttons to let the xterm do the selection. | |
| 724 | |
| 725 *xterm-command-server* | |
| 726 When the X-server clipboard is available, the command server described in | |
| 727 |x11-clientserver| can be enabled with the --servername command line argument. | |
| 728 | |
| 729 *xterm-copy-paste* | |
| 730 NOTE: In some (older) xterms, it's not possible to move the cursor past column | |
| 5908 | 731 95 or 223. This is an xterm problem, not Vim's. Get a newer xterm |
| 732 |color-xterm|. Also see |'ttymouse'|. | |
| 7 | 733 |
| 734 Copy/paste in xterm with (current mode NOT included in 'mouse'): | |
| 735 1. Press left mouse button on first letter of text, move mouse pointer to last | |
| 736 letter of the text and release the button. | |
| 737 2. Use normal Vim commands to put the cursor at the insert position. | |
| 738 3. Press "a" to start Insert mode. | |
| 739 4. Click the middle mouse button. | |
| 740 5. Press ESC to end Insert mode. | |
| 741 (The same can be done with anything in 'mouse' if you keep the shift key | |
| 742 pressed while using the mouse.) | |
| 743 | |
| 744 Note: if you lose the 8th bit when pasting (special characters are translated | |
| 745 into other characters), you may have to do "stty cs8 -istrip -parenb" in your | |
| 746 shell before starting Vim. | |
| 747 | |
| 748 Thus in an xterm the shift and ctrl keys cannot be used with the mouse. Mouse | |
| 749 commands requiring the CTRL modifier can be simulated by typing the "g" key | |
| 750 before using the mouse: | |
| 751 "g<LeftMouse>" is "<C-LeftMouse> (jump to tag under mouse click) | |
| 752 "g<RightMouse>" is "<C-RightMouse> ("CTRL-T") | |
| 753 | |
| 754 *mouse-mode-table* *mouse-overview* | |
| 755 A short overview of what the mouse buttons do, when 'mousemodel' is "extend": | |
| 756 | |
| 757 Normal Mode: | |
| 758 event position selection change action ~ | |
| 759 cursor window ~ | |
| 760 <LeftMouse> yes end yes | |
| 761 <C-LeftMouse> yes end yes "CTRL-]" (2) | |
| 762 <S-LeftMouse> yes no change yes "*" (2) *<S-LeftMouse>* | |
| 763 <LeftDrag> yes start or extend (1) no *<LeftDrag>* | |
| 764 <LeftRelease> yes start or extend (1) no | |
| 765 <MiddleMouse> yes if not active no put | |
| 766 <MiddleMouse> yes if active no yank and put | |
| 767 <RightMouse> yes start or extend yes | |
| 600 | 768 <A-RightMouse> yes start or extend blockw. yes *<A-RightMouse>* |
| 7 | 769 <S-RightMouse> yes no change yes "#" (2) *<S-RightMouse>* |
| 770 <C-RightMouse> no no change no "CTRL-T" | |
| 771 <RightDrag> yes extend no *<RightDrag>* | |
| 772 <RightRelease> yes extend no *<RightRelease>* | |
| 773 | |
| 774 Insert or Replace Mode: | |
| 775 event position selection change action ~ | |
| 776 cursor window ~ | |
| 777 <LeftMouse> yes (cannot be active) yes | |
| 778 <C-LeftMouse> yes (cannot be active) yes "CTRL-O^]" (2) | |
| 779 <S-LeftMouse> yes (cannot be active) yes "CTRL-O*" (2) | |
| 780 <LeftDrag> yes start or extend (1) no like CTRL-O (1) | |
| 781 <LeftRelease> yes start or extend (1) no like CTRL-O (1) | |
| 782 <MiddleMouse> no (cannot be active) no put register | |
| 783 <RightMouse> yes start or extend yes like CTRL-O | |
| 600 | 784 <A-RightMouse> yes start or extend blockw. yes |
| 7 | 785 <S-RightMouse> yes (cannot be active) yes "CTRL-O#" (2) |
| 786 <C-RightMouse> no (cannot be active) no "CTRL-O CTRL-T" | |
| 787 | |
| 788 In a help window: | |
| 789 event position selection change action ~ | |
| 790 cursor window ~ | |
| 791 <2-LeftMouse> yes (cannot be active) no "^]" (jump to help tag) | |
| 792 | |
| 793 When 'mousemodel' is "popup", these are different: | |
| 794 | |
| 795 Normal Mode: | |
| 796 event position selection change action ~ | |
| 797 cursor window ~ | |
| 798 <S-LeftMouse> yes start or extend (1) no | |
| 600 | 799 <A-LeftMouse> yes start or extend blockw. no *<A-LeftMouse>* |
| 7 | 800 <RightMouse> no popup menu no |
| 801 | |
| 802 Insert or Replace Mode: | |
| 803 event position selection change action ~ | |
| 804 cursor window ~ | |
| 805 <S-LeftMouse> yes start or extend (1) no like CTRL-O (1) | |
| 600 | 806 <A-LeftMouse> yes start or extend blockw. no |
| 7 | 807 <RightMouse> no popup menu no |
| 808 | |
| 809 (1) only if mouse pointer moved since press | |
| 810 (2) only if click is in same buffer | |
| 811 | |
| 812 Clicking the left mouse button causes the cursor to be positioned. If the | |
| 813 click is in another window that window is made the active window. When | |
| 814 editing the command-line the cursor can only be positioned on the | |
| 815 command-line. When in Insert mode Vim remains in Insert mode. If 'scrolloff' | |
| 816 is set, and the cursor is positioned within 'scrolloff' lines from the window | |
| 817 border, the text is scrolled. | |
| 818 | |
| 819 A selection can be started by pressing the left mouse button on the first | |
| 820 character, moving the mouse to the last character, then releasing the mouse | |
| 821 button. You will not always see the selection until you release the button, | |
| 822 only in some versions (GUI, MS-DOS, WIN32) will the dragging be shown | |
| 823 immediately. Note that you can make the text scroll by moving the mouse at | |
| 824 least one character in the first/last line in the window when 'scrolloff' is | |
| 825 non-zero. | |
| 826 | |
| 827 In Normal, Visual and Select mode clicking the right mouse button causes the | |
| 828 Visual area to be extended. When 'mousemodel' is "popup", the left button has | |
| 829 to be used while keeping the shift key pressed. When clicking in a window | |
| 830 which is editing another buffer, the Visual or Select mode is stopped. | |
| 831 | |
| 600 | 832 In Normal, Visual and Select mode clicking the right mouse button with the alt |
| 1121 | 833 key pressed causes the Visual area to become blockwise. When 'mousemodel' is |
| 600 | 834 "popup" the left button has to be used with the alt key. Note that this won't |
| 853 | 835 work on systems where the window manager consumes the mouse events when the |
| 836 alt key is pressed (it may move the window). | |
| 600 | 837 |
| 7 | 838 *double-click* |
| 839 Double, triple and quadruple clicks are supported when the GUI is active, | |
| 840 for MS-DOS and Win32, and for an xterm (if the gettimeofday() function is | |
| 841 available). For selecting text, extra clicks extend the selection: | |
| 842 click select ~ | |
| 843 double word or % match *<2-LeftMouse>* | |
| 844 triple line *<3-LeftMouse>* | |
| 845 quadruple rectangular block *<4-LeftMouse>* | |
| 846 Exception: In a Help window a double click jumps to help for the word that is | |
| 847 clicked on. | |
| 848 A double click on a word selects that word. 'iskeyword' is used to specify | |
| 849 which characters are included in a word. A double click on a character | |
| 850 that has a match selects until that match (like using "v%"). If the match is | |
| 851 an #if/#else/#endif block, the selection becomes linewise. | |
| 852 For MS-DOS and xterm the time for double clicking can be set with the | |
| 853 'mousetime' option. For the other systems this time is defined outside of | |
| 854 Vim. | |
| 855 An example, for using a double click to jump to the tag under the cursor: > | |
| 856 :map <2-LeftMouse> :exe "tag ". expand("<cword>")<CR> | |
| 857 | |
| 858 Dragging the mouse with a double click (button-down, button-up, button-down | |
| 859 and then drag) will result in whole words to be selected. This continues | |
| 860 until the button is released, at which point the selection is per character | |
| 861 again. | |
| 862 | |
| 863 *gpm-mouse* | |
| 864 The GPM mouse is only supported when the |+mouse_gpm| feature was enabled at | |
| 865 compile time. The GPM mouse driver (Linux console) does not support quadruple | |
| 866 clicks. | |
| 867 | |
| 868 In Insert mode, when a selection is started, Vim goes into Normal mode | |
| 869 temporarily. When Visual or Select mode ends, it returns to Insert mode. | |
| 870 This is like using CTRL-O in Insert mode. Select mode is used when the | |
| 871 'selectmode' option contains "mouse". | |
| 1621 | 872 *sysmouse* |
| 873 The sysmouse is only supported when the |+mouse_sysmouse| feature was enabled | |
| 874 at compile time. The sysmouse driver (*BSD console) does not support keyboard | |
| 875 modifiers. | |
| 7 | 876 |
| 877 *drag-status-line* | |
| 878 When working with several windows, the size of the windows can be changed by | |
| 879 dragging the status line with the mouse. Point the mouse at a status line, | |
| 880 press the left button, move the mouse to the new position of the status line, | |
| 881 release the button. Just clicking the mouse in a status line makes that window | |
| 882 the current window, without moving the cursor. If by selecting a window it | |
| 883 will change position or size, the dragging of the status line will look | |
| 884 confusing, but it will work (just try it). | |
| 885 | |
| 886 *<MiddleRelease>* *<MiddleDrag>* | |
| 887 Mouse clicks can be mapped. The codes for mouse clicks are: | |
| 888 code mouse button normal action ~ | |
| 889 <LeftMouse> left pressed set cursor position | |
| 890 <LeftDrag> left moved while pressed extend selection | |
| 891 <LeftRelease> left released set selection end | |
| 892 <MiddleMouse> middle pressed paste text at cursor position | |
| 893 <MiddleDrag> middle moved while pressed - | |
| 894 <MiddleRelease> middle released - | |
| 895 <RightMouse> right pressed extend selection | |
| 896 <RightDrag> right moved while pressed extend selection | |
| 897 <RightRelease> right released set selection end | |
| 898 <X1Mouse> X1 button pressed - *X1Mouse* | |
| 899 <X1Drag> X1 moved while pressed - *X1Drag* | |
| 900 <X1Release> X1 button release - *X1Release* | |
| 901 <X2Mouse> X2 button pressed - *X2Mouse* | |
| 902 <X2Drag> X2 moved while pressed - *X2Drag* | |
| 903 <X2Release> X2 button release - *X2Release* | |
| 904 | |
| 905 The X1 and X2 buttons refer to the extra buttons found on some mice. The | |
| 906 '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
|
907 Currently X1 and X2 only work on Win32 and X11 environments. |
| 7 | 908 |
| 909 Examples: > | |
| 910 :noremap <MiddleMouse> <LeftMouse><MiddleMouse> | |
| 911 Paste at the position of the middle mouse button click (otherwise the paste | |
| 912 would be done at the cursor position). > | |
| 913 | |
| 914 :noremap <LeftRelease> <LeftRelease>y | |
| 915 Immediately yank the selection, when using Visual mode. | |
| 916 | |
| 917 Note the use of ":noremap" instead of "map" to avoid a recursive mapping. | |
| 918 > | |
| 919 :map <X1Mouse> <C-O> | |
| 920 :map <X2Mouse> <C-I> | |
| 921 Map the X1 and X2 buttons to go forwards and backwards in the jump list, see | |
| 922 |CTRL-O| and |CTRL-I|. | |
| 923 | |
| 924 *mouse-swap-buttons* | |
| 925 To swap the meaning of the left and right mouse buttons: > | |
| 926 :noremap <LeftMouse> <RightMouse> | |
| 927 :noremap <LeftDrag> <RightDrag> | |
| 928 :noremap <LeftRelease> <RightRelease> | |
| 929 :noremap <RightMouse> <LeftMouse> | |
| 930 :noremap <RightDrag> <LeftDrag> | |
| 931 :noremap <RightRelease> <LeftRelease> | |
| 932 :noremap g<LeftMouse> <C-RightMouse> | |
| 933 :noremap g<RightMouse> <C-LeftMouse> | |
| 934 :noremap! <LeftMouse> <RightMouse> | |
| 935 :noremap! <LeftDrag> <RightDrag> | |
| 936 :noremap! <LeftRelease> <RightRelease> | |
| 937 :noremap! <RightMouse> <LeftMouse> | |
| 938 :noremap! <RightDrag> <LeftDrag> | |
| 939 :noremap! <RightRelease> <LeftRelease> | |
| 940 < | |
| 941 vim:tw=78:ts=8:ft=help:norl: |