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