Mercurial > vim
annotate runtime/doc/insert.txt @ 19973:9f5758ee0b10 v8.2.0542
patch 8.2.0542: no test for E386
Commit: https://github.com/vim/vim/commit/8832a3457831707286dd2d9252ba14a5f9fd4c60
Author: Bram Moolenaar <Bram@vim.org>
Date: Sat Apr 11 18:36:38 2020 +0200
patch 8.2.0542: no test for E386
Problem: No test for E386.
Solution: Add a test. (Dominique Pelle, closes https://github.com/vim/vim/issues/5911)
| author | Bram Moolenaar <Bram@vim.org> |
|---|---|
| date | Sat, 11 Apr 2020 18:45:03 +0200 |
| parents | 1908e92b02fd |
| children | 252d2bb90394 |
| rev | line source |
|---|---|
| 19813 | 1 *insert.txt* For Vim version 8.2. Last change: 2020 Mar 25 |
| 7 | 2 |
| 3 | |
| 4 VIM REFERENCE MANUAL by Bram Moolenaar | |
| 5 | |
| 6 | |
| 7 *Insert* *Insert-mode* | |
| 8 Inserting and replacing text *mode-ins-repl* | |
| 9 | |
| 10 Most of this file is about Insert and Replace mode. At the end are a few | |
| 11 commands for inserting text in other ways. | |
| 12 | |
| 13 An overview of the most often used commands can be found in chapter 24 of the | |
| 14 user manual |usr_24.txt|. | |
| 15 | |
| 16 1. Special keys |ins-special-keys| | |
| 17 2. Special special keys |ins-special-special| | |
| 18 3. 'textwidth' and 'wrapmargin' options |ins-textwidth| | |
| 19 4. 'expandtab', 'smarttab' and 'softtabstop' options |ins-expandtab| | |
| 20 5. Replace mode |Replace-mode| | |
| 21 6. Virtual Replace mode |Virtual-Replace-mode| | |
| 22 7. Insert mode completion |ins-completion| | |
| 23 8. Insert mode commands |inserting| | |
| 24 9. Ex insert commands |inserting-ex| | |
| 25 10. Inserting a file |inserting-file| | |
| 26 | |
| 27 Also see 'virtualedit', for moving the cursor to positions where there is no | |
| 28 character. Useful for editing a table. | |
| 29 | |
| 30 ============================================================================== | |
| 31 1. Special keys *ins-special-keys* | |
| 32 | |
| 33 In Insert and Replace mode, the following characters have a special meaning; | |
| 34 other characters are inserted directly. To insert one of these special | |
| 35 characters into the buffer, precede it with CTRL-V. To insert a <Nul> | |
| 36 character use "CTRL-V CTRL-@" or "CTRL-V 000". On some systems, you have to | |
| 37 use "CTRL-V 003" to insert a CTRL-C. Note: When CTRL-V is mapped you can | |
| 38 often use CTRL-Q instead |i_CTRL-Q|. | |
| 39 | |
| 40 If you are working in a special language mode when inserting text, see the | |
| 41 'langmap' option, |'langmap'|, on how to avoid switching this mode on and off | |
| 42 all the time. | |
| 43 | |
| 44 If you have 'insertmode' set, <Esc> and a few other keys get another meaning. | |
| 45 See |'insertmode'|. | |
| 46 | |
| 47 char action ~ | |
| 48 ----------------------------------------------------------------------- | |
| 49 *i_CTRL-[* *i_<Esc>* | |
| 50 <Esc> or CTRL-[ End insert or Replace mode, go back to Normal mode. Finish | |
| 51 abbreviation. | |
| 52 Note: If your <Esc> key is hard to hit on your keyboard, train | |
| 53 yourself to use CTRL-[. | |
| 6153 | 54 If Esc doesn't work and you are using a Mac, try CTRL-Esc. |
| 55 Or disable Listening under Accessibility preferences. | |
| 7 | 56 *i_CTRL-C* |
| 57 CTRL-C Quit insert mode, go back to Normal mode. Do not check for | |
| 140 | 58 abbreviations. Does not trigger the |InsertLeave| autocommand |
| 59 event. | |
| 7 | 60 |
| 61 *i_CTRL-@* | |
| 16610 | 62 CTRL-@ Insert previously inserted text and stop insert. |
| 63 | |
| 7 | 64 *i_CTRL-A* |
|
16553
0e473e9e70c2
patch 8.1.1280: remarks about functionality not in Vi clutters the help
Bram Moolenaar <Bram@vim.org>
parents:
16267
diff
changeset
|
65 CTRL-A Insert previously inserted text. |
| 7 | 66 |
| 67 *i_CTRL-H* *i_<BS>* *i_BS* | |
| 68 <BS> or CTRL-H Delete the character before the cursor (see |i_backspacing| | |
| 69 about joining lines). | |
| 70 See |:fixdel| if your <BS> key does not do what you want. | |
| 16610 | 71 |
| 7 | 72 *i_<Del>* *i_DEL* |
| 73 <Del> Delete the character under the cursor. If the cursor is at | |
| 74 the end of the line, and the 'backspace' option includes | |
| 75 "eol", delete the <EOL>; the next line is appended after the | |
| 76 current one. | |
| 77 See |:fixdel| if your <Del> key does not do what you want. | |
| 78 *i_CTRL-W* | |
| 79 CTRL-W Delete the word before the cursor (see |i_backspacing| about | |
| 80 joining lines). See the section "word motions", | |
| 81 |word-motions|, for the definition of a word. | |
| 82 *i_CTRL-U* | |
| 6823 | 83 CTRL-U Delete all entered characters before the cursor in the current |
| 6884 | 84 line. If there are no newly entered characters and |
| 85 'backspace' is not empty, delete all characters before the | |
| 6823 | 86 cursor in the current line. |
| 87 See |i_backspacing| about joining lines. | |
| 7 | 88 *i_CTRL-I* *i_<Tab>* *i_Tab* |
| 89 <Tab> or CTRL-I Insert a tab. If the 'expandtab' option is on, the | |
| 90 equivalent number of spaces is inserted (use CTRL-V <Tab> to | |
| 91 avoid the expansion; use CTRL-Q <Tab> if CTRL-V is mapped | |
| 92 |i_CTRL-Q|). See also the 'smarttab' option and | |
| 93 |ins-expandtab|. | |
| 94 *i_CTRL-J* *i_<NL>* | |
| 95 <NL> or CTRL-J Begin new line. | |
| 96 *i_CTRL-M* *i_<CR>* | |
| 97 <CR> or CTRL-M Begin new line. | |
| 98 *i_CTRL-K* | |
| 99 CTRL-K {char1} [char2] | |
| 100 Enter digraph (see |digraphs|). When {char1} is a special | |
| 101 key, the code for that key is inserted in <> form. For | |
| 102 example, the string "<S-Space>" can be entered by typing | |
| 103 <C-K><S-Space> (two keys). Neither char is considered for | |
|
16553
0e473e9e70c2
patch 8.1.1280: remarks about functionality not in Vi clutters the help
Bram Moolenaar <Bram@vim.org>
parents:
16267
diff
changeset
|
104 mapping. |
| 7 | 105 |
|
16553
0e473e9e70c2
patch 8.1.1280: remarks about functionality not in Vi clutters the help
Bram Moolenaar <Bram@vim.org>
parents:
16267
diff
changeset
|
106 CTRL-N Find next keyword (see |i_CTRL-N|). |
|
0e473e9e70c2
patch 8.1.1280: remarks about functionality not in Vi clutters the help
Bram Moolenaar <Bram@vim.org>
parents:
16267
diff
changeset
|
107 CTRL-P Find previous keyword (see |i_CTRL-P|). |
| 7 | 108 |
| 18186 | 109 CTRL-R {register} *i_CTRL-R* |
| 7 | 110 Insert the contents of a register. Between typing CTRL-R and |
| 111 the second character, '"' will be displayed to indicate that | |
| 112 you are expected to enter the name of a register. | |
| 113 The text is inserted as if you typed it, but mappings and | |
| 114 abbreviations are not used. If you have options like | |
| 115 'textwidth', 'formatoptions', or 'autoindent' set, this will | |
| 116 influence what will be inserted. This is different from what | |
| 117 happens with the "p" command and pasting with the mouse. | |
| 118 Special registers: | |
| 119 '"' the unnamed register, containing the text of | |
| 120 the last delete or yank | |
| 121 '%' the current file name | |
| 122 '#' the alternate file name | |
| 123 '*' the clipboard contents (X11: primary selection) | |
| 124 '+' the clipboard contents | |
| 125 '/' the last search pattern | |
| 126 ':' the last command-line | |
| 127 '.' the last inserted text | |
| 128 '-' the last small (less than a line) delete | |
|
2033
de5a43c5eedc
Update documentation files.
Bram Moolenaar <bram@zimbu.org>
parents:
1702
diff
changeset
|
129 *i_CTRL-R_=* |
| 7 | 130 '=' the expression register: you are prompted to |
| 131 enter an expression (see |expression|) | |
| 36 | 132 Note that 0x80 (128 decimal) is used for |
| 667 | 133 special keys. E.g., you can use this to move |
| 134 the cursor up: | |
| 135 CTRL-R ="\<Up>" | |
| 136 Use CTRL-R CTRL-R to insert text literally. | |
| 714 | 137 When the result is a |List| the items are used |
| 138 as lines. They can have line breaks inside | |
| 139 too. | |
|
2033
de5a43c5eedc
Update documentation files.
Bram Moolenaar <bram@zimbu.org>
parents:
1702
diff
changeset
|
140 When the result is a Float it's automatically |
|
de5a43c5eedc
Update documentation files.
Bram Moolenaar <bram@zimbu.org>
parents:
1702
diff
changeset
|
141 converted to a String. |
|
5130
71e066e10a47
updated for version 7.3.1308
Bram Moolenaar <bram@vim.org>
parents:
4869
diff
changeset
|
142 When append() or setline() is invoked the undo |
|
71e066e10a47
updated for version 7.3.1308
Bram Moolenaar <bram@vim.org>
parents:
4869
diff
changeset
|
143 sequence will be broken. |
|
16553
0e473e9e70c2
patch 8.1.1280: remarks about functionality not in Vi clutters the help
Bram Moolenaar <Bram@vim.org>
parents:
16267
diff
changeset
|
144 See |registers| about registers. |
| 7 | 145 |
| 18186 | 146 CTRL-R CTRL-R {register} *i_CTRL-R_CTRL-R* |
| 7 | 147 Insert the contents of a register. Works like using a single |
| 148 CTRL-R, but the text is inserted literally, not as if typed. | |
| 149 This differs when the register contains characters like <BS>. | |
| 150 Example, where register a contains "ab^Hc": > | |
| 151 CTRL-R a results in "ac". | |
| 152 CTRL-R CTRL-R a results in "ab^Hc". | |
| 153 < Options 'textwidth', 'formatoptions', etc. still apply. If | |
|
7147
c590de398af9
commit https://github.com/vim/vim/commit/ca63501fbcd1cf9c8aa9ff12c093c95b62a89ed7
Christian Brabandt <cb@256bit.org>
parents:
7100
diff
changeset
|
154 you also want to avoid these, use CTRL-R CTRL-O, see below. |
| 7 | 155 The '.' register (last inserted text) is still inserted as |
|
16553
0e473e9e70c2
patch 8.1.1280: remarks about functionality not in Vi clutters the help
Bram Moolenaar <Bram@vim.org>
parents:
16267
diff
changeset
|
156 typed. |
| 19968 | 157 After this command, the '.' register contains the text from |
| 158 the register as if it was inserted by typing it. | |
| 7 | 159 |
| 18186 | 160 CTRL-R CTRL-O {register} *i_CTRL-R_CTRL-O* |
| 7 | 161 Insert the contents of a register literally and don't |
| 162 auto-indent. Does the same as pasting with the mouse | |
| 11347 | 163 |<MiddleMouse>|. When the register is linewise this will |
| 164 insert the text above the current line, like with `P`. | |
| 7 | 165 Does not replace characters! |
| 166 The '.' register (last inserted text) is still inserted as | |
|
16553
0e473e9e70c2
patch 8.1.1280: remarks about functionality not in Vi clutters the help
Bram Moolenaar <Bram@vim.org>
parents:
16267
diff
changeset
|
167 typed. |
| 19968 | 168 After this command, the '.' register contains the command |
| 169 typed and not the text. I.e., the literals "^R^O" and not the | |
| 170 text from the register. | |
| 7 | 171 |
| 18186 | 172 CTRL-R CTRL-P {register} *i_CTRL-R_CTRL-P* |
| 7 | 173 Insert the contents of a register literally and fix the |
| 174 indent, like |[<MiddleMouse>|. | |
| 175 Does not replace characters! | |
| 176 The '.' register (last inserted text) is still inserted as | |
|
16553
0e473e9e70c2
patch 8.1.1280: remarks about functionality not in Vi clutters the help
Bram Moolenaar <Bram@vim.org>
parents:
16267
diff
changeset
|
177 typed. |
| 19968 | 178 After this command, the '.' register contains the command |
| 179 typed and not the text. I.e., the literals "^R^P" and not the | |
| 180 text from the register. | |
| 7 | 181 |
| 182 *i_CTRL-T* | |
| 183 CTRL-T Insert one shiftwidth of indent at the start of the current | |
| 184 line. The indent is always rounded to a 'shiftwidth' (this is | |
| 16610 | 185 vi compatible). |
| 7 | 186 *i_CTRL-D* |
| 187 CTRL-D Delete one shiftwidth of indent at the start of the current | |
| 188 line. The indent is always rounded to a 'shiftwidth' (this is | |
| 16610 | 189 vi compatible). |
| 7 | 190 *i_0_CTRL-D* |
| 16610 | 191 0 CTRL-D Delete all indent in the current line. |
| 192 | |
| 7 | 193 *i_^_CTRL-D* |
| 194 ^ CTRL-D Delete all indent in the current line. The indent is | |
| 195 restored in the next line. This is useful when inserting a | |
| 16610 | 196 label. |
| 7 | 197 |
| 198 *i_CTRL-V* | |
| 199 CTRL-V Insert next non-digit literally. For special keys, the | |
| 200 terminal code is inserted. It's also possible to enter the | |
| 201 decimal, octal or hexadecimal value of a character | |
| 202 |i_CTRL-V_digit|. | |
| 203 The characters typed right after CTRL-V are not considered for | |
| 16610 | 204 mapping. |
| 7 | 205 Note: When CTRL-V is mapped (e.g., to paste text) you can |
| 206 often use CTRL-Q instead |i_CTRL-Q|. | |
|
18717
14d2a210fab1
patch 8.1.2350: other text for CTRL-V in Insert mode with modifyOtherKeys
Bram Moolenaar <Bram@vim.org>
parents:
18396
diff
changeset
|
207 When |modifyOtherKeys| is enabled then special Escape sequence |
|
14d2a210fab1
patch 8.1.2350: other text for CTRL-V in Insert mode with modifyOtherKeys
Bram Moolenaar <Bram@vim.org>
parents:
18396
diff
changeset
|
208 is converted back to what it was without |modifyOtherKeys|, |
|
14d2a210fab1
patch 8.1.2350: other text for CTRL-V in Insert mode with modifyOtherKeys
Bram Moolenaar <Bram@vim.org>
parents:
18396
diff
changeset
|
209 unless the Shift key is also pressed. |
|
14d2a210fab1
patch 8.1.2350: other text for CTRL-V in Insert mode with modifyOtherKeys
Bram Moolenaar <Bram@vim.org>
parents:
18396
diff
changeset
|
210 |
| 7 | 211 *i_CTRL-Q* |
| 212 CTRL-Q Same as CTRL-V. | |
| 213 Note: Some terminal connections may eat CTRL-Q, it doesn't | |
| 214 work then. It does work in the GUI. | |
| 215 | |
| 19116 | 216 CTRL-SHIFT-V *i_CTRL-SHIFT-V* *i_CTRL-SHIFT-Q* |
| 217 CTRL-SHIFT-Q Works just like CTRL-V, unless |modifyOtherKeys| is active, | |
| 218 then it inserts the Escape sequence for a key with modifiers. | |
| 219 | |
| 7 | 220 CTRL-X Enter CTRL-X mode. This is a sub-mode where commands can |
| 236 | 221 be given to complete words or scroll the window. See |
|
16553
0e473e9e70c2
patch 8.1.1280: remarks about functionality not in Vi clutters the help
Bram Moolenaar <Bram@vim.org>
parents:
16267
diff
changeset
|
222 |i_CTRL-X| and |ins-completion|. |
| 7 | 223 |
| 224 *i_CTRL-E* | |
|
16553
0e473e9e70c2
patch 8.1.1280: remarks about functionality not in Vi clutters the help
Bram Moolenaar <Bram@vim.org>
parents:
16267
diff
changeset
|
225 CTRL-E Insert the character which is below the cursor. |
| 7 | 226 *i_CTRL-Y* |
|
16553
0e473e9e70c2
patch 8.1.1280: remarks about functionality not in Vi clutters the help
Bram Moolenaar <Bram@vim.org>
parents:
16267
diff
changeset
|
227 CTRL-Y Insert the character which is above the cursor. |
| 7 | 228 Note that for CTRL-E and CTRL-Y 'textwidth' is not used, to be |
| 229 able to copy characters from a long line. | |
| 230 | |
| 231 *i_CTRL-_* | |
| 232 CTRL-_ Switch between languages, as follows: | |
| 233 - When in a rightleft window, revins and nohkmap are toggled, | |
| 234 since English will likely be inserted in this case. | |
| 235 - When in a norightleft window, revins and hkmap are toggled, | |
| 236 since Hebrew will likely be inserted in this case. | |
| 237 | |
| 238 CTRL-_ moves the cursor to the end of the typed text. | |
| 239 | |
| 240 This command is only available when the 'allowrevins' option | |
| 241 is set. | |
| 242 Please refer to |rileft.txt| for more information about | |
| 243 right-to-left mode. | |
| 1121 | 244 Only if compiled with the |+rightleft| feature. |
| 245 | |
| 7 | 246 *i_CTRL-^* |
| 247 CTRL-^ Toggle the use of typing language characters. | |
| 248 When language |:lmap| mappings are defined: | |
| 249 - If 'iminsert' is 1 (langmap mappings used) it becomes 0 (no | |
| 250 langmap mappings used). | |
| 251 - If 'iminsert' has another value it becomes 1, thus langmap | |
| 252 mappings are enabled. | |
| 253 When no language mappings are defined: | |
| 254 - If 'iminsert' is 2 (Input Method used) it becomes 0 (no | |
| 255 Input Method used). | |
| 256 - If 'iminsert' has another value it becomes 2, thus the Input | |
| 257 Method is enabled. | |
| 258 When set to 1, the value of the "b:keymap_name" variable, the | |
| 259 'keymap' option or "<lang>" appears in the status line. | |
| 260 The language mappings are normally used to type characters | |
| 261 that are different from what the keyboard produces. The | |
| 262 'keymap' option can be used to install a whole number of them. | |
| 263 | |
| 264 *i_CTRL-]* | |
|
16553
0e473e9e70c2
patch 8.1.1280: remarks about functionality not in Vi clutters the help
Bram Moolenaar <Bram@vim.org>
parents:
16267
diff
changeset
|
265 CTRL-] Trigger abbreviation, without inserting a character. |
| 7 | 266 |
| 267 *i_<Insert>* | |
|
16553
0e473e9e70c2
patch 8.1.1280: remarks about functionality not in Vi clutters the help
Bram Moolenaar <Bram@vim.org>
parents:
16267
diff
changeset
|
268 <Insert> Toggle between Insert and Replace mode. |
| 7 | 269 ----------------------------------------------------------------------- |
| 270 | |
| 271 *i_backspacing* | |
| 272 The effect of the <BS>, CTRL-W, and CTRL-U depend on the 'backspace' option | |
| 273 (unless 'revins' is set). This is a comma separated list of items: | |
| 274 | |
| 275 item action ~ | |
| 276 indent allow backspacing over autoindent | |
| 277 eol allow backspacing over end-of-line (join lines) | |
| 278 start allow backspacing over the start position of insert; CTRL-W and | |
| 279 CTRL-U stop once at the start position | |
| 280 | |
| 281 When 'backspace' is empty, Vi compatible backspacing is used. You cannot | |
| 282 backspace over autoindent, before column 1 or before where insert started. | |
| 283 | |
| 284 For backwards compatibility the values "0", "1" and "2" are also allowed, see | |
| 285 |'backspace'|. | |
| 286 | |
| 287 If the 'backspace' option does contain "eol" and the cursor is in column 1 | |
| 288 when one of the three keys is used, the current line is joined with the | |
| 289 previous line. This effectively deletes the <EOL> in front of the cursor. | |
| 290 | |
| 291 *i_CTRL-V_digit* | |
| 292 With CTRL-V the decimal, octal or hexadecimal value of a character can be | |
| 293 entered directly. This way you can enter any character, except a line break | |
| 294 (<NL>, value 10). There are five ways to enter the character value: | |
| 295 | |
| 296 first char mode max nr of chars max value ~ | |
| 297 (none) decimal 3 255 | |
| 236 | 298 o or O octal 3 377 (255) |
| 7 | 299 x or X hexadecimal 2 ff (255) |
| 300 u hexadecimal 4 ffff (65535) | |
| 301 U hexadecimal 8 7fffffff (2147483647) | |
| 302 | |
| 303 Normally you would type the maximum number of characters. Thus to enter a | |
| 304 space (value 32) you would type <C-V>032. You can omit the leading zero, in | |
| 305 which case the character typed after the number must be a non-digit. This | |
| 306 happens for the other modes as well: As soon as you type a character that is | |
| 307 invalid for the mode, the value before it will be used and the "invalid" | |
| 308 character is dealt with in the normal way. | |
| 309 | |
| 310 If you enter a value of 10, it will end up in the file as a 0. The 10 is a | |
| 311 <NL>, which is used internally to represent the <Nul> character. When writing | |
| 312 the buffer to a file, the <NL> character is translated into <Nul>. The <NL> | |
| 313 character is written at the end of each line. Thus if you want to insert a | |
| 314 <NL> character in a file you will have to make a line break. | |
| 315 | |
| 316 *i_CTRL-X* *insert_expand* | |
| 317 CTRL-X enters a sub-mode where several commands can be used. Most of these | |
|
17809
59f8948b7590
patch 8.1.1901: the +insert_expand feature is not always available
Bram Moolenaar <Bram@vim.org>
parents:
17771
diff
changeset
|
318 commands do keyword completion; see |ins-completion|. |
| 7 | 319 |
| 320 Two commands can be used to scroll the window up or down, without exiting | |
| 321 insert mode: | |
| 322 | |
| 323 *i_CTRL-X_CTRL-E* | |
| 324 CTRL-X CTRL-E scroll window one line up. | |
| 816 | 325 When doing completion look here: |complete_CTRL-E| |
| 7 | 326 |
| 327 *i_CTRL-X_CTRL-Y* | |
| 328 CTRL-X CTRL-Y scroll window one line down. | |
| 816 | 329 When doing completion look here: |complete_CTRL-Y| |
| 7 | 330 |
| 331 After CTRL-X is pressed, each CTRL-E (CTRL-Y) scrolls the window up (down) by | |
| 332 one line unless that would cause the cursor to move from its current position | |
| 333 in the file. As soon as another key is pressed, CTRL-X mode is exited and | |
| 334 that key is interpreted as in Insert mode. | |
| 335 | |
| 336 | |
| 337 ============================================================================== | |
| 338 2. Special special keys *ins-special-special* | |
| 339 | |
| 340 The following keys are special. They stop the current insert, do something, | |
| 341 and then restart insertion. This means you can do something without getting | |
| 342 out of Insert mode. This is very handy if you prefer to use the Insert mode | |
| 343 all the time, just like editors that don't have a separate Normal mode. You | |
| 344 may also want to set the 'backspace' option to "indent,eol,start" and set the | |
| 345 'insertmode' option. You can use CTRL-O if you want to map a function key to | |
| 346 a command. | |
| 347 | |
| 348 The changes (inserted or deleted characters) before and after these keys can | |
| 349 be undone separately. Only the last change can be redone and always behaves | |
| 350 like an "i" command. | |
| 351 | |
| 352 char action ~ | |
| 353 ----------------------------------------------------------------------- | |
| 354 <Up> cursor one line up *i_<Up>* | |
| 355 <Down> cursor one line down *i_<Down>* | |
| 356 CTRL-G <Up> cursor one line up, insert start column *i_CTRL-G_<Up>* | |
| 357 CTRL-G k cursor one line up, insert start column *i_CTRL-G_k* | |
| 358 CTRL-G CTRL-K cursor one line up, insert start column *i_CTRL-G_CTRL-K* | |
| 359 CTRL-G <Down> cursor one line down, insert start column *i_CTRL-G_<Down>* | |
| 360 CTRL-G j cursor one line down, insert start column *i_CTRL-G_j* | |
| 361 CTRL-G CTRL-J cursor one line down, insert start column *i_CTRL-G_CTRL-J* | |
| 362 <Left> cursor one character left *i_<Left>* | |
| 363 <Right> cursor one character right *i_<Right>* | |
| 364 <S-Left> cursor one word back (like "b" command) *i_<S-Left>* | |
| 365 <C-Left> cursor one word back (like "b" command) *i_<C-Left>* | |
| 366 <S-Right> cursor one word forward (like "w" command) *i_<S-Right>* | |
| 367 <C-Right> cursor one word forward (like "w" command) *i_<C-Right>* | |
| 368 <Home> cursor to first char in the line *i_<Home>* | |
| 369 <End> cursor to after last char in the line *i_<End>* | |
| 370 <C-Home> cursor to first char in the file *i_<C-Home>* | |
| 371 <C-End> cursor to after last char in the file *i_<C-End>* | |
| 372 <LeftMouse> cursor to position of mouse click *i_<LeftMouse>* | |
| 373 <S-Up> move window one page up *i_<S-Up>* | |
| 374 <PageUp> move window one page up *i_<PageUp>* | |
| 375 <S-Down> move window one page down *i_<S-Down>* | |
| 376 <PageDown> move window one page down *i_<PageDown>* | |
|
2409
0ca06a92adfb
Add support for horizontal scroll wheel. (Bjorn Winckler)
Bram Moolenaar <bram@vim.org>
parents:
2365
diff
changeset
|
377 <ScrollWheelDown> move window three lines down *i_<ScrollWheelDown>* |
|
0ca06a92adfb
Add support for horizontal scroll wheel. (Bjorn Winckler)
Bram Moolenaar <bram@vim.org>
parents:
2365
diff
changeset
|
378 <S-ScrollWheelDown> move window one page down *i_<S-ScrollWheelDown>* |
|
0ca06a92adfb
Add support for horizontal scroll wheel. (Bjorn Winckler)
Bram Moolenaar <bram@vim.org>
parents:
2365
diff
changeset
|
379 <ScrollWheelUp> move window three lines up *i_<ScrollWheelUp>* |
|
0ca06a92adfb
Add support for horizontal scroll wheel. (Bjorn Winckler)
Bram Moolenaar <bram@vim.org>
parents:
2365
diff
changeset
|
380 <S-ScrollWheelUp> move window one page up *i_<S-ScrollWheelUp>* |
|
0ca06a92adfb
Add support for horizontal scroll wheel. (Bjorn Winckler)
Bram Moolenaar <bram@vim.org>
parents:
2365
diff
changeset
|
381 <ScrollWheelLeft> move window six columns left *i_<ScrollWheelLeft>* |
|
0ca06a92adfb
Add support for horizontal scroll wheel. (Bjorn Winckler)
Bram Moolenaar <bram@vim.org>
parents:
2365
diff
changeset
|
382 <S-ScrollWheelLeft> move window one page left *i_<S-ScrollWheelLeft>* |
|
0ca06a92adfb
Add support for horizontal scroll wheel. (Bjorn Winckler)
Bram Moolenaar <bram@vim.org>
parents:
2365
diff
changeset
|
383 <ScrollWheelRight> move window six columns right *i_<ScrollWheelRight>* |
|
0ca06a92adfb
Add support for horizontal scroll wheel. (Bjorn Winckler)
Bram Moolenaar <bram@vim.org>
parents:
2365
diff
changeset
|
384 <S-ScrollWheelRight> move window one page right *i_<S-ScrollWheelRight>* |
| 7 | 385 CTRL-O execute one command, return to Insert mode *i_CTRL-O* |
| 625 | 386 CTRL-\ CTRL-O like CTRL-O but don't move the cursor *i_CTRL-\_CTRL-O* |
| 477 | 387 CTRL-L when 'insertmode' is set: go to Normal mode *i_CTRL-L* |
| 7 | 388 CTRL-G u break undo sequence, start new change *i_CTRL-G_u* |
|
7074
c8efa41dd451
commit https://github.com/vim/vim/commit/8b5f65a527c353b9942e362e719687c3a7592309
Christian Brabandt <cb@256bit.org>
parents:
6884
diff
changeset
|
389 CTRL-G U don't break undo with next left/right cursor *i_CTRL-G_U* |
| 19813 | 390 movement, if the cursor stays within the |
| 391 same line | |
| 7 | 392 ----------------------------------------------------------------------- |
| 393 | |
| 394 Note: If the cursor keys take you out of Insert mode, check the 'noesckeys' | |
| 395 option. | |
| 396 | |
| 397 The CTRL-O command sometimes has a side effect: If the cursor was beyond the | |
| 398 end of the line, it will be put on the last character in the line. In | |
| 399 mappings it's often better to use <Esc> (first put an "x" in the text, <Esc> | |
| 477 | 400 will then always put the cursor on it). Or use CTRL-\ CTRL-O, but then |
| 4073 | 401 beware of the cursor possibly being beyond the end of the line. Note that the |
| 402 command following CTRL-\ CTRL-O can still move the cursor, it is not restored | |
| 403 to its original position. | |
| 7 | 404 |
| 2625 | 405 The CTRL-O command takes you to Normal mode. If you then use a command enter |
| 3492 | 406 Insert mode again it normally doesn't nest. Thus when typing "a<C-O>a" and |
| 407 then <Esc> takes you back to Normal mode, you do not need to type <Esc> twice. | |
| 408 An exception is when not typing the command, e.g. when executing a mapping or | |
| 409 sourcing a script. This makes mappings work that briefly switch to Insert | |
| 410 mode. | |
| 2625 | 411 |
| 7 | 412 The shifted cursor keys are not available on all terminals. |
| 413 | |
| 414 Another side effect is that a count specified before the "i" or "a" command is | |
| 415 ignored. That is because repeating the effect of the command after CTRL-O is | |
| 416 too complicated. | |
| 417 | |
| 418 An example for using CTRL-G u: > | |
| 419 | |
| 420 :inoremap <C-H> <C-G>u<C-H> | |
| 421 | |
| 422 This redefines the backspace key to start a new undo sequence. You can now | |
| 423 undo the effect of the backspace key, without changing what you typed before | |
| 3456 | 424 that, with CTRL-O u. Another example: > |
| 425 | |
| 426 :inoremap <CR> <C-]><C-G>u<CR> | |
| 427 | |
| 428 This breaks undo at each line break. It also expands abbreviations before | |
| 429 this. | |
| 7 | 430 |
|
7074
c8efa41dd451
commit https://github.com/vim/vim/commit/8b5f65a527c353b9942e362e719687c3a7592309
Christian Brabandt <cb@256bit.org>
parents:
6884
diff
changeset
|
431 An example for using CTRL-G U: > |
|
c8efa41dd451
commit https://github.com/vim/vim/commit/8b5f65a527c353b9942e362e719687c3a7592309
Christian Brabandt <cb@256bit.org>
parents:
6884
diff
changeset
|
432 |
|
c8efa41dd451
commit https://github.com/vim/vim/commit/8b5f65a527c353b9942e362e719687c3a7592309
Christian Brabandt <cb@256bit.org>
parents:
6884
diff
changeset
|
433 inoremap <Left> <C-G>U<Left> |
|
c8efa41dd451
commit https://github.com/vim/vim/commit/8b5f65a527c353b9942e362e719687c3a7592309
Christian Brabandt <cb@256bit.org>
parents:
6884
diff
changeset
|
434 inoremap <Right> <C-G>U<Right> |
|
c8efa41dd451
commit https://github.com/vim/vim/commit/8b5f65a527c353b9942e362e719687c3a7592309
Christian Brabandt <cb@256bit.org>
parents:
6884
diff
changeset
|
435 inoremap <expr> <Home> col('.') == match(getline('.'), '\S') + 1 ? |
|
c8efa41dd451
commit https://github.com/vim/vim/commit/8b5f65a527c353b9942e362e719687c3a7592309
Christian Brabandt <cb@256bit.org>
parents:
6884
diff
changeset
|
436 \ repeat('<C-G>U<Left>', col('.') - 1) : |
|
c8efa41dd451
commit https://github.com/vim/vim/commit/8b5f65a527c353b9942e362e719687c3a7592309
Christian Brabandt <cb@256bit.org>
parents:
6884
diff
changeset
|
437 \ (col('.') < match(getline('.'), '\S') ? |
|
c8efa41dd451
commit https://github.com/vim/vim/commit/8b5f65a527c353b9942e362e719687c3a7592309
Christian Brabandt <cb@256bit.org>
parents:
6884
diff
changeset
|
438 \ repeat('<C-G>U<Right>', match(getline('.'), '\S') + 0) : |
|
c8efa41dd451
commit https://github.com/vim/vim/commit/8b5f65a527c353b9942e362e719687c3a7592309
Christian Brabandt <cb@256bit.org>
parents:
6884
diff
changeset
|
439 \ repeat('<C-G>U<Left>', col('.') - 1 - match(getline('.'), '\S'))) |
|
c8efa41dd451
commit https://github.com/vim/vim/commit/8b5f65a527c353b9942e362e719687c3a7592309
Christian Brabandt <cb@256bit.org>
parents:
6884
diff
changeset
|
440 inoremap <expr> <End> repeat('<C-G>U<Right>', col('$') - col('.')) |
|
c8efa41dd451
commit https://github.com/vim/vim/commit/8b5f65a527c353b9942e362e719687c3a7592309
Christian Brabandt <cb@256bit.org>
parents:
6884
diff
changeset
|
441 inoremap ( ()<C-G>U<Left> |
|
c8efa41dd451
commit https://github.com/vim/vim/commit/8b5f65a527c353b9942e362e719687c3a7592309
Christian Brabandt <cb@256bit.org>
parents:
6884
diff
changeset
|
442 |
|
c8efa41dd451
commit https://github.com/vim/vim/commit/8b5f65a527c353b9942e362e719687c3a7592309
Christian Brabandt <cb@256bit.org>
parents:
6884
diff
changeset
|
443 This makes it possible to use the cursor keys in Insert mode, without breaking |
| 13125 | 444 the undo sequence and therefore using |.| (redo) will work as expected. |
| 14123 | 445 Also entering a text like (with the "(" mapping from above): |
|
7074
c8efa41dd451
commit https://github.com/vim/vim/commit/8b5f65a527c353b9942e362e719687c3a7592309
Christian Brabandt <cb@256bit.org>
parents:
6884
diff
changeset
|
446 |
|
c8efa41dd451
commit https://github.com/vim/vim/commit/8b5f65a527c353b9942e362e719687c3a7592309
Christian Brabandt <cb@256bit.org>
parents:
6884
diff
changeset
|
447 Lorem ipsum (dolor |
|
c8efa41dd451
commit https://github.com/vim/vim/commit/8b5f65a527c353b9942e362e719687c3a7592309
Christian Brabandt <cb@256bit.org>
parents:
6884
diff
changeset
|
448 |
| 14123 | 449 will be repeatable by using |.| to the expected |
|
7074
c8efa41dd451
commit https://github.com/vim/vim/commit/8b5f65a527c353b9942e362e719687c3a7592309
Christian Brabandt <cb@256bit.org>
parents:
6884
diff
changeset
|
450 |
|
c8efa41dd451
commit https://github.com/vim/vim/commit/8b5f65a527c353b9942e362e719687c3a7592309
Christian Brabandt <cb@256bit.org>
parents:
6884
diff
changeset
|
451 Lorem ipsum (dolor) |
|
c8efa41dd451
commit https://github.com/vim/vim/commit/8b5f65a527c353b9942e362e719687c3a7592309
Christian Brabandt <cb@256bit.org>
parents:
6884
diff
changeset
|
452 |
| 10 | 453 Using CTRL-O splits undo: the text typed before and after it is undone |
| 454 separately. If you want to avoid this (e.g., in a mapping) you might be able | |
| 455 to use CTRL-R = |i_CTRL-R|. E.g., to call a function: > | |
| 456 :imap <F2> <C-R>=MyFunc()<CR> | |
| 457 | |
| 7 | 458 When the 'whichwrap' option is set appropriately, the <Left> and <Right> |
| 459 keys on the first/last character in the line make the cursor wrap to the | |
| 460 previous/next line. | |
| 461 | |
| 462 The CTRL-G j and CTRL-G k commands can be used to insert text in front of a | |
| 463 column. Example: > | |
| 464 int i; | |
| 465 int j; | |
| 236 | 466 Position the cursor on the first "int", type "istatic <C-G>j ". The |
| 7 | 467 result is: > |
| 468 static int i; | |
| 469 int j; | |
| 470 When inserting the same text in front of the column in every line, use the | |
| 471 Visual blockwise command "I" |v_b_I|. | |
| 472 | |
| 473 ============================================================================== | |
| 474 3. 'textwidth' and 'wrapmargin' options *ins-textwidth* | |
| 475 | |
| 476 The 'textwidth' option can be used to automatically break a line before it | |
| 477 gets too long. Set the 'textwidth' option to the desired maximum line | |
| 478 length. If you then type more characters (not spaces or tabs), the | |
| 479 last word will be put on a new line (unless it is the only word on the | |
| 480 line). If you set 'textwidth' to 0, this feature is disabled. | |
| 481 | |
| 482 The 'wrapmargin' option does almost the same. The difference is that | |
| 483 'textwidth' has a fixed width while 'wrapmargin' depends on the width of the | |
| 484 screen. When using 'wrapmargin' this is equal to using 'textwidth' with a | |
| 485 value equal to (columns - 'wrapmargin'), where columns is the width of the | |
| 486 screen. | |
| 487 | |
| 488 When 'textwidth' and 'wrapmargin' are both set, 'textwidth' is used. | |
| 489 | |
| 490 If you don't really want to break the line, but view the line wrapped at a | |
| 491 convenient place, see the 'linebreak' option. | |
| 492 | |
| 667 | 493 The line is only broken automatically when using Insert mode, or when |
| 7 | 494 appending to a line. When in replace mode and the line length is not |
| 495 changed, the line will not be broken. | |
| 496 | |
| 497 Long lines are broken if you enter a non-white character after the margin. | |
| 498 The situations where a line will be broken can be restricted by adding | |
| 499 characters to the 'formatoptions' option: | |
| 500 "l" Only break a line if it was not longer than 'textwidth' when the insert | |
| 501 started. | |
| 502 "v" Only break at a white character that has been entered during the | |
| 503 current insert command. This is mostly Vi-compatible. | |
| 504 "lv" Only break if the line was not longer than 'textwidth' when the insert | |
| 505 started and only at a white character that has been entered during the | |
| 506 current insert command. Only differs from "l" when entering non-white | |
| 507 characters while crossing the 'textwidth' boundary. | |
| 508 | |
| 667 | 509 Normally an internal function will be used to decide where to break the line. |
| 510 If you want to do it in a different way set the 'formatexpr' option to an | |
| 511 expression that will take care of the line break. | |
| 512 | |
| 7 | 513 If you want to format a block of text, you can use the "gq" operator. Type |
| 514 "gq" and a movement command to move the cursor to the end of the block. In | |
| 515 many cases, the command "gq}" will do what you want (format until the end of | |
| 516 paragraph). Alternatively, you can use "gqap", which will format the whole | |
| 517 paragraph, no matter where the cursor currently is. Or you can use Visual | |
| 518 mode: hit "v", move to the end of the block, and type "gq". See also |gq|. | |
| 519 | |
| 520 ============================================================================== | |
| 521 4. 'expandtab', 'smarttab' and 'softtabstop' options *ins-expandtab* | |
| 522 | |
| 523 If the 'expandtab' option is on, spaces will be used to fill the amount of | |
| 524 whitespace of the tab. If you want to enter a real <Tab>, type CTRL-V first | |
| 525 (use CTRL-Q when CTRL-V is mapped |i_CTRL-Q|). | |
| 526 The 'expandtab' option is off by default. Note that in Replace mode, a single | |
| 527 character is replaced with several spaces. The result of this is that the | |
| 528 number of characters in the line increases. Backspacing will delete one | |
| 529 space at a time. The original character will be put back for only one space | |
|
16553
0e473e9e70c2
patch 8.1.1280: remarks about functionality not in Vi clutters the help
Bram Moolenaar <Bram@vim.org>
parents:
16267
diff
changeset
|
530 that you backspace over (the last one). |
| 7 | 531 |
| 532 *ins-smarttab* | |
| 533 When the 'smarttab' option is on, a <Tab> inserts 'shiftwidth' positions at | |
| 534 the beginning of a line and 'tabstop' positions in other places. This means | |
| 3682 | 535 that often spaces instead of a <Tab> character are inserted. When 'smarttab' |
| 7 | 536 is off, a <Tab> always inserts 'tabstop' positions, and 'shiftwidth' is only |
|
16553
0e473e9e70c2
patch 8.1.1280: remarks about functionality not in Vi clutters the help
Bram Moolenaar <Bram@vim.org>
parents:
16267
diff
changeset
|
537 used for ">>" and the like. |
| 7 | 538 |
| 539 *ins-softtabstop* | |
| 540 When the 'softtabstop' option is non-zero, a <Tab> inserts 'softtabstop' | |
| 541 positions, and a <BS> used to delete white space, will delete 'softtabstop' | |
| 542 positions. This feels like 'tabstop' was set to 'softtabstop', but a real | |
| 543 <Tab> character still takes 'tabstop' positions, so your file will still look | |
| 544 correct when used by other applications. | |
| 545 | |
| 546 If 'softtabstop' is non-zero, a <BS> will try to delete as much white space to | |
| 547 move to the previous 'softtabstop' position, except when the previously | |
| 548 inserted character is a space, then it will only delete the character before | |
| 549 the cursor. Otherwise you cannot always delete a single character before the | |
| 550 cursor. You will have to delete 'softtabstop' characters first, and then type | |
| 551 extra spaces to get where you want to be. | |
| 552 | |
| 553 ============================================================================== | |
| 554 5. Replace mode *Replace* *Replace-mode* *mode-replace* | |
| 555 | |
| 556 Enter Replace mode with the "R" command in normal mode. | |
| 557 | |
| 558 In Replace mode, one character in the line is deleted for every character you | |
| 559 type. If there is no character to delete (at the end of the line), the | |
| 560 typed character is appended (as in Insert mode). Thus the number of | |
| 561 characters in a line stays the same until you get to the end of the line. | |
| 562 If a <NL> is typed, a line break is inserted and no character is deleted. | |
| 563 | |
| 564 Be careful with <Tab> characters. If you type a normal printing character in | |
| 565 its place, the number of characters is still the same, but the number of | |
| 566 columns will become smaller. | |
| 567 | |
| 568 If you delete characters in Replace mode (with <BS>, CTRL-W, or CTRL-U), what | |
| 569 happens is that you delete the changes. The characters that were replaced | |
| 570 are restored. If you had typed past the existing text, the characters you | |
| 571 added are deleted. This is effectively a character-at-a-time undo. | |
| 572 | |
| 573 If the 'expandtab' option is on, a <Tab> will replace one character with | |
| 574 several spaces. The result of this is that the number of characters in the | |
| 575 line increases. Backspacing will delete one space at a time. The original | |
| 576 character will be put back for only one space that you backspace over (the | |
|
16553
0e473e9e70c2
patch 8.1.1280: remarks about functionality not in Vi clutters the help
Bram Moolenaar <Bram@vim.org>
parents:
16267
diff
changeset
|
577 last one). |
| 7 | 578 |
| 579 ============================================================================== | |
| 580 6. Virtual Replace mode *vreplace-mode* *Virtual-Replace-mode* | |
| 581 | |
| 582 Enter Virtual Replace mode with the "gR" command in normal mode. | |
|
2570
71b56b4e7785
Make the references to features in the help more consistent. (Sylvain Hitier)
Bram Moolenaar <bram@vim.org>
parents:
2561
diff
changeset
|
583 {not available when compiled without the |+vreplace| feature} |
| 7 | 584 |
| 585 Virtual Replace mode is similar to Replace mode, but instead of replacing | |
| 586 actual characters in the file, you are replacing screen real estate, so that | |
| 587 characters further on in the file never appear to move. | |
| 588 | |
| 589 So if you type a <Tab> it may replace several normal characters, and if you | |
| 590 type a letter on top of a <Tab> it may not replace anything at all, since the | |
| 591 <Tab> will still line up to the same place as before. | |
| 592 | |
| 593 Typing a <NL> still doesn't cause characters later in the file to appear to | |
| 594 move. The rest of the current line will be replaced by the <NL> (that is, | |
| 595 they are deleted), and replacing continues on the next line. A new line is | |
| 596 NOT inserted unless you go past the end of the file. | |
| 597 | |
| 598 Interesting effects are seen when using CTRL-T and CTRL-D. The characters | |
| 599 before the cursor are shifted sideways as normal, but characters later in the | |
| 600 line still remain still. CTRL-T will hide some of the old line under the | |
| 601 shifted characters, but CTRL-D will reveal them again. | |
| 602 | |
| 603 As with Replace mode, using <BS> etc will bring back the characters that were | |
| 604 replaced. This still works in conjunction with 'smartindent', CTRL-T and | |
| 605 CTRL-D, 'expandtab', 'smarttab', 'softtabstop', etc. | |
| 606 | |
| 607 In 'list' mode, Virtual Replace mode acts as if it was not in 'list' mode, | |
| 608 unless "L" is in 'cpoptions'. | |
| 609 | |
| 2581 | 610 Note that the only situations for which characters beyond the cursor should |
| 611 appear to move are in List mode |'list'|, and occasionally when 'wrap' is set | |
| 612 (and the line changes length to become shorter or wider than the width of the | |
| 613 screen). In other cases spaces may be inserted to avoid following characters | |
| 614 to move. | |
| 7 | 615 |
| 616 This mode is very useful for editing <Tab> separated columns in tables, for | |
| 617 entering new data while keeping all the columns aligned. | |
| 618 | |
| 619 ============================================================================== | |
| 620 7. Insert mode completion *ins-completion* | |
| 621 | |
| 449 | 622 In Insert and Replace mode, there are several commands to complete part of a |
| 7 | 623 keyword or line that has been typed. This is useful if you are using |
| 624 complicated keywords (e.g., function names with capitals and underscores). | |
| 625 | |
| 626 Completion can be done for: | |
| 627 | |
| 628 1. Whole lines |i_CTRL-X_CTRL-L| | |
| 629 2. keywords in the current file |i_CTRL-X_CTRL-N| | |
| 630 3. keywords in 'dictionary' |i_CTRL-X_CTRL-K| | |
| 631 4. keywords in 'thesaurus', thesaurus-style |i_CTRL-X_CTRL-T| | |
| 632 5. keywords in the current and included files |i_CTRL-X_CTRL-I| | |
| 633 6. tags |i_CTRL-X_CTRL-]| | |
| 634 7. file names |i_CTRL-X_CTRL-F| | |
| 635 8. definitions or macros |i_CTRL-X_CTRL-D| | |
| 636 9. Vim command-line |i_CTRL-X_CTRL-V| | |
| 449 | 637 10. User defined completion |i_CTRL-X_CTRL-U| |
| 523 | 638 11. omni completion |i_CTRL-X_CTRL-O| |
| 477 | 639 12. Spelling suggestions |i_CTRL-X_s| |
| 11473 | 640 13. keywords in 'complete' |i_CTRL-N| |i_CTRL-P| |
| 7 | 641 |
| 11473 | 642 All these, except CTRL-N and CTRL-P, are done in CTRL-X mode. This is a |
| 643 sub-mode of Insert and Replace modes. You enter CTRL-X mode by typing CTRL-X | |
| 644 and one of the CTRL-X commands. You exit CTRL-X mode by typing a key that is | |
| 645 not a valid CTRL-X mode command. Valid keys are the CTRL-X command itself, | |
| 646 CTRL-N (next), and CTRL-P (previous). | |
| 7 | 647 |
|
16127
0375e54f0adc
patch 8.1.1068: cannot get all the information about current completion
Bram Moolenaar <Bram@vim.org>
parents:
15729
diff
changeset
|
648 To get the current completion information, |complete_info()| can be used. |
| 7 | 649 Also see the 'infercase' option if you want to adjust the case of the match. |
| 650 | |
| 816 | 651 *complete_CTRL-E* |
| 652 When completion is active you can use CTRL-E to stop it and go back to the | |
| 843 | 653 originally typed text. The CTRL-E will not be inserted. |
| 816 | 654 |
| 655 *complete_CTRL-Y* | |
| 656 When the popup menu is displayed you can use CTRL-Y to stop completion and | |
| 657 accept the currently selected entry. The CTRL-Y is not inserted. Typing a | |
| 658 space, Enter, or some other unprintable character will leave completion mode | |
| 659 and insert that typed character. | |
| 660 | |
| 829 | 661 When the popup menu is displayed there are a few more special keys, see |
| 662 |popupmenu-keys|. | |
| 663 | |
| 7 | 664 Note: The keys that are valid in CTRL-X mode are not mapped. This allows for |
| 665 ":map ^F ^X^F" to work (where ^F is CTRL-F and ^X is CTRL-X). The key that | |
| 666 ends CTRL-X mode (any key that is not a valid CTRL-X mode command) is mapped. | |
| 667 Also, when doing completion with 'complete' mappings apply as usual. | |
| 668 | |
| 844 | 669 Note: While completion is active Insert mode can't be used recursively. |
| 670 Mappings that somehow invoke ":normal i.." will generate an E523 error. | |
| 671 | |
| 7 | 672 The following mappings are suggested to make typing the completion commands |
| 673 a bit easier (although they will hide other commands): > | |
| 674 :inoremap ^] ^X^] | |
| 675 :inoremap ^F ^X^F | |
| 676 :inoremap ^D ^X^D | |
| 677 :inoremap ^L ^X^L | |
| 678 | |
| 679 As a special case, typing CTRL-R to perform register insertion (see | |
| 680 |i_CTRL-R|) will not exit CTRL-X mode. This is primarily to allow the use of | |
| 681 the '=' register to call some function to determine the next operation. If | |
| 682 the contents of the register (or result of the '=' register evaluation) are | |
| 683 not valid CTRL-X mode keys, then CTRL-X mode will be exited as if those keys | |
| 684 had been typed. | |
| 685 | |
| 686 For example, the following will map <Tab> to either actually insert a <Tab> if | |
| 687 the current line is currently only whitespace, or start/continue a CTRL-N | |
| 688 completion operation: > | |
| 689 | |
| 690 function! CleverTab() | |
| 691 if strpart( getline('.'), 0, col('.')-1 ) =~ '^\s*$' | |
| 692 return "\<Tab>" | |
| 693 else | |
| 694 return "\<C-N>" | |
|
2120
f63ace015c63
Updated runtime and language files.
Bram Moolenaar <bram@zimbu.org>
parents:
2033
diff
changeset
|
695 endif |
| 7 | 696 endfunction |
| 697 inoremap <Tab> <C-R>=CleverTab()<CR> | |
| 698 | |
| 699 | |
| 700 | |
| 701 Completing whole lines *compl-whole-line* | |
| 702 | |
| 703 *i_CTRL-X_CTRL-L* | |
| 704 CTRL-X CTRL-L Search backwards for a line that starts with the | |
| 459 | 705 same characters as those in the current line before |
| 706 the cursor. Indent is ignored. The matching line is | |
| 7 | 707 inserted in front of the cursor. |
| 459 | 708 The 'complete' option is used to decide which buffers |
| 667 | 709 are searched for a match. Both loaded and unloaded |
| 710 buffers are used. | |
| 7 | 711 CTRL-L or |
| 712 CTRL-P Search backwards for next matching line. This line | |
| 713 replaces the previous matching line. | |
| 714 | |
| 715 CTRL-N Search forward for next matching line. This line | |
| 716 replaces the previous matching line. | |
| 717 | |
| 718 CTRL-X CTRL-L After expanding a line you can additionally get the | |
| 719 line next to it by typing CTRL-X CTRL-L again, unless | |
|
2033
de5a43c5eedc
Update documentation files.
Bram Moolenaar <bram@zimbu.org>
parents:
1702
diff
changeset
|
720 a double CTRL-X is used. Only works for loaded |
|
de5a43c5eedc
Update documentation files.
Bram Moolenaar <bram@zimbu.org>
parents:
1702
diff
changeset
|
721 buffers. |
| 7 | 722 |
| 723 Completing keywords in current file *compl-current* | |
| 724 | |
| 725 *i_CTRL-X_CTRL-P* | |
| 726 *i_CTRL-X_CTRL-N* | |
| 727 CTRL-X CTRL-N Search forwards for words that start with the keyword | |
| 728 in front of the cursor. The found keyword is inserted | |
| 729 in front of the cursor. | |
| 730 | |
| 731 CTRL-X CTRL-P Search backwards for words that start with the keyword | |
| 732 in front of the cursor. The found keyword is inserted | |
| 733 in front of the cursor. | |
| 734 | |
| 735 CTRL-N Search forward for next matching keyword. This | |
| 736 keyword replaces the previous matching keyword. | |
| 737 | |
| 738 CTRL-P Search backwards for next matching keyword. This | |
| 739 keyword replaces the previous matching keyword. | |
| 740 | |
| 741 CTRL-X CTRL-N or | |
| 742 CTRL-X CTRL-P Further use of CTRL-X CTRL-N or CTRL-X CTRL-P will | |
| 743 copy the words following the previous expansion in | |
| 744 other contexts unless a double CTRL-X is used. | |
| 745 | |
| 746 If there is a keyword in front of the cursor (a name made out of alphabetic | |
| 747 characters and characters in 'iskeyword'), it is used as the search pattern, | |
| 748 with "\<" prepended (meaning: start of a word). Otherwise "\<\k\k" is used | |
| 749 as search pattern (start of any keyword of at least two characters). | |
| 750 | |
| 751 In Replace mode, the number of characters that are replaced depends on the | |
| 752 length of the matched string. This works like typing the characters of the | |
| 753 matched string in Replace mode. | |
| 754 | |
| 755 If there is not a valid keyword character before the cursor, any keyword of | |
| 756 at least two characters is matched. | |
| 757 e.g., to get: | |
| 758 printf("(%g, %g, %g)", vector[0], vector[1], vector[2]); | |
| 759 just type: | |
| 760 printf("(%g, %g, %g)", vector[0], ^P[1], ^P[2]); | |
| 761 | |
| 523 | 762 The search wraps around the end of the file, the value of 'wrapscan' is not |
| 763 used here. | |
| 764 | |
| 7 | 765 Multiple repeats of the same completion are skipped; thus a different match |
| 766 will be inserted at each CTRL-N and CTRL-P (unless there is only one | |
| 767 matching keyword). | |
| 768 | |
| 769 Single character matches are never included, as they usually just get in | |
| 770 the way of what you were really after. | |
| 771 e.g., to get: | |
| 772 printf("name = %s\n", name); | |
| 773 just type: | |
| 774 printf("name = %s\n", n^P); | |
| 775 or even: | |
| 776 printf("name = %s\n", ^P); | |
| 777 The 'n' in '\n' is skipped. | |
| 778 | |
| 779 After expanding a word, you can use CTRL-X CTRL-P or CTRL-X CTRL-N to get the | |
| 780 word following the expansion in other contexts. These sequences search for | |
| 781 the text just expanded and further expand by getting an extra word. This is | |
| 782 useful if you need to repeat a sequence of complicated words. Although CTRL-P | |
| 783 and CTRL-N look just for strings of at least two characters, CTRL-X CTRL-P and | |
| 784 CTRL-X CTRL-N can be used to expand words of just one character. | |
| 785 e.g., to get: | |
| 786 México | |
| 787 you can type: | |
| 788 M^N^P^X^P^X^P | |
| 789 CTRL-N starts the expansion and then CTRL-P takes back the single character | |
| 790 "M", the next two CTRL-X CTRL-P's get the words "é" and ";xico". | |
| 791 | |
| 792 If the previous expansion was split, because it got longer than 'textwidth', | |
| 793 then just the text in the current line will be used. | |
| 794 | |
| 795 If the match found is at the end of a line, then the first word in the next | |
| 796 line will be inserted and the message "word from next line" displayed, if | |
| 797 this word is accepted the next CTRL-X CTRL-P or CTRL-X CTRL-N will search | |
| 798 for those lines starting with this word. | |
| 799 | |
| 800 | |
| 801 Completing keywords in 'dictionary' *compl-dictionary* | |
| 802 | |
| 803 *i_CTRL-X_CTRL-K* | |
| 804 CTRL-X CTRL-K Search the files given with the 'dictionary' option | |
| 805 for words that start with the keyword in front of the | |
| 806 cursor. This is like CTRL-N, but only the dictionary | |
| 807 files are searched, not the current file. The found | |
| 808 keyword is inserted in front of the cursor. This | |
| 809 could potentially be pretty slow, since all matches | |
| 810 are found before the first match is used. By default, | |
| 811 the 'dictionary' option is empty. | |
| 812 For suggestions where to find a list of words, see the | |
| 813 'dictionary' option. | |
| 814 | |
| 815 CTRL-K or | |
| 816 CTRL-N Search forward for next matching keyword. This | |
| 817 keyword replaces the previous matching keyword. | |
| 818 | |
| 819 CTRL-P Search backwards for next matching keyword. This | |
| 820 keyword replaces the previous matching keyword. | |
| 821 | |
| 822 *i_CTRL-X_CTRL-T* | |
| 236 | 823 CTRL-X CTRL-T Works as CTRL-X CTRL-K, but in a special way. It uses |
| 7 | 824 the 'thesaurus' option instead of 'dictionary'. If a |
| 825 match is found in the thesaurus file, all the | |
| 826 remaining words on the same line are included as | |
| 827 matches, even though they don't complete the word. | |
| 828 Thus a word can be completely replaced. | |
| 829 | |
| 830 For an example, imagine the 'thesaurus' file has a | |
| 831 line like this: > | |
| 832 angry furious mad enraged | |
| 833 < Placing the cursor after the letters "ang" and typing | |
| 834 CTRL-X CTRL-T would complete the word "angry"; | |
| 835 subsequent presses would change the word to "furious", | |
| 836 "mad" etc. | |
| 837 Other uses include translation between two languages, | |
| 838 or grouping API functions by keyword. | |
| 839 | |
| 840 CTRL-T or | |
| 841 CTRL-N Search forward for next matching keyword. This | |
| 842 keyword replaces the previous matching keyword. | |
| 843 | |
| 844 CTRL-P Search backwards for next matching keyword. This | |
| 845 keyword replaces the previous matching keyword. | |
| 846 | |
| 847 | |
| 848 Completing keywords in the current and included files *compl-keyword* | |
| 849 | |
| 850 The 'include' option is used to specify a line that contains an include file | |
| 851 name. The 'path' option is used to search for include files. | |
| 852 | |
| 853 *i_CTRL-X_CTRL-I* | |
| 854 CTRL-X CTRL-I Search for the first keyword in the current and | |
| 855 included files that starts with the same characters | |
| 856 as those before the cursor. The matched keyword is | |
| 857 inserted in front of the cursor. | |
| 858 | |
| 859 CTRL-N Search forwards for next matching keyword. This | |
| 860 keyword replaces the previous matching keyword. | |
| 861 Note: CTRL-I is the same as <Tab>, which is likely to | |
| 862 be typed after a successful completion, therefore | |
| 863 CTRL-I is not used for searching for the next match. | |
| 864 | |
| 865 CTRL-P Search backward for previous matching keyword. This | |
| 866 keyword replaces the previous matching keyword. | |
| 867 | |
| 868 CTRL-X CTRL-I Further use of CTRL-X CTRL-I will copy the words | |
| 869 following the previous expansion in other contexts | |
| 870 unless a double CTRL-X is used. | |
| 871 | |
| 872 Completing tags *compl-tag* | |
| 873 *i_CTRL-X_CTRL-]* | |
| 874 CTRL-X CTRL-] Search for the first tag that starts with the same | |
| 875 characters as before the cursor. The matching tag is | |
| 876 inserted in front of the cursor. Alphabetic | |
| 877 characters and characters in 'iskeyword' are used | |
| 878 to decide which characters are included in the tag | |
| 879 name (same as for a keyword). See also |CTRL-]|. | |
| 880 The 'showfulltag' option can be used to add context | |
| 881 from around the tag definition. | |
| 882 CTRL-] or | |
| 883 CTRL-N Search forwards for next matching tag. This tag | |
| 884 replaces the previous matching tag. | |
| 885 | |
| 886 CTRL-P Search backward for previous matching tag. This tag | |
| 887 replaces the previous matching tag. | |
| 888 | |
| 889 | |
| 890 Completing file names *compl-filename* | |
| 891 *i_CTRL-X_CTRL-F* | |
| 892 CTRL-X CTRL-F Search for the first file name that starts with the | |
| 893 same characters as before the cursor. The matching | |
| 894 file name is inserted in front of the cursor. | |
| 895 Alphabetic characters and characters in 'isfname' | |
| 896 are used to decide which characters are included in | |
| 897 the file name. Note: the 'path' option is not used | |
| 898 here (yet). | |
| 899 CTRL-F or | |
| 900 CTRL-N Search forwards for next matching file name. This | |
| 901 file name replaces the previous matching file name. | |
| 902 | |
| 903 CTRL-P Search backward for previous matching file name. | |
| 904 This file name replaces the previous matching file | |
| 905 name. | |
| 906 | |
| 907 | |
| 908 Completing definitions or macros *compl-define* | |
| 909 | |
| 910 The 'define' option is used to specify a line that contains a definition. | |
| 911 The 'include' option is used to specify a line that contains an include file | |
| 912 name. The 'path' option is used to search for include files. | |
| 913 | |
| 914 *i_CTRL-X_CTRL-D* | |
| 915 CTRL-X CTRL-D Search in the current and included files for the | |
| 916 first definition (or macro) name that starts with | |
| 917 the same characters as before the cursor. The found | |
| 918 definition name is inserted in front of the cursor. | |
| 919 CTRL-D or | |
| 920 CTRL-N Search forwards for next matching macro name. This | |
| 921 macro name replaces the previous matching macro | |
| 922 name. | |
| 923 | |
| 924 CTRL-P Search backward for previous matching macro name. | |
| 925 This macro name replaces the previous matching macro | |
| 926 name. | |
| 927 | |
| 928 CTRL-X CTRL-D Further use of CTRL-X CTRL-D will copy the words | |
| 929 following the previous expansion in other contexts | |
| 930 unless a double CTRL-X is used. | |
| 931 | |
| 932 | |
| 933 Completing Vim commands *compl-vim* | |
| 934 | |
| 935 Completion is context-sensitive. It works like on the Command-line. It | |
| 449 | 936 completes an Ex command as well as its arguments. This is useful when writing |
| 937 a Vim script. | |
| 7 | 938 |
| 939 *i_CTRL-X_CTRL-V* | |
| 940 CTRL-X CTRL-V Guess what kind of item is in front of the cursor and | |
| 941 find the first match for it. | |
| 942 Note: When CTRL-V is mapped you can often use CTRL-Q | |
| 1620 | 943 instead of |i_CTRL-Q|. |
| 7 | 944 CTRL-V or |
| 945 CTRL-N Search forwards for next match. This match replaces | |
| 946 the previous one. | |
| 947 | |
| 1620 | 948 CTRL-P Search backwards for previous match. This match |
| 7 | 949 replaces the previous one. |
| 950 | |
| 951 CTRL-X CTRL-V Further use of CTRL-X CTRL-V will do the same as | |
| 952 CTRL-V. This allows mapping a key to do Vim command | |
| 953 completion, for example: > | |
| 954 :imap <Tab> <C-X><C-V> | |
| 955 | |
| 449 | 956 User defined completion *compl-function* |
| 12 | 957 |
| 958 Completion is done by a function that can be defined by the user with the | |
| 648 | 959 'completefunc' option. See below for how the function is called and an |
| 960 example |complete-functions|. | |
| 12 | 961 |
| 962 *i_CTRL-X_CTRL-U* | |
| 963 CTRL-X CTRL-U Guess what kind of item is in front of the cursor and | |
| 964 find the first match for it. | |
| 965 CTRL-U or | |
| 966 CTRL-N Use the next match. This match replaces the previous | |
| 967 one. | |
| 968 | |
| 969 CTRL-P Use the previous match. This match replaces the | |
| 970 previous one. | |
| 971 | |
| 972 | |
| 523 | 973 Omni completion *compl-omni* |
| 449 | 974 |
| 502 | 975 Completion is done by a function that can be defined by the user with the |
| 523 | 976 'omnifunc' option. This is to be used for filetype-specific completion. |
| 502 | 977 |
| 648 | 978 See below for how the function is called and an example |complete-functions|. |
| 523 | 979 For remarks about specific filetypes see |compl-omni-filetypes|. |
| 859 | 980 More completion scripts will appear, check www.vim.org. Currently there is a |
| 981 first version for C++. | |
| 449 | 982 |
| 983 *i_CTRL-X_CTRL-O* | |
| 984 CTRL-X CTRL-O Guess what kind of item is in front of the cursor and | |
| 985 find the first match for it. | |
| 986 CTRL-O or | |
| 987 CTRL-N Use the next match. This match replaces the previous | |
| 988 one. | |
| 989 | |
| 990 CTRL-P Use the previous match. This match replaces the | |
| 991 previous one. | |
| 992 | |
| 993 | |
| 477 | 994 Spelling suggestions *compl-spelling* |
| 995 | |
| 483 | 996 A word before or at the cursor is located and correctly spelled words are |
| 997 suggested to replace it. If there is a badly spelled word in the line, before | |
| 998 or under the cursor, the cursor is moved to after it. Otherwise the word just | |
| 999 before the cursor is used for suggestions, even though it isn't badly spelled. | |
| 1000 | |
| 477 | 1001 NOTE: CTRL-S suspends display in many Unix terminals. Use 's' instead. Type |
| 1002 CTRL-Q to resume displaying. | |
| 1003 | |
| 1004 *i_CTRL-X_CTRL-S* *i_CTRL-X_s* | |
| 1005 CTRL-X CTRL-S or | |
| 1006 CTRL-X s Locate the word in front of the cursor and find the | |
| 1007 first spell suggestion for it. | |
| 1008 CTRL-S or | |
| 1009 CTRL-N Use the next suggestion. This replaces the previous | |
| 1010 one. Note that you can't use 's' here. | |
| 1011 | |
| 1012 CTRL-P Use the previous suggestion. This replaces the | |
| 1013 previous one. | |
| 1014 | |
| 1015 | |
| 7 | 1016 Completing keywords from different sources *compl-generic* |
| 1017 | |
| 1018 *i_CTRL-N* | |
| 1019 CTRL-N Find next match for words that start with the | |
| 1020 keyword in front of the cursor, looking in places | |
| 1021 specified with the 'complete' option. The found | |
| 1022 keyword is inserted in front of the cursor. | |
| 1023 | |
| 1024 *i_CTRL-P* | |
| 1025 CTRL-P Find previous match for words that start with the | |
| 1026 keyword in front of the cursor, looking in places | |
| 1027 specified with the 'complete' option. The found | |
| 1028 keyword is inserted in front of the cursor. | |
| 1029 | |
| 1030 CTRL-N Search forward for next matching keyword. This | |
| 1031 keyword replaces the previous matching keyword. | |
| 1032 | |
| 1033 CTRL-P Search backwards for next matching keyword. This | |
| 1034 keyword replaces the previous matching keyword. | |
| 1035 | |
| 1036 CTRL-X CTRL-N or | |
| 1037 CTRL-X CTRL-P Further use of CTRL-X CTRL-N or CTRL-X CTRL-P will | |
| 1038 copy the words following the previous expansion in | |
| 1039 other contexts unless a double CTRL-X is used. | |
| 1040 | |
| 519 | 1041 |
| 648 | 1042 FUNCTIONS FOR FINDING COMPLETIONS *complete-functions* |
| 1043 | |
| 1044 This applies to 'completefunc' and 'omnifunc'. | |
| 1045 | |
| 659 | 1046 The function is called in two different ways: |
| 1047 - First the function is called to find the start of the text to be completed. | |
| 1048 - Later the function is called to actually find the matches. | |
| 648 | 1049 |
| 1050 On the first invocation the arguments are: | |
| 1051 a:findstart 1 | |
| 1052 a:base empty | |
| 1053 | |
| 659 | 1054 The function must return the column where the completion starts. It must be a |
| 1055 number between zero and the cursor column "col('.')". This involves looking | |
| 1056 at the characters just before the cursor and including those characters that | |
| 1057 could be part of the completed item. The text between this column and the | |
| 14637 | 1058 cursor column will be replaced with the matches. If the returned value is |
| 1059 larger than the cursor column, the cursor column is used. | |
|
3526
dd6c2497c997
Fix more 'cpo' issues in runtime files.
Bram Moolenaar <bram@vim.org>
parents:
3492
diff
changeset
|
1060 |
| 14637 | 1061 Negative return values: |
| 1062 -2 To cancel silently and stay in completion mode. | |
| 1063 -3 To cancel silently and leave completion mode. | |
| 1064 Another negative value: completion starts at the cursor column | |
| 648 | 1065 |
| 1066 On the second invocation the arguments are: | |
| 1067 a:findstart 0 | |
| 659 | 1068 a:base the text with which matches should match; the text that was |
| 648 | 1069 located in the first call (can be empty) |
| 1070 | |
| 1071 The function must return a List with the matching words. These matches | |
| 1072 usually include the "a:base" text. When there are no matches return an empty | |
| 659 | 1073 List. |
| 3082 | 1074 |
| 1075 In order to return more information than the matching words, return a Dict | |
| 1076 that contains the List. The Dict can have these items: | |
| 1077 words The List of matching words (mandatory). | |
| 1078 refresh A string to control re-invocation of the function | |
| 1079 (optional). | |
| 1080 The only value currently recognized is "always", the | |
| 1081 effect is that the function is called whenever the | |
| 1082 leading text is changed. | |
|
15416
5f8ddd2a7b92
patch 8.1.0716: get warning message when 'completefunc' returns nothing
Bram Moolenaar <Bram@vim.org>
parents:
14637
diff
changeset
|
1083 |
|
5f8ddd2a7b92
patch 8.1.0716: get warning message when 'completefunc' returns nothing
Bram Moolenaar <Bram@vim.org>
parents:
14637
diff
changeset
|
1084 If you want to suppress the warning message for an empty result, return |
| 15729 | 1085 |v:none|. This is useful to implement asynchronous completion with |
| 1086 |complete()|. | |
|
15416
5f8ddd2a7b92
patch 8.1.0716: get warning message when 'completefunc' returns nothing
Bram Moolenaar <Bram@vim.org>
parents:
14637
diff
changeset
|
1087 |
| 3082 | 1088 Other items are ignored. |
| 1089 | |
| 19303 | 1090 For acting upon end of completion, see the |CompleteDonePre| and |
| 1091 |CompleteDone| autocommand event. | |
| 3682 | 1092 |
| 3082 | 1093 For example, the function can contain this: > |
| 1094 let matches = ... list of words ... | |
| 1095 return {'words': matches, 'refresh': 'always'} | |
| 1096 < | |
| 723 | 1097 *complete-items* |
| 659 | 1098 Each list item can either be a string or a Dictionary. When it is a string it |
| 1099 is used as the completion. When it is a Dictionary it can contain these | |
| 1100 items: | |
| 819 | 1101 word the text that will be inserted, mandatory |
| 1102 abbr abbreviation of "word"; when not empty it is used in | |
| 1103 the menu instead of "word" | |
| 820 | 1104 menu extra text for the popup menu, displayed after "word" |
| 1105 or "abbr" | |
| 819 | 1106 info more information about the item, can be displayed in a |
|
17771
4bd21046902b
patch 8.1.1882: cannot specify properties of the info popup window
Bram Moolenaar <Bram@vim.org>
parents:
16610
diff
changeset
|
1107 preview or popup window |
| 659 | 1108 kind single letter indicating the type of completion |
| 867 | 1109 icase when non-zero case is to be ignored when comparing |
| 1110 items to be equal; when omitted zero is used, thus | |
| 1111 items that only differ in case are added | |
|
16237
56451a2677dc
patch 8.1.1123: no way to avoid filtering for autocomplete function
Bram Moolenaar <Bram@vim.org>
parents:
16208
diff
changeset
|
1112 equal when non-zero, always treat this item to be equal when |
|
56451a2677dc
patch 8.1.1123: no way to avoid filtering for autocomplete function
Bram Moolenaar <Bram@vim.org>
parents:
16208
diff
changeset
|
1113 comparing. Which means, "equal=1" disables filtering |
|
56451a2677dc
patch 8.1.1123: no way to avoid filtering for autocomplete function
Bram Moolenaar <Bram@vim.org>
parents:
16208
diff
changeset
|
1114 of this item. |
| 841 | 1115 dup when non-zero this match will be added even when an |
| 1116 item with the same word is already present. | |
| 2642 | 1117 empty when non-zero this match will be added even when it is |
| 1118 an empty string | |
|
13238
e0dcfd3dbb52
patch 8.0.1493: completion items cannot be annotated
Christian Brabandt <cb@256bit.org>
parents:
13125
diff
changeset
|
1119 user_data custom data which is associated with the item and |
|
19047
a3fce2763e83
patch 8.2.0084: complete item "user_data" can only be a string
Bram Moolenaar <Bram@vim.org>
parents:
18972
diff
changeset
|
1120 available in |v:completed_item|; it can be any type; |
|
a3fce2763e83
patch 8.2.0084: complete item "user_data" can only be a string
Bram Moolenaar <Bram@vim.org>
parents:
18972
diff
changeset
|
1121 defaults to an empty string |
| 659 | 1122 |
|
16237
56451a2677dc
patch 8.1.1123: no way to avoid filtering for autocomplete function
Bram Moolenaar <Bram@vim.org>
parents:
16208
diff
changeset
|
1123 All of these except "icase", "equal", "dup" and "empty" must be a string. If |
|
56451a2677dc
patch 8.1.1123: no way to avoid filtering for autocomplete function
Bram Moolenaar <Bram@vim.org>
parents:
16208
diff
changeset
|
1124 an item does not meet these requirements then an error message is given and |
|
56451a2677dc
patch 8.1.1123: no way to avoid filtering for autocomplete function
Bram Moolenaar <Bram@vim.org>
parents:
16208
diff
changeset
|
1125 further items in the list are not used. You can mix string and Dictionary |
|
56451a2677dc
patch 8.1.1123: no way to avoid filtering for autocomplete function
Bram Moolenaar <Bram@vim.org>
parents:
16208
diff
changeset
|
1126 items in the returned list. |
| 659 | 1127 |
| 1128 The "menu" item is used in the popup menu and may be truncated, thus it should | |
| 728 | 1129 be relatively short. The "info" item can be longer, it will be displayed in |
|
17771
4bd21046902b
patch 8.1.1882: cannot specify properties of the info popup window
Bram Moolenaar <Bram@vim.org>
parents:
16610
diff
changeset
|
1130 the preview window when "preview" appears in 'completeopt' or in a popup |
|
4bd21046902b
patch 8.1.1882: cannot specify properties of the info popup window
Bram Moolenaar <Bram@vim.org>
parents:
16610
diff
changeset
|
1131 window when "popup" appears in 'completeopt'. In the preview window the |
|
4bd21046902b
patch 8.1.1882: cannot specify properties of the info popup window
Bram Moolenaar <Bram@vim.org>
parents:
16610
diff
changeset
|
1132 "info" item will also remain displayed after the popup menu has been removed. |
|
4bd21046902b
patch 8.1.1882: cannot specify properties of the info popup window
Bram Moolenaar <Bram@vim.org>
parents:
16610
diff
changeset
|
1133 This is useful for function arguments. Use a single space for "info" to |
|
4bd21046902b
patch 8.1.1882: cannot specify properties of the info popup window
Bram Moolenaar <Bram@vim.org>
parents:
16610
diff
changeset
|
1134 remove existing text in the preview window. The size of the preview window is |
|
4bd21046902b
patch 8.1.1882: cannot specify properties of the info popup window
Bram Moolenaar <Bram@vim.org>
parents:
16610
diff
changeset
|
1135 three lines, but 'previewheight' is used when it has a value of 1 or 2. |
|
4bd21046902b
patch 8.1.1882: cannot specify properties of the info popup window
Bram Moolenaar <Bram@vim.org>
parents:
16610
diff
changeset
|
1136 |
|
4bd21046902b
patch 8.1.1882: cannot specify properties of the info popup window
Bram Moolenaar <Bram@vim.org>
parents:
16610
diff
changeset
|
1137 *complete-popup* |
|
4bd21046902b
patch 8.1.1882: cannot specify properties of the info popup window
Bram Moolenaar <Bram@vim.org>
parents:
16610
diff
changeset
|
1138 When "popup" is in 'completeopt' a popup window is used to display the "info". |
| 17909 | 1139 Then the 'completepopup' option specifies the properties of the popup. This |
| 1140 is used when the info popup is created. The option is a comma separated list | |
| 1141 of values: | |
|
17771
4bd21046902b
patch 8.1.1882: cannot specify properties of the info popup window
Bram Moolenaar <Bram@vim.org>
parents:
16610
diff
changeset
|
1142 height maximum height of the popup |
|
4bd21046902b
patch 8.1.1882: cannot specify properties of the info popup window
Bram Moolenaar <Bram@vim.org>
parents:
16610
diff
changeset
|
1143 width maximum width of the popup |
| 18053 | 1144 highlight highlight group of the popup (default is PmenuSel) |
|
17815
9ec2526c04c5
patch 8.1.1904: cannot have an info popup align with the popup menu
Bram Moolenaar <Bram@vim.org>
parents:
17809
diff
changeset
|
1145 align "item" (default) or "menu" |
|
9ec2526c04c5
patch 8.1.1904: cannot have an info popup align with the popup menu
Bram Moolenaar <Bram@vim.org>
parents:
17809
diff
changeset
|
1146 border "on" (default) or "off" |
|
17771
4bd21046902b
patch 8.1.1882: cannot specify properties of the info popup window
Bram Moolenaar <Bram@vim.org>
parents:
16610
diff
changeset
|
1147 Example: > |
|
4bd21046902b
patch 8.1.1882: cannot specify properties of the info popup window
Bram Moolenaar <Bram@vim.org>
parents:
16610
diff
changeset
|
1148 :set completepopup=height:10,width:60,highlight:InfoPopup |
| 659 | 1149 |
| 17909 | 1150 When the "align" value is "item" then the popup is positioned close to the |
|
17815
9ec2526c04c5
patch 8.1.1904: cannot have an info popup align with the popup menu
Bram Moolenaar <Bram@vim.org>
parents:
17809
diff
changeset
|
1151 selected item. Changing the selection will also move the popup. When "align" |
|
9ec2526c04c5
patch 8.1.1904: cannot have an info popup align with the popup menu
Bram Moolenaar <Bram@vim.org>
parents:
17809
diff
changeset
|
1152 is "menu" then the popup is aligned with the top of the menu if the menu is |
|
9ec2526c04c5
patch 8.1.1904: cannot have an info popup align with the popup menu
Bram Moolenaar <Bram@vim.org>
parents:
17809
diff
changeset
|
1153 below the text, and the bottom of the menu otherwise. |
|
9ec2526c04c5
patch 8.1.1904: cannot have an info popup align with the popup menu
Bram Moolenaar <Bram@vim.org>
parents:
17809
diff
changeset
|
1154 |
| 17909 | 1155 After the info popup is created it can be found with |popup_findinfo()| and |
| 1156 properties can be changed with |popup_setoptions()|. | |
| 1157 | |
|
18396
ba5d8c5d77d7
patch 8.1.2192: cannot easily fill the info popup asynchronously
Bram Moolenaar <Bram@vim.org>
parents:
18186
diff
changeset
|
1158 *complete-popuphidden* |
|
ba5d8c5d77d7
patch 8.1.2192: cannot easily fill the info popup asynchronously
Bram Moolenaar <Bram@vim.org>
parents:
18186
diff
changeset
|
1159 If the information for the popup is obtained asynchronously, use "popuphidden" |
| 18750 | 1160 in 'completeopt'. The info popup will then be initially hidden and |
|
18396
ba5d8c5d77d7
patch 8.1.2192: cannot easily fill the info popup asynchronously
Bram Moolenaar <Bram@vim.org>
parents:
18186
diff
changeset
|
1161 |popup_show()| must be called once it has been filled with the info. This can |
|
ba5d8c5d77d7
patch 8.1.2192: cannot easily fill the info popup asynchronously
Bram Moolenaar <Bram@vim.org>
parents:
18186
diff
changeset
|
1162 be done with a |CompleteChanged| autocommand, something like this: > |
|
ba5d8c5d77d7
patch 8.1.2192: cannot easily fill the info popup asynchronously
Bram Moolenaar <Bram@vim.org>
parents:
18186
diff
changeset
|
1163 set completeopt+=popuphidden |
|
ba5d8c5d77d7
patch 8.1.2192: cannot easily fill the info popup asynchronously
Bram Moolenaar <Bram@vim.org>
parents:
18186
diff
changeset
|
1164 au CompleteChanged * call UpdateCompleteInfo() |
|
ba5d8c5d77d7
patch 8.1.2192: cannot easily fill the info popup asynchronously
Bram Moolenaar <Bram@vim.org>
parents:
18186
diff
changeset
|
1165 func UpdateCompleteInfo() |
|
ba5d8c5d77d7
patch 8.1.2192: cannot easily fill the info popup asynchronously
Bram Moolenaar <Bram@vim.org>
parents:
18186
diff
changeset
|
1166 " Cancel any pending info fetch |
|
ba5d8c5d77d7
patch 8.1.2192: cannot easily fill the info popup asynchronously
Bram Moolenaar <Bram@vim.org>
parents:
18186
diff
changeset
|
1167 let item = v:event.completed_item |
|
ba5d8c5d77d7
patch 8.1.2192: cannot easily fill the info popup asynchronously
Bram Moolenaar <Bram@vim.org>
parents:
18186
diff
changeset
|
1168 " Start fetching info for the item then call ShowCompleteInfo(info) |
|
ba5d8c5d77d7
patch 8.1.2192: cannot easily fill the info popup asynchronously
Bram Moolenaar <Bram@vim.org>
parents:
18186
diff
changeset
|
1169 endfunc |
|
ba5d8c5d77d7
patch 8.1.2192: cannot easily fill the info popup asynchronously
Bram Moolenaar <Bram@vim.org>
parents:
18186
diff
changeset
|
1170 func ShowCompleteInfo(info) |
|
ba5d8c5d77d7
patch 8.1.2192: cannot easily fill the info popup asynchronously
Bram Moolenaar <Bram@vim.org>
parents:
18186
diff
changeset
|
1171 let id = popup_findinfo() |
|
ba5d8c5d77d7
patch 8.1.2192: cannot easily fill the info popup asynchronously
Bram Moolenaar <Bram@vim.org>
parents:
18186
diff
changeset
|
1172 if id |
|
ba5d8c5d77d7
patch 8.1.2192: cannot easily fill the info popup asynchronously
Bram Moolenaar <Bram@vim.org>
parents:
18186
diff
changeset
|
1173 call popup_settext(id, 'async info: ' .. a:info) |
|
ba5d8c5d77d7
patch 8.1.2192: cannot easily fill the info popup asynchronously
Bram Moolenaar <Bram@vim.org>
parents:
18186
diff
changeset
|
1174 call popup_show(id) |
|
ba5d8c5d77d7
patch 8.1.2192: cannot easily fill the info popup asynchronously
Bram Moolenaar <Bram@vim.org>
parents:
18186
diff
changeset
|
1175 endif |
|
ba5d8c5d77d7
patch 8.1.2192: cannot easily fill the info popup asynchronously
Bram Moolenaar <Bram@vim.org>
parents:
18186
diff
changeset
|
1176 endfunc |
|
ba5d8c5d77d7
patch 8.1.2192: cannot easily fill the info popup asynchronously
Bram Moolenaar <Bram@vim.org>
parents:
18186
diff
changeset
|
1177 |
|
ba5d8c5d77d7
patch 8.1.2192: cannot easily fill the info popup asynchronously
Bram Moolenaar <Bram@vim.org>
parents:
18186
diff
changeset
|
1178 < *complete-item-kind* |
| 659 | 1179 The "kind" item uses a single letter to indicate the kind of completion. This |
| 1180 may be used to show the completion differently (different color or icon). | |
| 1181 Currently these types can be used: | |
| 1182 v variable | |
| 1183 f function or method | |
| 728 | 1184 m member of a struct or class |
| 1185 t typedef | |
| 1186 d #define or macro | |
| 648 | 1187 |
| 1188 When searching for matches takes some time call |complete_add()| to add each | |
| 1189 match to the total list. These matches should then not appear in the returned | |
| 1190 list! Call |complete_check()| now and then to allow the user to press a key | |
| 1191 while still searching for matches. Stop searching when it returns non-zero. | |
| 1192 | |
| 2642 | 1193 *E839* *E840* |
| 1194 The function is allowed to move the cursor, it is restored afterwards. | |
| 1195 The function is not allowed to move to another window or delete text. | |
| 648 | 1196 |
| 1197 An example that completes the names of the months: > | |
| 1198 fun! CompleteMonths(findstart, base) | |
| 1199 if a:findstart | |
| 1200 " locate the start of the word | |
| 1201 let line = getline('.') | |
| 1202 let start = col('.') - 1 | |
| 1203 while start > 0 && line[start - 1] =~ '\a' | |
| 1204 let start -= 1 | |
| 1205 endwhile | |
| 1206 return start | |
| 1207 else | |
| 1208 " find months matching with "a:base" | |
| 1209 let res = [] | |
| 1210 for m in split("Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec") | |
| 1211 if m =~ '^' . a:base | |
| 1212 call add(res, m) | |
| 1213 endif | |
| 1214 endfor | |
| 1215 return res | |
| 1216 endif | |
| 1217 endfun | |
| 1218 set completefunc=CompleteMonths | |
| 1219 < | |
| 1220 The same, but now pretending searching for matches is slow: > | |
| 1221 fun! CompleteMonths(findstart, base) | |
| 1222 if a:findstart | |
| 1223 " locate the start of the word | |
| 1224 let line = getline('.') | |
| 1225 let start = col('.') - 1 | |
| 1226 while start > 0 && line[start - 1] =~ '\a' | |
| 1227 let start -= 1 | |
| 1228 endwhile | |
| 1229 return start | |
| 1230 else | |
| 1231 " find months matching with "a:base" | |
| 1232 for m in split("Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec") | |
| 1233 if m =~ '^' . a:base | |
| 1234 call complete_add(m) | |
| 1235 endif | |
| 1236 sleep 300m " simulate searching for next match | |
| 1237 if complete_check() | |
| 1238 break | |
| 1239 endif | |
| 1240 endfor | |
| 1241 return [] | |
| 1242 endif | |
| 1243 endfun | |
| 1244 set completefunc=CompleteMonths | |
| 1245 < | |
| 1246 | |
| 540 | 1247 INSERT COMPLETION POPUP MENU *ins-completion-menu* |
| 620 | 1248 *popupmenu-completion* |
| 540 | 1249 Vim can display the matches in a simplistic popup menu. |
| 1250 | |
| 1251 The menu is used when: | |
| 715 | 1252 - The 'completeopt' option contains "menu" or "menuone". |
| 540 | 1253 - The terminal supports at least 8 colors. |
| 857 | 1254 - There are at least two matches. One if "menuone" is used. |
| 540 | 1255 |
| 765 | 1256 The 'pumheight' option can be used to set a maximum height. The default is to |
| 1257 use all space available. | |
|
13238
e0dcfd3dbb52
patch 8.0.1493: completion items cannot be annotated
Christian Brabandt <cb@256bit.org>
parents:
13125
diff
changeset
|
1258 The 'pumwidth' option can be used to set a minimum width. The default is 15 |
|
e0dcfd3dbb52
patch 8.0.1493: completion items cannot be annotated
Christian Brabandt <cb@256bit.org>
parents:
13125
diff
changeset
|
1259 characters. |
| 765 | 1260 |
| 825 | 1261 There are three states: |
| 1262 1. A complete match has been inserted, e.g., after using CTRL-N or CTRL-P. | |
| 1263 2. A cursor key has been used to select another match. The match was not | |
| 1264 inserted then, only the entry in the popup menu is highlighted. | |
| 1265 3. Only part of a match has been inserted and characters were typed or the | |
| 1266 backspace key was used. The list of matches was then adjusted for what is | |
| 1267 in front of the cursor. | |
| 667 | 1268 |
| 682 | 1269 You normally start in the first state, with the first match being inserted. |
| 667 | 1270 When "longest" is in 'completeopt' and there is more than one match you start |
| 825 | 1271 in the third state. |
| 665 | 1272 |
| 825 | 1273 If you select another match, e.g., with CTRL-N or CTRL-P, you go to the first |
| 1274 state. This doesn't change the list of matches. | |
| 682 | 1275 |
| 825 | 1276 When you are back at the original text then you are in the third state. To |
| 715 | 1277 get there right away you can use a mapping that uses CTRL-P right after |
| 1278 starting the completion: > | |
| 1279 :imap <F7> <C-N><C-P> | |
| 793 | 1280 < |
| 1281 *popupmenu-keys* | |
| 667 | 1282 In the first state these keys have a special meaning: |
| 1283 <BS> and CTRL-H Delete one character, find the matches for the word before | |
| 1284 the cursor. This reduces the list of matches, often to one | |
| 682 | 1285 entry, and switches to the second state. |
| 825 | 1286 Any non-special character: |
| 1287 Stop completion without changing the match and insert the | |
| 1288 typed character. | |
| 665 | 1289 |
| 825 | 1290 In the second and third state these keys have a special meaning: |
| 659 | 1291 <BS> and CTRL-H Delete one character, find the matches for the shorter word |
| 1292 before the cursor. This may find more matches. | |
| 1293 CTRL-L Add one character from the current match, may reduce the | |
| 667 | 1294 number of matches. |
| 682 | 1295 any printable, non-white character: |
| 1296 Add this character and reduce the number of matches. | |
| 667 | 1297 |
| 825 | 1298 In all three states these can be used: |
| 816 | 1299 CTRL-Y Yes: Accept the currently selected match and stop completion. |
| 1121 | 1300 CTRL-E End completion, go back to what was there before selecting a |
| 1301 match (what was typed or longest common string). | |
| 682 | 1302 <PageUp> Select a match several entries back, but don't insert it. |
| 1303 <PageDown> Select a match several entries further, but don't insert it. | |
| 665 | 1304 <Up> Select the previous match, as if CTRL-P was used, but don't |
| 682 | 1305 insert it. |
| 665 | 1306 <Down> Select the next match, as if CTRL-N was used, but don't |
| 682 | 1307 insert it. |
| 1121 | 1308 <Space> or <Tab> Stop completion without changing the match and insert the |
| 825 | 1309 typed character. |
| 1310 | |
| 1203 | 1311 The behavior of the <Enter> key depends on the state you are in: |
| 825 | 1312 first state: Use the text as it is and insert a line break. |
| 1313 second state: Insert the currently selected match. | |
| 1314 third state: Use the text as it is and insert a line break. | |
| 1315 | |
| 1316 In other words: If you used the cursor keys to select another entry in the | |
| 1203 | 1317 list of matches then the <Enter> key inserts that match. If you typed |
| 1318 something else then <Enter> inserts a line break. | |
| 667 | 1319 |
| 540 | 1320 |
| 1321 The colors of the menu can be changed with these highlight groups: | |
| 1322 Pmenu normal item |hl-Pmenu| | |
| 1323 PmenuSel selected item |hl-PmenuSel| | |
| 1324 PmenuSbar scrollbar |hl-PmenuSbar| | |
| 1325 PmenuThumb thumb of the scrollbar |hl-PmenuThumb| | |
| 1326 | |
| 667 | 1327 There are no special mappings for when the popup menu is visible. However, |
| 1328 you can use an Insert mode mapping that checks the |pumvisible()| function to | |
| 1329 do something different. Example: > | |
| 1330 :inoremap <Down> <C-R>=pumvisible() ? "\<lt>C-N>" : "\<lt>Down>"<CR> | |
| 540 | 1331 |
| 723 | 1332 You can use of <expr> in mapping to have the popup menu used when typing a |
| 1333 character and some condition is met. For example, for typing a dot: > | |
| 1334 inoremap <expr> . MayComplete() | |
| 1335 func MayComplete() | |
| 1336 if (can complete) | |
| 1337 return ".\<C-X>\<C-O>" | |
| 1338 endif | |
| 1339 return '.' | |
| 1340 endfunc | |
| 1341 | |
| 1342 See |:map-<expr>| for more info. | |
| 1343 | |
| 667 | 1344 |
| 1345 FILETYPE-SPECIFIC REMARKS FOR OMNI COMPLETION *compl-omni-filetypes* | |
| 1346 | |
| 1347 The file used for {filetype} should be autoload/{filetype}complete.vim | |
| 1348 in 'runtimepath'. Thus for "java" it is autoload/javacomplete.vim. | |
| 519 | 1349 |
| 557 | 1350 |
| 523 | 1351 C *ft-c-omni* |
| 519 | 1352 |
| 523 | 1353 Completion of C code requires a tags file. You should use Exuberant ctags, |
| 1354 because it adds extra information that is needed for completion. You can find | |
| 1121 | 1355 it here: http://ctags.sourceforge.net/ Version 5.6 or later is recommended. |
| 1356 | |
| 523 | 1357 For version 5.5.4 you should add a patch that adds the "typename:" field: |
| 711 | 1358 ftp://ftp.vim.org/pub/vim/unstable/patches/ctags-5.5.4.patch |
| 659 | 1359 A compiled .exe for MS-Windows can be found at: |
| 12968 | 1360 http://ctags.sourceforge.net/ |
| 1361 https://github.com/universal-ctags/ctags-win32 | |
| 519 | 1362 |
| 1363 If you want to complete system functions you can do something like this. Use | |
| 1364 ctags to generate a tags file for all the system header files: > | |
| 1365 % ctags -R -f ~/.vim/systags /usr/include /usr/local/include | |
| 1366 In your vimrc file add this tags file to the 'tags' option: > | |
| 1367 set tags+=~/.vim/systags | |
| 1368 | |
| 1369 When using CTRL-X CTRL-O after a name without any "." or "->" it is completed | |
| 1370 from the tags file directly. This works for any identifier, also function | |
| 1371 names. If you want to complete a local variable name, which does not appear | |
| 1372 in the tags file, use CTRL-P instead. | |
| 1373 | |
| 1374 When using CTRL-X CTRL-O after something that has "." or "->" Vim will attempt | |
| 1375 to recognize the type of the variable and figure out what members it has. | |
| 1376 This means only members valid for the variable will be listed. | |
| 1377 | |
| 523 | 1378 When a member name already was complete, CTRL-X CTRL-O will add a "." or |
| 1379 "->" for composite types. | |
| 1380 | |
| 519 | 1381 Vim doesn't include a C compiler, only the most obviously formatted |
| 1382 declarations are recognized. Preprocessor stuff may cause confusion. | |
| 1383 When the same structure name appears in multiple places all possible members | |
| 1384 are included. | |
| 1385 | |
| 529 | 1386 |
| 625 | 1387 CSS *ft-css-omni* |
| 557 | 1388 |
| 1389 Complete properties and their appropriate values according to CSS 2.1 | |
| 818 | 1390 specification. |
| 557 | 1391 |
| 1392 | |
| 818 | 1393 HTML *ft-html-omni* |
| 1394 XHTML *ft-xhtml-omni* | |
| 529 | 1395 |
| 667 | 1396 CTRL-X CTRL-O provides completion of various elements of (X)HTML files. It is |
| 6051 | 1397 designed to support writing of XHTML 1.0 Strict files but will also work for |
| 667 | 1398 other versions of HTML. Features: |
| 529 | 1399 |
| 667 | 1400 - after "<" complete tag name depending on context (no div suggestion inside |
| 1401 of an a tag); '/>' indicates empty tags | |
| 1402 - inside of tag complete proper attributes (no width attribute for an a tag); | |
| 1403 show also type of attribute; '*' indicates required attributes | |
| 1404 - when attribute has limited number of possible values help to complete them | |
| 557 | 1405 - complete names of entities |
| 532 | 1406 - complete values of "class" and "id" attributes with data obtained from |
| 667 | 1407 <style> tag and included CSS files |
| 659 | 1408 - when completing value of "style" attribute or working inside of "style" tag |
| 532 | 1409 switch to |ft-css-omni| completion |
| 667 | 1410 - when completing values of events attributes or working inside of "script" |
| 1411 tag switch to |ft-javascript-omni| completion | |
| 532 | 1412 - when used after "</" CTRL-X CTRL-O will close the last opened tag |
| 529 | 1413 |
| 557 | 1414 Note: When used first time completion menu will be shown with little delay |
| 818 | 1415 - this is time needed for loading of data file. |
| 659 | 1416 Note: Completion may fail in badly formatted documents. In such case try to |
| 1417 run |:make| command to detect formatting problems. | |
| 557 | 1418 |
| 1419 | |
| 836 | 1420 HTML flavor *html-flavor* |
| 1421 | |
| 859 | 1422 The default HTML completion depends on the filetype. For HTML files it is |
| 1423 HTML 4.01 Transitional ('filetype' is "html"), for XHTML it is XHTML 1.0 | |
| 1424 Strict ('filetype' is "xhtml"). | |
| 836 | 1425 |
| 859 | 1426 When doing completion outside of any other tag you will have possibility to |
| 1427 choose DOCTYPE and the appropriate data file will be loaded and used for all | |
| 1428 next completions. | |
| 836 | 1429 |
| 859 | 1430 More about format of data file in |xml-omni-datafile|. Some of the data files |
| 1431 may be found on the Vim website (|www|). | |
| 836 | 1432 |
| 859 | 1433 Note that b:html_omni_flavor may point to a file with any XML data. This |
| 1434 makes possible to mix PHP (|ft-php-omni|) completion with any XML dialect | |
| 1435 (assuming you have data file for it). Without setting that variable XHTML 1.0 | |
| 1436 Strict will be used. | |
| 836 | 1437 |
| 1438 | |
| 818 | 1439 JAVASCRIPT *ft-javascript-omni* |
| 649 | 1440 |
| 659 | 1441 Completion of most elements of JavaScript language and DOM elements. |
| 649 | 1442 |
| 1443 Complete: | |
| 1444 | |
| 1445 - variables | |
| 667 | 1446 - function name; show function arguments |
| 649 | 1447 - function arguments |
| 1448 - properties of variables trying to detect type of variable | |
| 659 | 1449 - complete DOM objects and properties depending on context |
| 649 | 1450 - keywords of language |
| 1451 | |
| 659 | 1452 Completion works in separate JavaScript files (&ft==javascript), inside of |
| 1453 <script> tag of (X)HTML and in values of event attributes (including scanning | |
| 5220 | 1454 of external files). |
| 818 | 1455 |
| 649 | 1456 DOM compatibility |
| 1457 | |
| 1458 At the moment (beginning of 2006) there are two main browsers - MS Internet | |
| 1459 Explorer and Mozilla Firefox. These two applications are covering over 90% of | |
| 1460 market. Theoretically standards are created by W3C organisation | |
| 1461 (http://www.w3c.org) but they are not always followed/implemented. | |
| 1462 | |
| 818 | 1463 IE FF W3C Omni completion ~ |
| 1464 +/- +/- + + ~ | |
| 1465 + + - + ~ | |
| 1466 + - - - ~ | |
| 1467 - + - - ~ | |
| 649 | 1468 |
| 1469 Regardless from state of implementation in browsers but if element is defined | |
| 1470 in standards, completion plugin will place element in suggestion list. When | |
| 1471 both major engines implemented element, even if this is not in standards it | |
| 1472 will be suggested. All other elements are not placed in suggestion list. | |
| 1473 | |
| 1474 | |
| 818 | 1475 PHP *ft-php-omni* |
| 714 | 1476 |
| 1121 | 1477 Completion of PHP code requires a tags file for completion of data from |
| 1478 external files and for class aware completion. You should use Exuberant ctags | |
| 1479 version 5.5.4 or newer. You can find it here: http://ctags.sourceforge.net/ | |
| 714 | 1480 |
| 1481 Script completes: | |
| 1482 | |
| 1483 - after $ variables name | |
| 728 | 1484 - if variable was declared as object add "->", if tags file is available show |
| 1485 name of class | |
| 819 | 1486 - after "->" complete only function and variable names specific for given |
| 1487 class. To find class location and contents tags file is required. Because | |
| 1488 PHP isn't strongly typed language user can use @var tag to declare class: > | |
| 1489 | |
| 856 | 1490 /* @var $myVar myClass */ |
| 819 | 1491 $myVar-> |
| 1492 < | |
| 1493 Still, to find myClass contents tags file is required. | |
| 728 | 1494 |
| 843 | 1495 - function names with additional info: |
| 728 | 1496 - in case of built-in functions list of possible arguments and after | type |
| 1497 data returned by function | |
|
2207
b17bbfa96fa0
Add the settabvar() and gettabvar() functions.
Bram Moolenaar <bram@vim.org>
parents:
2154
diff
changeset
|
1498 - in case of user function arguments and name of file where function was |
| 728 | 1499 defined (if it is not current file) |
| 1500 | |
| 1501 - constants names | |
| 1502 - class names after "new" declaration | |
| 1503 | |
| 714 | 1504 |
| 1505 Note: when doing completion first time Vim will load all necessary data into | |
| 1506 memory. It may take several seconds. After next use of completion delay | |
| 728 | 1507 should not be noticeable. |
| 714 | 1508 |
| 1509 Script detects if cursor is inside <?php ?> tags. If it is outside it will | |
| 1510 automatically switch to HTML/CSS/JavaScript completion. Note: contrary to | |
| 1511 original HTML files completion of tags (and only tags) isn't context aware. | |
| 1512 | |
| 1513 | |
| 856 | 1514 RUBY *ft-ruby-omni* |
| 838 | 1515 |
| 1516 Completion of Ruby code requires that vim be built with |+ruby|. | |
| 1517 | |
| 1518 Ruby completion will parse your buffer on demand in order to provide a list of | |
| 1519 completions. These completions will be drawn from modules loaded by 'require' | |
| 1520 and modules defined in the current buffer. | |
| 1521 | |
| 1522 The completions provided by CTRL-X CTRL-O are sensitive to the context: | |
| 1523 | |
| 856 | 1524 CONTEXT COMPLETIONS PROVIDED ~ |
| 838 | 1525 |
| 1526 1. Not inside a class definition Classes, constants and globals | |
| 1527 | |
| 856 | 1528 2. Inside a class definition Methods or constants defined in the class |
| 838 | 1529 |
| 856 | 1530 3. After '.', '::' or ':' Methods applicable to the object being |
| 1531 dereferenced | |
| 838 | 1532 |
| 856 | 1533 4. After ':' or ':foo' Symbol name (beginning with 'foo') |
| 838 | 1534 |
| 1535 Notes: | |
| 1536 - Vim will load/evaluate code in order to provide completions. This may | |
| 13125 | 1537 cause some code execution, which may be a concern. This is no longer |
| 1121 | 1538 enabled by default, to enable this feature add > |
| 1539 let g:rubycomplete_buffer_loading = 1 | |
| 1540 <- In context 1 above, Vim can parse the entire buffer to add a list of | |
| 843 | 1541 classes to the completion results. This feature is turned off by default, |
| 1542 to enable it add > | |
| 1543 let g:rubycomplete_classes_in_global = 1 | |
| 1544 < to your vimrc | |
| 838 | 1545 - In context 2 above, anonymous classes are not supported. |
| 1546 - In context 3 above, Vim will attempt to determine the methods supported by | |
| 1547 the object. | |
| 1548 - Vim can detect and load the Rails environment for files within a rails | |
| 1549 project. The feature is disabled by default, to enable it add > | |
| 843 | 1550 let g:rubycomplete_rails = 1 |
| 1551 < to your vimrc | |
| 838 | 1552 |
| 1553 | |
| 625 | 1554 SYNTAX *ft-syntax-omni* |
| 1555 | |
| 1121 | 1556 Vim has the ability to color syntax highlight nearly 500 languages. Part of |
| 1557 this highlighting includes knowing what keywords are part of a language. Many | |
| 1558 filetypes already have custom completion scripts written for them, the | |
| 1559 syntaxcomplete plugin provides basic completion for all other filetypes. It | |
| 1560 does this by populating the omni completion list with the text Vim already | |
| 1561 knows how to color highlight. It can be used for any filetype and provides a | |
| 1562 minimal language-sensitive completion. | |
| 625 | 1563 |
| 702 | 1564 To enable syntax code completion you can run: > |
| 4869 | 1565 setlocal omnifunc=syntaxcomplete#Complete |
| 702 | 1566 |
| 4869 | 1567 You can automate this by placing the following in your |.vimrc| (after any |
| 702 | 1568 ":filetype" command): > |
| 1569 if has("autocmd") && exists("+omnifunc") | |
| 818 | 1570 autocmd Filetype * |
| 1571 \ if &omnifunc == "" | | |
| 1572 \ setlocal omnifunc=syntaxcomplete#Complete | | |
| 1573 \ endif | |
| 702 | 1574 endif |
| 1575 | |
| 1576 The above will set completion to this script only if a specific plugin does | |
| 1577 not already exist for that filetype. | |
| 1578 | |
| 1579 Each filetype can have a wide range of syntax items. The plugin allows you to | |
| 1580 customize which syntax groups to include or exclude from the list. Let's have | |
| 1581 a look at the PHP filetype to see how this works. | |
| 1582 | |
| 1583 If you edit a file called, index.php, run the following command: > | |
| 4869 | 1584 syntax list |
| 625 | 1585 |
|
2207
b17bbfa96fa0
Add the settabvar() and gettabvar() functions.
Bram Moolenaar <bram@vim.org>
parents:
2154
diff
changeset
|
1586 The first thing you will notice is that there are many different syntax groups. |
|
b17bbfa96fa0
Add the settabvar() and gettabvar() functions.
Bram Moolenaar <bram@vim.org>
parents:
2154
diff
changeset
|
1587 The PHP language can include elements from different languages like HTML, |
| 702 | 1588 JavaScript and many more. The syntax plugin will only include syntax groups |
| 1589 that begin with the filetype, "php", in this case. For example these syntax | |
| 1590 groups are included by default with the PHP: phpEnvVar, phpIntVar, | |
| 1591 phpFunctions. | |
| 1592 | |
| 13125 | 1593 If you wish non-filetype syntax items to also be included, you can use a |
| 1594 regular expression syntax (added in version 13.0 of | |
|
14249
4543777545a3
Updated runtime and language files.
Christian Brabandt <cb@256bit.org>
parents:
14123
diff
changeset
|
1595 autoload/syntaxcomplete.vim) to add items. Looking at the output from |
| 13125 | 1596 ":syntax list" while editing a PHP file I can see some of these entries: > |
| 4869 | 1597 htmlArg,htmlTag,htmlTagName,javaScriptStatement,javaScriptGlobalObjects |
| 625 | 1598 |
| 4869 | 1599 To pick up any JavaScript and HTML keyword syntax groups while editing a PHP |
| 13125 | 1600 file, you can use 3 different regexs, one for each language. Or you can |
| 1601 simply restrict the include groups to a particular value, without using | |
| 4869 | 1602 a regex string: > |
| 1603 let g:omni_syntax_group_include_php = 'php\w\+,javaScript\w\+,html\w\+' | |
| 1604 let g:omni_syntax_group_include_php = 'phpFunctions,phpMethods' | |
| 1605 < | |
| 1606 The basic form of this variable is: > | |
| 1607 let g:omni_syntax_group_include_{filetype} = 'regex,comma,separated' | |
| 1608 | |
| 1609 The PHP language has an enormous number of items which it knows how to syntax | |
| 5220 | 1610 highlight. These items will be available within the omni completion list. |
| 4869 | 1611 |
| 1612 Some people may find this list unwieldy or are only interested in certain | |
| 1613 items. There are two ways to prune this list (if necessary). If you find | |
| 13125 | 1614 certain syntax groups you do not wish displayed you can use two different |
| 1615 methods to identify these groups. The first specifically lists the syntax | |
| 1616 groups by name. The second uses a regular expression to identify both | |
| 4869 | 1617 syntax groups. Simply add one the following to your vimrc: > |
| 1618 let g:omni_syntax_group_exclude_php = 'phpCoreConstant,phpConstant' | |
| 1619 let g:omni_syntax_group_exclude_php = 'php\w*Constant' | |
| 702 | 1620 |
| 1621 Add as many syntax groups to this list by comma separating them. The basic | |
| 1622 form of this variable is: > | |
| 4869 | 1623 let g:omni_syntax_group_exclude_{filetype} = 'regex,comma,separated' |
| 702 | 1624 |
| 1625 You can create as many of these variables as you need, varying only the | |
| 1626 filetype at the end of the variable name. | |
| 625 | 1627 |
| 1121 | 1628 The plugin uses the isKeyword option to determine where word boundaries are |
| 1629 for the syntax items. For example, in the Scheme language completion should | |
| 1630 include the "-", call-with-output-file. Depending on your filetype, this may | |
| 1631 not provide the words you are expecting. Setting the | |
| 1632 g:omni_syntax_use_iskeyword option to 0 will force the syntax plugin to break | |
| 1633 on word characters. This can be controlled adding the following to your | |
| 1634 vimrc: > | |
| 1635 let g:omni_syntax_use_iskeyword = 0 | |
| 1636 | |
| 2439 | 1637 For plugin developers, the plugin exposes a public function OmniSyntaxList. |
| 1638 This function can be used to request a List of syntax items. When editing a | |
| 13125 | 1639 SQL file (:e syntax.sql) you can use the ":syntax list" command to see the |
| 2439 | 1640 various groups and syntax items. For example: > |
| 13125 | 1641 syntax list |
| 2439 | 1642 |
| 13125 | 1643 Yields data similar to this: |
| 1644 sqlOperator xxx some prior all like and any escape exists in is not ~ | |
| 1645 or intersect minus between distinct ~ | |
| 1646 links to Operator ~ | |
| 1647 sqlType xxx varbit varchar nvarchar bigint int uniqueidentifier ~ | |
| 1648 date money long tinyint unsigned xml text smalldate ~ | |
| 1649 double datetime nchar smallint numeric time bit char ~ | |
| 1650 varbinary binary smallmoney ~ | |
| 1651 image float integer timestamp real decimal ~ | |
| 2439 | 1652 |
| 1653 There are two syntax groups listed here: sqlOperator and sqlType. To retrieve | |
| 13125 | 1654 a List of syntax items you can call OmniSyntaxList a number of different |
| 2439 | 1655 ways. To retrieve all syntax items regardless of syntax group: > |
| 1656 echo OmniSyntaxList( [] ) | |
| 1657 | |
| 1658 To retrieve only the syntax items for the sqlOperator syntax group: > | |
| 1659 echo OmniSyntaxList( ['sqlOperator'] ) | |
| 1660 | |
| 1661 To retrieve all syntax items for both the sqlOperator and sqlType groups: > | |
| 1662 echo OmniSyntaxList( ['sqlOperator', 'sqlType'] ) | |
| 1663 | |
| 4869 | 1664 A regular expression can also be used: > |
| 1665 echo OmniSyntaxList( ['sql\w\+'] ) | |
| 1666 | |
| 2439 | 1667 From within a plugin, you would typically assign the output to a List: > |
| 1668 let myKeywords = [] | |
| 1669 let myKeywords = OmniSyntaxList( ['sqlKeyword'] ) | |
| 1670 | |
| 625 | 1671 |
| 818 | 1672 SQL *ft-sql-omni* |
| 1673 | |
| 1674 Completion for the SQL language includes statements, functions, keywords. | |
| 1675 It will also dynamically complete tables, procedures, views and column lists | |
| 1676 with data pulled directly from within a database. For detailed instructions | |
| 1677 and a tutorial see |omni-sql-completion|. | |
| 1678 | |
| 819 | 1679 The SQL completion plugin can be used in conjunction with other completion |
|
2033
de5a43c5eedc
Update documentation files.
Bram Moolenaar <bram@zimbu.org>
parents:
1702
diff
changeset
|
1680 plugins. For example, the PHP filetype has its own completion plugin. |
| 819 | 1681 Since PHP is often used to generate dynamic website by accessing a database, |
| 1682 the SQL completion plugin can also be enabled. This allows you to complete | |
| 1683 PHP code and SQL code at the same time. | |
| 1684 | |
| 818 | 1685 |
| 625 | 1686 XML *ft-xml-omni* |
| 557 | 1687 |
| 859 | 1688 Vim 7 provides a mechanism for context aware completion of XML files. It |
| 1689 depends on a special |xml-omni-datafile| and two commands: |:XMLns| and | |
| 1690 |:XMLent|. Features are: | |
| 557 | 1691 |
| 859 | 1692 - after "<" complete the tag name, depending on context |
| 1693 - inside of a tag complete proper attributes | |
| 1694 - when an attribute has a limited number of possible values help to complete | |
| 557 | 1695 them |
| 859 | 1696 - complete names of entities (defined in |xml-omni-datafile| and in the |
| 1697 current file with "<!ENTITY" declarations) | |
| 557 | 1698 - when used after "</" CTRL-X CTRL-O will close the last opened tag |
| 1699 | |
| 625 | 1700 Format of XML data file *xml-omni-datafile* |
| 557 | 1701 |
| 859 | 1702 XML data files are stored in the "autoload/xml" directory in 'runtimepath'. |
| 1703 Vim distribution provides examples of data files in the | |
| 1704 "$VIMRUNTIME/autoload/xml" directory. They have a meaningful name which will | |
| 1705 be used in commands. It should be a unique name which will not create | |
| 1706 conflicts. For example, the name xhtml10s.vim means it is the data file for | |
| 1707 XHTML 1.0 Strict. | |
| 557 | 1708 |
| 859 | 1709 Each file contains a variable with a name like g:xmldata_xhtml10s . It is |
| 1710 a compound from two parts: | |
| 557 | 1711 |
| 859 | 1712 1. "g:xmldata_" general prefix, constant for all data files |
| 1713 2. "xhtml10s" the name of the file and the name of the described XML | |
| 1714 dialect; it will be used as an argument for the |:XMLns| | |
| 1715 command | |
| 557 | 1716 |
| 1717 Part two must be exactly the same as name of file. | |
| 1718 | |
| 859 | 1719 The variable is a |Dictionary|. Keys are tag names and each value is a two |
| 1720 element |List|. The first element of the List is also a List with the names | |
| 1721 of possible children. The second element is a |Dictionary| with the names of | |
| 1722 attributes as keys and the possible values of attributes as values. Example: > | |
| 557 | 1723 |
| 859 | 1724 let g:xmldata_crippled = { |
| 1725 \ "vimxmlentities": ["amp", "lt", "gt", "apos", "quot"], | |
| 1726 \ 'vimxmlroot': ['tag1'], | |
| 1727 \ 'tag1': | |
| 1728 \ [ ['childoftag1a', 'childoftag1b'], {'attroftag1a': [], | |
| 1729 \ 'attroftag1b': ['valueofattr1', 'valueofattr2']}], | |
| 1730 \ 'childoftag1a': | |
| 1731 \ [ [], {'attrofchild': ['attrofchild']}], | |
| 1732 \ 'childoftag1b': | |
| 1733 \ [ ['childoftag1a'], {'attrofchild': []}], | |
| 667 | 1734 \ "vimxmltaginfo": { |
| 859 | 1735 \ 'tag1': ['Menu info', 'Long information visible in preview window']}, |
| 1736 \ 'vimxmlattrinfo': { | |
| 1737 \ 'attrofchild': ['Menu info', 'Long information visible in preview window']}} | |
| 557 | 1738 |
| 859 | 1739 This example would be put in the "autoload/xml/crippled.vim" file and could |
| 1740 help to write this file: > | |
| 557 | 1741 |
| 859 | 1742 <tag1 attroftag1b="valueofattr1"> |
| 1743 <childoftag1a attrofchild> | |
| 1744 & < | |
| 1745 </childoftag1a> | |
| 1746 <childoftag1b attrofchild="5"> | |
| 1747 <childoftag1a> | |
| 1748 > ' " | |
| 1749 </childoftag1a> | |
| 1750 </childoftag1b> | |
| 1751 </tag1> | |
| 1752 | |
| 1753 In the example four special elements are visible: | |
| 1754 | |
| 1755 1. "vimxmlentities" - a special key with List containing entities of this XML | |
| 557 | 1756 dialect. |
| 859 | 1757 2. If the list containing possible values of attributes has one element and |
| 1758 this element is equal to the name of the attribute this attribute will be | |
| 1759 treated as boolean and inserted as 'attrname' and not as 'attrname="' | |
| 1760 3. "vimxmltaginfo" - a special key with a Dictionary containing tag | |
| 1761 names as keys and two element List as values, for additional menu info and | |
| 1762 the long description. | |
| 1763 4. "vimxmlattrinfo" - special key with Dictionary containing attribute names | |
| 1764 as keys and two element List as values, for additional menu info and long | |
| 667 | 1765 description. |
| 557 | 1766 |
| 859 | 1767 Note: Tag names in the data file MUST not contain a namespace description. |
| 1768 Check xsl.vim for an example. | |
| 1769 Note: All data and functions are publicly available as global | |
| 1770 variables/functions and can be used for personal editing functions. | |
| 557 | 1771 |
| 667 | 1772 |
| 856 | 1773 DTD -> Vim *dtd2vim* |
| 836 | 1774 |
| 859 | 1775 On |www| is the script |dtd2vim| which parses DTD and creates an XML data file |
| 836 | 1776 for Vim XML omni completion. |
| 1777 | |
| 1778 dtd2vim: http://www.vim.org/scripts/script.php?script_id=1462 | |
| 1779 | |
| 859 | 1780 Check the beginning of that file for usage details. |
| 1781 The script requires perl and: | |
| 836 | 1782 |
| 1783 perlSGML: http://savannah.nongnu.org/projects/perlsgml | |
| 1784 | |
| 1785 | |
| 557 | 1786 Commands |
| 1787 | |
| 625 | 1788 :XMLns {name} [{namespace}] *:XMLns* |
| 557 | 1789 |
| 859 | 1790 Vim has to know which data file should be used and with which namespace. For |
| 1791 loading of the data file and connecting data with the proper namespace use | |
| 1792 |:XMLns| command. The first (obligatory) argument is the name of the data | |
| 1793 (xhtml10s, xsl). The second argument is the code of namespace (h, xsl). When | |
| 1794 used without a second argument the dialect will be used as default - without | |
| 1795 namespace declaration. For example to use XML completion in .xsl files: > | |
| 557 | 1796 |
| 1797 :XMLns xhtml10s | |
| 1798 :XMLns xsl xsl | |
| 1799 | |
| 1800 | |
| 625 | 1801 :XMLent {name} *:XMLent* |
| 557 | 1802 |
| 859 | 1803 By default entities will be completed from the data file of the default |
| 1804 namespace. The XMLent command should be used in case when there is no default | |
| 1805 namespace: > | |
| 557 | 1806 |
| 625 | 1807 :XMLent xhtml10s |
| 557 | 1808 |
| 1809 Usage | |
| 1810 | |
| 859 | 1811 While used in this situation (after declarations from previous part, | is |
| 557 | 1812 cursor position): > |
| 1813 | |
| 625 | 1814 <| |
| 557 | 1815 |
| 859 | 1816 Will complete to an appropriate XHTML tag, and in this situation: > |
| 557 | 1817 |
| 625 | 1818 <xsl:| |
| 557 | 1819 |
| 859 | 1820 Will complete to an appropriate XSL tag. |
| 1821 | |
| 557 | 1822 |
| 859 | 1823 The script xmlcomplete.vim, provided through the |autoload| mechanism, |
| 1824 has the xmlcomplete#GetLastOpenTag() function which can be used in XML files | |
| 1825 to get the name of the last open tag (b:unaryTagsStack has to be defined): > | |
| 529 | 1826 |
| 625 | 1827 :echo xmlcomplete#GetLastOpenTag("b:unaryTagsStack") |
| 531 | 1828 |
| 529 | 1829 |
| 532 | 1830 |
| 7 | 1831 ============================================================================== |
| 1832 8. Insert mode commands *inserting* | |
| 1833 | |
| 1834 The following commands can be used to insert new text into the buffer. They | |
| 1835 can all be undone and repeated with the "." command. | |
| 1836 | |
| 1837 *a* | |
| 1838 a Append text after the cursor [count] times. If the | |
| 1839 cursor is in the first column of an empty line Insert | |
| 1840 starts there. But not when 'virtualedit' is set! | |
| 1841 | |
| 1842 *A* | |
| 1843 A Append text at the end of the line [count] times. | |
| 1844 | |
| 1845 <insert> or *i* *insert* *<Insert>* | |
| 1846 i Insert text before the cursor [count] times. | |
| 1847 When using CTRL-O in Insert mode |i_CTRL-O| the count | |
| 1848 is not supported. | |
| 1849 | |
| 1850 *I* | |
| 1851 I Insert text before the first non-blank in the line | |
| 1852 [count] times. | |
| 164 | 1853 When the 'H' flag is present in 'cpoptions' and the |
| 1854 line only contains blanks, insert start just before | |
| 1855 the last blank. | |
| 7 | 1856 |
| 1857 *gI* | |
|
16553
0e473e9e70c2
patch 8.1.1280: remarks about functionality not in Vi clutters the help
Bram Moolenaar <Bram@vim.org>
parents:
16267
diff
changeset
|
1858 gI Insert text in column 1 [count] times. |
| 7 | 1859 |
| 1860 *gi* | |
| 1861 gi Insert text in the same position as where Insert mode | |
| 1862 was stopped last time in the current buffer. | |
| 1863 This uses the |'^| mark. It's different from "`^i" | |
| 1864 when the mark is past the end of the line. | |
| 1865 The position is corrected for inserted/deleted lines, | |
| 1866 but NOT for inserted/deleted characters. | |
| 1867 When the |:keepjumps| command modifier is used the |'^| | |
| 9 | 1868 mark won't be changed. |
| 7 | 1869 |
| 1870 *o* | |
| 1871 o Begin a new line below the cursor and insert text, | |
| 16610 | 1872 repeat [count] times. |
| 164 | 1873 When the '#' flag is in 'cpoptions' the count is |
| 1874 ignored. | |
| 7 | 1875 |
| 1876 *O* | |
| 1877 O Begin a new line above the cursor and insert text, | |
| 16610 | 1878 repeat [count] times. |
| 164 | 1879 When the '#' flag is in 'cpoptions' the count is |
| 1880 ignored. | |
| 7 | 1881 |
| 1882 These commands are used to start inserting text. You can end insert mode with | |
| 1883 <Esc>. See |mode-ins-repl| for the other special characters in Insert mode. | |
| 1884 The effect of [count] takes place after Insert mode is exited. | |
| 1885 | |
| 1886 When 'autoindent' is on, the indent for a new line is obtained from the | |
| 1887 previous line. When 'smartindent' or 'cindent' is on, the indent for a line | |
| 1888 is automatically adjusted for C programs. | |
| 1889 | |
| 1890 'textwidth' can be set to the maximum width for a line. When a line becomes | |
| 1891 too long when appending characters a line break is automatically inserted. | |
| 1892 | |
| 1893 | |
| 1894 ============================================================================== | |
| 1895 9. Ex insert commands *inserting-ex* | |
| 1896 | |
| 1897 *:a* *:append* | |
| 167 | 1898 :{range}a[ppend][!] Insert several lines of text below the specified |
| 7 | 1899 line. If the {range} is missing, the text will be |
| 1900 inserted after the current line. | |
| 167 | 1901 Adding [!] toggles 'autoindent' for the time this |
| 1902 command is executed. | |
| 7 | 1903 |
| 1904 *:i* *:in* *:insert* | |
| 167 | 1905 :{range}i[nsert][!] Insert several lines of text above the specified |
| 7 | 1906 line. If the {range} is missing, the text will be |
| 1907 inserted before the current line. | |
| 167 | 1908 Adding [!] toggles 'autoindent' for the time this |
| 1909 command is executed. | |
| 7 | 1910 |
| 1911 These two commands will keep on asking for lines, until you type a line | |
| 1912 containing only a ".". Watch out for lines starting with a backslash, see | |
| 1913 |line-continuation|. | |
|
2033
de5a43c5eedc
Update documentation files.
Bram Moolenaar <bram@zimbu.org>
parents:
1702
diff
changeset
|
1914 |
| 2596 | 1915 When in Ex mode (see |-e|) a backslash at the end of the line can be used to |
| 1916 insert a NUL character. To be able to have a line ending in a backslash use | |
| 1917 two backslashes. This means that the number of backslashes is halved, but | |
| 1918 only at the end of the line. | |
| 1919 | |
|
2033
de5a43c5eedc
Update documentation files.
Bram Moolenaar <bram@zimbu.org>
parents:
1702
diff
changeset
|
1920 NOTE: These commands cannot be used with |:global| or |:vglobal|. |
|
de5a43c5eedc
Update documentation files.
Bram Moolenaar <bram@zimbu.org>
parents:
1702
diff
changeset
|
1921 ":append" and ":insert" don't work properly in between ":if" and |
| 74 | 1922 ":endif", ":for" and ":endfor", ":while" and ":endwhile". |
| 7 | 1923 |
| 1924 *:start* *:startinsert* | |
| 1925 :star[tinsert][!] Start Insert mode just after executing this command. | |
| 1926 Works like typing "i" in Normal mode. When the ! is | |
| 1927 included it works like "A", append to the line. | |
| 1928 Otherwise insertion starts at the cursor position. | |
| 1929 Note that when using this command in a function or | |
| 1930 script, the insertion only starts after the function | |
| 1931 or script is finished. | |
| 446 | 1932 This command does not work from |:normal|. |
| 7 | 1933 |
| 1934 *:stopi* *:stopinsert* | |
| 1935 :stopi[nsert] Stop Insert mode as soon as possible. Works like | |
| 1936 typing <Esc> in Insert mode. | |
| 1937 Can be used in an autocommand, example: > | |
| 1938 :au BufEnter scratch stopinsert | |
| 14 | 1939 < |
| 1940 *replacing-ex* *:startreplace* | |
| 1941 :startr[eplace][!] Start Replace mode just after executing this command. | |
| 1942 Works just like typing "R" in Normal mode. When the | |
| 1943 ! is included it acts just like "$R" had been typed | |
| 1944 (ie. begin replace mode at the end-of-line). Other- | |
| 1945 wise replacement begins at the cursor position. | |
| 1946 Note that when using this command in a function or | |
| 1947 script that the replacement will only start after | |
| 1948 the function or script is finished. | |
| 7 | 1949 |
| 599 | 1950 *:startgreplace* |
| 1951 :startg[replace][!] Just like |:startreplace|, but use Virtual Replace | |
| 1952 mode, like with |gR|. | |
| 1953 | |
| 7 | 1954 ============================================================================== |
| 1955 10. Inserting a file *inserting-file* | |
| 1956 | |
| 1957 *:r* *:re* *:read* | |
| 819 | 1958 :r[ead] [++opt] [name] |
| 1959 Insert the file [name] (default: current file) below | |
| 7 | 1960 the cursor. |
| 819 | 1961 See |++opt| for the possible values of [++opt]. |
| 7 | 1962 |
| 819 | 1963 :{range}r[ead] [++opt] [name] |
| 1964 Insert the file [name] (default: current file) below | |
| 7 | 1965 the specified line. |
| 819 | 1966 See |++opt| for the possible values of [++opt]. |
| 7 | 1967 |
| 1968 *:r!* *:read!* | |
| 4278 | 1969 :[range]r[ead] [++opt] !{cmd} |
| 1970 Execute {cmd} and insert its standard output below | |
| 1121 | 1971 the cursor or the specified line. A temporary file is |
| 1972 used to store the output of the command which is then | |
| 1973 read into the buffer. 'shellredir' is used to save | |
| 1974 the output of the command, which can be set to include | |
| 1975 stderr or not. {cmd} is executed like with ":!{cmd}", | |
| 1976 any '!' is replaced with the previous command |:!|. | |
| 4278 | 1977 See |++opt| for the possible values of [++opt]. |
| 7 | 1978 |
| 1979 These commands insert the contents of a file, or the output of a command, | |
| 1980 into the buffer. They can be undone. They cannot be repeated with the "." | |
| 1981 command. They work on a line basis, insertion starts below the line in which | |
| 1982 the cursor is, or below the specified line. To insert text above the first | |
| 1983 line use the command ":0r {name}". | |
| 1984 | |
| 1985 After the ":read" command, the cursor is left on the first non-blank in the | |
| 1986 first new line. Unless in Ex mode, then the cursor is left on the last new | |
| 1987 line (sorry, this is Vi compatible). | |
| 1988 | |
| 1989 If a file name is given with ":r", it becomes the alternate file. This can be | |
| 1990 used, for example, when you want to edit that file instead: ":e! #". This can | |
| 1991 be switched off by removing the 'a' flag from the 'cpoptions' option. | |
| 1992 | |
| 819 | 1993 Of the [++opt] arguments one is specifically for ":read", the ++edit argument. |
| 1994 This is useful when the ":read" command is actually used to read a file into | |
| 1995 the buffer as if editing that file. Use this command in an empty buffer: > | |
| 1996 :read ++edit filename | |
| 1997 The effect is that the 'fileformat', 'fileencoding', 'bomb', etc. options are | |
| 1998 set to what has been detected for "filename". Note that a single empty line | |
| 1999 remains, you may want to delete it. | |
| 2000 | |
| 7 | 2001 *file-read* |
| 2002 The 'fileformat' option sets the <EOL> style for a file: | |
| 2003 'fileformat' characters name ~ | |
| 2004 "dos" <CR><NL> or <NL> DOS format | |
| 2005 "unix" <NL> Unix format | |
| 2006 "mac" <CR> Mac format | |
| 2007 Previously 'textmode' was used. It is obsolete now. | |
| 2008 | |
| 2009 If 'fileformat' is "dos", a <CR> in front of an <NL> is ignored and a CTRL-Z | |
| 2010 at the end of the file is ignored. | |
| 2011 | |
| 2012 If 'fileformat' is "mac", a <NL> in the file is internally represented by a | |
| 2013 <CR>. This is to avoid confusion with a <NL> which is used to represent a | |
| 2014 <NUL>. See |CR-used-for-NL|. | |
| 2015 | |
| 2016 If the 'fileformats' option is not empty Vim tries to recognize the type of | |
| 2017 <EOL> (see |file-formats|). However, the 'fileformat' option will not be | |
| 2018 changed, the detected format is only used while reading the file. | |
| 2019 A similar thing happens with 'fileencodings'. | |
| 2020 | |
| 19116 | 2021 On non-Win32 systems the message "[dos format]" is shown if a file is read in |
| 2022 DOS format, to remind you that something unusual is done. | |
| 18972 | 2023 On Macintosh and Win32 the message "[unix format]" is shown if a file is read |
| 2024 in Unix format. | |
| 19116 | 2025 On non-Macintosh systems, the message "[mac format]" is shown if a file is |
| 7 | 2026 read in Mac format. |
| 2027 | |
| 2028 An example on how to use ":r !": > | |
| 2029 :r !uuencode binfile binfile | |
| 2030 This command reads "binfile", uuencodes it and reads it into the current | |
| 2031 buffer. Useful when you are editing e-mail and want to include a binary | |
| 2032 file. | |
| 2033 | |
| 2034 *read-messages* | |
| 2035 When reading a file Vim will display a message with information about the read | |
| 2036 file. In the table is an explanation for some of the items. The others are | |
| 2037 self explanatory. Using the long or the short version depends on the | |
| 2038 'shortmess' option. | |
| 2039 | |
| 2040 long short meaning ~ | |
| 2041 [readonly] {RO} the file is write protected | |
| 2042 [fifo/socket] using a stream | |
| 2043 [fifo] using a fifo stream | |
| 2044 [socket] using a socket stream | |
| 2045 [CR missing] reading with "dos" 'fileformat' and a | |
| 2046 NL without a preceding CR was found. | |
| 2047 [NL found] reading with "mac" 'fileformat' and a | |
| 2048 NL was found (could be "unix" format) | |
| 2049 [long lines split] at least one line was split in two | |
| 2050 [NOT converted] conversion from 'fileencoding' to | |
| 2051 'encoding' was desired but not | |
| 2052 possible | |
| 2053 [converted] conversion from 'fileencoding' to | |
| 2054 'encoding' done | |
| 2055 [crypted] file was decrypted | |
| 2056 [READ ERRORS] not all of the file could be read | |
| 2057 | |
| 2058 | |
| 14421 | 2059 vim:tw=78:ts=8:noet:ft=help:norl: |