Mercurial > vim
annotate runtime/doc/usr_41.txt @ 2662:916c90b37ea9
Update runtime files.
| author | Bram Moolenaar <bram@vim.org> |
|---|---|
| date | Fri, 10 Dec 2010 20:35:50 +0100 |
| parents | 840c3cadb842 |
| children | b6471224d2af |
| rev | line source |
|---|---|
| 2662 | 1 *usr_41.txt* For Vim version 7.3. Last change: 2010 Nov 17 |
| 7 | 2 |
| 3 VIM USER MANUAL - by Bram Moolenaar | |
| 4 | |
| 5 Write a Vim script | |
| 6 | |
| 7 | |
| 8 The Vim script language is used for the startup vimrc file, syntax files, and | |
| 9 many other things. This chapter explains the items that can be used in a Vim | |
| 10 script. There are a lot of them, thus this is a long chapter. | |
| 11 | |
| 12 |41.1| Introduction | |
| 13 |41.2| Variables | |
| 14 |41.3| Expressions | |
| 15 |41.4| Conditionals | |
| 16 |41.5| Executing an expression | |
| 17 |41.6| Using functions | |
| 18 |41.7| Defining a function | |
| 161 | 19 |41.8| Lists and Dictionaries |
| 20 |41.9| Exceptions | |
| 21 |41.10| Various remarks | |
| 22 |41.11| Writing a plugin | |
| 23 |41.12| Writing a filetype plugin | |
| 24 |41.13| Writing a compiler plugin | |
| 170 | 25 |41.14| Writing a plugin that loads quickly |
| 26 |41.15| Writing library scripts | |
| 793 | 27 |41.16| Distributing Vim scripts |
| 7 | 28 |
| 29 Next chapter: |usr_42.txt| Add new menus | |
| 30 Previous chapter: |usr_40.txt| Make new commands | |
| 31 Table of contents: |usr_toc.txt| | |
| 32 | |
| 33 ============================================================================== | |
| 129 | 34 *41.1* Introduction *vim-script-intro* *script* |
| 7 | 35 |
| 36 Your first experience with Vim scripts is the vimrc file. Vim reads it when | |
| 37 it starts up and executes the commands. You can set options to values you | |
| 38 prefer. And you can use any colon command in it (commands that start with a | |
| 39 ":"; these are sometimes referred to as Ex commands or command-line commands). | |
| 40 Syntax files are also Vim scripts. As are files that set options for a | |
| 41 specific file type. A complicated macro can be defined by a separate Vim | |
| 42 script file. You can think of other uses yourself. | |
| 43 | |
| 44 Let's start with a simple example: > | |
| 45 | |
| 46 :let i = 1 | |
| 47 :while i < 5 | |
| 48 : echo "count is" i | |
| 161 | 49 : let i += 1 |
| 7 | 50 :endwhile |
| 51 < | |
| 52 Note: | |
| 53 The ":" characters are not really needed here. You only need to use | |
| 54 them when you type a command. In a Vim script file they can be left | |
| 55 out. We will use them here anyway to make clear these are colon | |
| 56 commands and make them stand out from Normal mode commands. | |
| 161 | 57 Note: |
| 58 You can try out the examples by yanking the lines from the text here | |
| 59 and executing them with :@" | |
| 60 | |
| 61 The output of the example code is: | |
| 62 | |
| 63 count is 1 ~ | |
| 64 count is 2 ~ | |
| 65 count is 3 ~ | |
| 66 count is 4 ~ | |
| 67 | |
| 68 In the first line the ":let" command assigns a value to a variable. The | |
| 69 generic form is: > | |
| 7 | 70 |
| 71 :let {variable} = {expression} | |
| 72 | |
| 73 In this case the variable name is "i" and the expression is a simple value, | |
| 74 the number one. | |
| 75 The ":while" command starts a loop. The generic form is: > | |
| 76 | |
| 77 :while {condition} | |
| 78 : {statements} | |
| 79 :endwhile | |
| 80 | |
| 81 The statements until the matching ":endwhile" are executed for as long as the | |
| 82 condition is true. The condition used here is the expression "i < 5". This | |
| 83 is true when the variable i is smaller than five. | |
| 84 Note: | |
| 85 If you happen to write a while loop that keeps on running, you can | |
| 86 interrupt it by pressing CTRL-C (CTRL-Break on MS-Windows). | |
| 161 | 87 |
| 88 The ":echo" command prints its arguments. In this case the string "count is" | |
| 89 and the value of the variable i. Since i is one, this will print: | |
| 90 | |
| 91 count is 1 ~ | |
| 92 | |
| 93 Then there is the ":let i += 1" command. This does the same thing as | |
| 94 ":let i = i + 1". This adds one to the variable i and assigns the new value | |
| 95 to the same variable. | |
| 96 | |
| 97 The example was given to explain the commands, but would you really want to | |
| 112 | 98 make such a loop it can be written much more compact: > |
| 99 | |
| 100 :for i in range(1, 4) | |
| 101 : echo "count is" i | |
| 102 :endfor | |
| 103 | |
| 161 | 104 We won't explain how |:for| and |range()| work until later. Follow the links |
| 105 if you are impatient. | |
| 112 | 106 |
| 7 | 107 |
| 108 THREE KINDS OF NUMBERS | |
| 109 | |
| 110 Numbers can be decimal, hexadecimal or octal. A hexadecimal number starts | |
| 161 | 111 with "0x" or "0X". For example "0x1f" is decimal 31. An octal number starts |
| 112 with a zero. "017" is decimal 15. Careful: don't put a zero before a decimal | |
| 113 number, it will be interpreted as an octal number! | |
| 7 | 114 The ":echo" command always prints decimal numbers. Example: > |
| 115 | |
| 116 :echo 0x7f 036 | |
| 117 < 127 30 ~ | |
| 118 | |
| 119 A number is made negative with a minus sign. This also works for hexadecimal | |
| 161 | 120 and octal numbers. A minus sign is also used for subtraction. Compare this |
| 121 with the previous example: > | |
| 7 | 122 |
| 123 :echo 0x7f -036 | |
| 124 < 97 ~ | |
| 125 | |
| 126 White space in an expression is ignored. However, it's recommended to use it | |
| 127 for separating items, to make the expression easier to read. For example, to | |
| 161 | 128 avoid the confusion with a negative number above, put a space between the |
| 129 minus sign and the following number: > | |
| 7 | 130 |
| 131 :echo 0x7f - 036 | |
| 132 | |
| 133 ============================================================================== | |
| 134 *41.2* Variables | |
| 135 | |
| 136 A variable name consists of ASCII letters, digits and the underscore. It | |
| 137 cannot start with a digit. Valid variable names are: | |
| 138 | |
| 139 counter | |
| 140 _aap3 | |
| 141 very_long_variable_name_with_underscores | |
| 142 FuncLength | |
| 143 LENGTH | |
| 144 | |
| 145 Invalid names are "foo+bar" and "6var". | |
| 146 These variables are global. To see a list of currently defined variables | |
| 147 use this command: > | |
| 148 | |
| 149 :let | |
| 150 | |
| 151 You can use global variables everywhere. This also means that when the | |
| 152 variable "count" is used in one script file, it might also be used in another | |
| 153 file. This leads to confusion at least, and real problems at worst. To avoid | |
| 154 this, you can use a variable local to a script file by prepending "s:". For | |
| 155 example, one script contains this code: > | |
| 156 | |
| 157 :let s:count = 1 | |
| 158 :while s:count < 5 | |
| 159 : source other.vim | |
| 161 | 160 : let s:count += 1 |
| 7 | 161 :endwhile |
| 162 | |
| 163 Since "s:count" is local to this script, you can be sure that sourcing the | |
| 164 "other.vim" script will not change this variable. If "other.vim" also uses an | |
| 165 "s:count" variable, it will be a different copy, local to that script. More | |
| 166 about script-local variables here: |script-variable|. | |
| 167 | |
| 168 There are more kinds of variables, see |internal-variables|. The most often | |
| 169 used ones are: | |
| 170 | |
| 171 b:name variable local to a buffer | |
| 172 w:name variable local to a window | |
| 173 g:name global variable (also in a function) | |
| 174 v:name variable predefined by Vim | |
| 175 | |
| 176 | |
| 177 DELETING VARIABLES | |
| 178 | |
| 179 Variables take up memory and show up in the output of the ":let" command. To | |
| 180 delete a variable use the ":unlet" command. Example: > | |
| 181 | |
| 182 :unlet s:count | |
| 183 | |
| 184 This deletes the script-local variable "s:count" to free up the memory it | |
| 185 uses. If you are not sure if the variable exists, and don't want an error | |
| 186 message when it doesn't, append !: > | |
| 187 | |
| 188 :unlet! s:count | |
| 189 | |
| 190 When a script finishes, the local variables used there will not be | |
| 191 automatically freed. The next time the script executes, it can still use the | |
| 192 old value. Example: > | |
| 193 | |
| 194 :if !exists("s:call_count") | |
| 195 : let s:call_count = 0 | |
| 196 :endif | |
| 197 :let s:call_count = s:call_count + 1 | |
| 198 :echo "called" s:call_count "times" | |
| 199 | |
| 200 The "exists()" function checks if a variable has already been defined. Its | |
| 201 argument is the name of the variable you want to check. Not the variable | |
| 202 itself! If you would do this: > | |
| 203 | |
| 204 :if !exists(s:call_count) | |
| 205 | |
| 206 Then the value of s:call_count will be used as the name of the variable that | |
| 207 exists() checks. That's not what you want. | |
| 208 The exclamation mark ! negates a value. When the value was true, it | |
| 209 becomes false. When it was false, it becomes true. You can read it as "not". | |
| 210 Thus "if !exists()" can be read as "if not exists()". | |
| 161 | 211 What Vim calls true is anything that is not zero. Zero is false. |
| 856 | 212 Note: |
| 161 | 213 Vim automatically converts a string to a number when it is looking for |
| 214 a number. When using a string that doesn't start with a digit the | |
| 215 resulting number is zero. Thus look out for this: > | |
| 216 :if "true" | |
| 217 < The "true" will be interpreted as a zero, thus as false! | |
| 7 | 218 |
| 219 | |
| 220 STRING VARIABLES AND CONSTANTS | |
| 221 | |
| 222 So far only numbers were used for the variable value. Strings can be used as | |
| 161 | 223 well. Numbers and strings are the basic types of variables that Vim supports. |
| 224 The type is dynamic, it is set each time when assigning a value to the | |
| 225 variable with ":let". More about types in |41.8|. | |
| 7 | 226 To assign a string value to a variable, you need to use a string constant. |
| 227 There are two types of these. First the string in double quotes: > | |
| 228 | |
| 229 :let name = "peter" | |
| 230 :echo name | |
| 231 < peter ~ | |
| 232 | |
| 233 If you want to include a double quote inside the string, put a backslash in | |
| 234 front of it: > | |
| 235 | |
| 236 :let name = "\"peter\"" | |
| 237 :echo name | |
| 238 < "peter" ~ | |
| 239 | |
| 240 To avoid the need for a backslash, you can use a string in single quotes: > | |
| 241 | |
| 242 :let name = '"peter"' | |
| 243 :echo name | |
| 244 < "peter" ~ | |
| 245 | |
| 161 | 246 Inside a single-quote string all the characters are as they are. Only the |
| 247 single quote itself is special: you need to use two to get one. A backslash | |
| 248 is taken literally, thus you can't use it to change the meaning of the | |
| 7 | 249 character after it. |
| 250 In double-quote strings it is possible to use special characters. Here are | |
| 251 a few useful ones: | |
| 252 | |
| 253 \t <Tab> | |
| 254 \n <NL>, line break | |
| 255 \r <CR>, <Enter> | |
| 256 \e <Esc> | |
| 257 \b <BS>, backspace | |
| 258 \" " | |
| 259 \\ \, backslash | |
| 260 \<Esc> <Esc> | |
| 261 \<C-W> CTRL-W | |
| 262 | |
| 263 The last two are just examples. The "\<name>" form can be used to include | |
| 264 the special key "name". | |
| 265 See |expr-quote| for the full list of special items in a string. | |
| 266 | |
| 267 ============================================================================== | |
| 268 *41.3* Expressions | |
| 269 | |
| 270 Vim has a rich, yet simple way to handle expressions. You can read the | |
| 271 definition here: |expression-syntax|. Here we will show the most common | |
| 272 items. | |
| 273 The numbers, strings and variables mentioned above are expressions by | |
| 274 themselves. Thus everywhere an expression is expected, you can use a number, | |
| 275 string or variable. Other basic items in an expression are: | |
| 276 | |
| 277 $NAME environment variable | |
| 278 &name option | |
| 279 @r register | |
| 280 | |
| 281 Examples: > | |
| 282 | |
| 283 :echo "The value of 'tabstop' is" &ts | |
| 284 :echo "Your home directory is" $HOME | |
| 285 :if @a > 5 | |
| 286 | |
| 287 The &name form can be used to save an option value, set it to a new value, | |
| 288 do something and restore the old value. Example: > | |
| 289 | |
| 290 :let save_ic = &ic | |
| 291 :set noic | |
| 292 :/The Start/,$delete | |
| 293 :let &ic = save_ic | |
| 294 | |
| 295 This makes sure the "The Start" pattern is used with the 'ignorecase' option | |
| 161 | 296 off. Still, it keeps the value that the user had set. (Another way to do |
| 297 this would be to add "\C" to the pattern, see |/\C|.) | |
| 7 | 298 |
| 299 | |
| 300 MATHEMATICS | |
| 301 | |
| 302 It becomes more interesting if we combine these basic items. Let's start with | |
| 303 mathematics on numbers: | |
| 304 | |
| 305 a + b add | |
| 306 a - b subtract | |
| 307 a * b multiply | |
| 308 a / b divide | |
| 309 a % b modulo | |
| 310 | |
| 311 The usual precedence is used. Example: > | |
| 312 | |
| 313 :echo 10 + 5 * 2 | |
| 314 < 20 ~ | |
| 315 | |
| 316 Grouping is done with braces. No surprises here. Example: > | |
| 317 | |
| 318 :echo (10 + 5) * 2 | |
| 319 < 30 ~ | |
| 320 | |
| 321 Strings can be concatenated with ".". Example: > | |
| 322 | |
| 323 :echo "foo" . "bar" | |
| 324 < foobar ~ | |
| 325 | |
| 326 When the ":echo" command gets multiple arguments, it separates them with a | |
| 327 space. In the example the argument is a single expression, thus no space is | |
| 328 inserted. | |
| 329 | |
| 330 Borrowed from the C language is the conditional expression: | |
| 331 | |
| 332 a ? b : c | |
| 333 | |
| 334 If "a" evaluates to true "b" is used, otherwise "c" is used. Example: > | |
| 335 | |
| 336 :let i = 4 | |
| 337 :echo i > 5 ? "i is big" : "i is small" | |
| 338 < i is small ~ | |
| 339 | |
| 340 The three parts of the constructs are always evaluated first, thus you could | |
| 341 see it work as: | |
| 342 | |
| 343 (a) ? (b) : (c) | |
| 344 | |
| 345 ============================================================================== | |
| 346 *41.4* Conditionals | |
| 347 | |
| 348 The ":if" commands executes the following statements, until the matching | |
| 349 ":endif", only when a condition is met. The generic form is: | |
| 350 | |
| 351 :if {condition} | |
| 352 {statements} | |
| 353 :endif | |
| 354 | |
| 355 Only when the expression {condition} evaluates to true (non-zero) will the | |
| 356 {statements} be executed. These must still be valid commands. If they | |
| 357 contain garbage, Vim won't be able to find the ":endif". | |
| 358 You can also use ":else". The generic form for this is: | |
| 359 | |
| 360 :if {condition} | |
| 361 {statements} | |
| 362 :else | |
| 363 {statements} | |
| 364 :endif | |
| 365 | |
| 366 The second {statements} is only executed if the first one isn't. | |
| 367 Finally, there is ":elseif": | |
| 368 | |
| 369 :if {condition} | |
| 370 {statements} | |
| 371 :elseif {condition} | |
| 372 {statements} | |
| 373 :endif | |
| 374 | |
| 375 This works just like using ":else" and then "if", but without the need for an | |
| 376 extra ":endif". | |
| 377 A useful example for your vimrc file is checking the 'term' option and | |
| 378 doing something depending upon its value: > | |
| 379 | |
| 380 :if &term == "xterm" | |
| 381 : " Do stuff for xterm | |
| 382 :elseif &term == "vt100" | |
| 383 : " Do stuff for a vt100 terminal | |
| 384 :else | |
| 385 : " Do something for other terminals | |
| 386 :endif | |
| 387 | |
| 388 | |
| 389 LOGIC OPERATIONS | |
| 390 | |
| 391 We already used some of them in the examples. These are the most often used | |
| 392 ones: | |
| 393 | |
| 394 a == b equal to | |
| 395 a != b not equal to | |
| 396 a > b greater than | |
| 397 a >= b greater than or equal to | |
| 398 a < b less than | |
| 399 a <= b less than or equal to | |
| 400 | |
| 401 The result is one if the condition is met and zero otherwise. An example: > | |
| 402 | |
| 161 | 403 :if v:version >= 700 |
| 7 | 404 : echo "congratulations" |
| 405 :else | |
| 406 : echo "you are using an old version, upgrade!" | |
| 407 :endif | |
| 408 | |
| 409 Here "v:version" is a variable defined by Vim, which has the value of the Vim | |
| 410 version. 600 is for version 6.0. Version 6.1 has the value 601. This is | |
| 411 very useful to write a script that works with multiple versions of Vim. | |
| 412 |v:version| | |
| 413 | |
| 414 The logic operators work both for numbers and strings. When comparing two | |
| 415 strings, the mathematical difference is used. This compares byte values, | |
| 416 which may not be right for some languages. | |
| 417 When comparing a string with a number, the string is first converted to a | |
| 418 number. This is a bit tricky, because when a string doesn't look like a | |
| 419 number, the number zero is used. Example: > | |
| 420 | |
| 421 :if 0 == "one" | |
| 422 : echo "yes" | |
| 423 :endif | |
| 424 | |
| 425 This will echo "yes", because "one" doesn't look like a number, thus it is | |
| 426 converted to the number zero. | |
| 427 | |
| 428 For strings there are two more items: | |
| 429 | |
| 430 a =~ b matches with | |
| 431 a !~ b does not match with | |
| 432 | |
| 433 The left item "a" is used as a string. The right item "b" is used as a | |
| 434 pattern, like what's used for searching. Example: > | |
| 435 | |
| 436 :if str =~ " " | |
| 437 : echo "str contains a space" | |
| 438 :endif | |
| 439 :if str !~ '\.$' | |
| 440 : echo "str does not end in a full stop" | |
| 441 :endif | |
| 442 | |
| 443 Notice the use of a single-quote string for the pattern. This is useful, | |
| 161 | 444 because backslashes would need to be doubled in a double-quote string and |
| 445 patterns tend to contain many backslashes. | |
| 7 | 446 |
| 447 The 'ignorecase' option is used when comparing strings. When you don't want | |
| 448 that, append "#" to match case and "?" to ignore case. Thus "==?" compares | |
| 449 two strings to be equal while ignoring case. And "!~#" checks if a pattern | |
| 450 doesn't match, also checking the case of letters. For the full table see | |
| 451 |expr-==|. | |
| 452 | |
| 453 | |
| 454 MORE LOOPING | |
| 455 | |
| 456 The ":while" command was already mentioned. Two more statements can be used | |
| 457 in between the ":while" and the ":endwhile": | |
| 458 | |
| 459 :continue Jump back to the start of the while loop; the | |
| 460 loop continues. | |
| 461 :break Jump forward to the ":endwhile"; the loop is | |
| 462 discontinued. | |
| 463 | |
| 464 Example: > | |
| 465 | |
| 466 :while counter < 40 | |
| 467 : call do_something() | |
| 468 : if skip_flag | |
| 469 : continue | |
| 470 : endif | |
| 471 : if finished_flag | |
| 472 : break | |
| 473 : endif | |
| 474 : sleep 50m | |
| 475 :endwhile | |
| 476 | |
| 477 The ":sleep" command makes Vim take a nap. The "50m" specifies fifty | |
| 478 milliseconds. Another example is ":sleep 4", which sleeps for four seconds. | |
| 479 | |
| 161 | 480 Even more looping can be done with the ":for" command, see below in |41.8|. |
| 481 | |
| 7 | 482 ============================================================================== |
| 483 *41.5* Executing an expression | |
| 484 | |
| 485 So far the commands in the script were executed by Vim directly. The | |
| 486 ":execute" command allows executing the result of an expression. This is a | |
| 487 very powerful way to build commands and execute them. | |
| 488 An example is to jump to a tag, which is contained in a variable: > | |
| 489 | |
| 490 :execute "tag " . tag_name | |
| 491 | |
| 492 The "." is used to concatenate the string "tag " with the value of variable | |
| 493 "tag_name". Suppose "tag_name" has the value "get_cmd", then the command that | |
| 494 will be executed is: > | |
| 495 | |
| 496 :tag get_cmd | |
| 497 | |
| 498 The ":execute" command can only execute colon commands. The ":normal" command | |
| 499 executes Normal mode commands. However, its argument is not an expression but | |
| 500 the literal command characters. Example: > | |
| 501 | |
| 502 :normal gg=G | |
| 503 | |
| 504 This jumps to the first line and formats all lines with the "=" operator. | |
| 505 To make ":normal" work with an expression, combine ":execute" with it. | |
| 506 Example: > | |
| 507 | |
| 508 :execute "normal " . normal_commands | |
| 509 | |
| 510 The variable "normal_commands" must contain the Normal mode commands. | |
| 511 Make sure that the argument for ":normal" is a complete command. Otherwise | |
| 512 Vim will run into the end of the argument and abort the command. For example, | |
| 513 if you start Insert mode, you must leave Insert mode as well. This works: > | |
| 514 | |
| 515 :execute "normal Inew text \<Esc>" | |
| 516 | |
| 517 This inserts "new text " in the current line. Notice the use of the special | |
| 518 key "\<Esc>". This avoids having to enter a real <Esc> character in your | |
| 519 script. | |
| 520 | |
| 161 | 521 If you don't want to execute a string but evaluate it to get its expression |
| 522 value, you can use the eval() function: > | |
| 523 | |
| 524 :let optname = "path" | |
| 525 :let optval = eval('&' . optname) | |
| 526 | |
| 527 A "&" character is prepended to "path", thus the argument to eval() is | |
| 528 "&path". The result will then be the value of the 'path' option. | |
| 529 The same thing can be done with: > | |
| 530 :exe 'let optval = &' . optname | |
| 531 | |
| 7 | 532 ============================================================================== |
| 533 *41.6* Using functions | |
| 534 | |
| 535 Vim defines many functions and provides a large amount of functionality that | |
| 536 way. A few examples will be given in this section. You can find the whole | |
| 537 list here: |functions|. | |
| 538 | |
| 539 A function is called with the ":call" command. The parameters are passed in | |
| 540 between braces, separated by commas. Example: > | |
| 541 | |
| 542 :call search("Date: ", "W") | |
| 543 | |
| 544 This calls the search() function, with arguments "Date: " and "W". The | |
| 545 search() function uses its first argument as a search pattern and the second | |
| 546 one as flags. The "W" flag means the search doesn't wrap around the end of | |
| 547 the file. | |
| 548 | |
| 549 A function can be called in an expression. Example: > | |
| 550 | |
| 551 :let line = getline(".") | |
| 552 :let repl = substitute(line, '\a', "*", "g") | |
| 553 :call setline(".", repl) | |
| 554 | |
| 161 | 555 The getline() function obtains a line from the current buffer. Its argument |
| 556 is a specification of the line number. In this case "." is used, which means | |
| 557 the line where the cursor is. | |
| 7 | 558 The substitute() function does something similar to the ":substitute" |
| 559 command. The first argument is the string on which to perform the | |
| 560 substitution. The second argument is the pattern, the third the replacement | |
| 561 string. Finally, the last arguments are the flags. | |
| 562 The setline() function sets the line, specified by the first argument, to a | |
| 563 new string, the second argument. In this example the line under the cursor is | |
| 564 replaced with the result of the substitute(). Thus the effect of the three | |
| 565 statements is equal to: > | |
| 566 | |
| 567 :substitute/\a/*/g | |
| 568 | |
| 569 Using the functions becomes more interesting when you do more work before and | |
| 570 after the substitute() call. | |
| 571 | |
| 572 | |
| 573 FUNCTIONS *function-list* | |
| 574 | |
| 575 There are many functions. We will mention them here, grouped by what they are | |
| 576 used for. You can find an alphabetical list here: |functions|. Use CTRL-] on | |
| 577 the function name to jump to detailed help on it. | |
| 578 | |
|
2301
6f63294a1781
Avoid use of the GTK mail_loop() so that the GtkFileChooser can be used.
Bram Moolenaar <bram@vim.org>
parents:
2207
diff
changeset
|
579 String manipulation: *string-functions* |
| 824 | 580 nr2char() get a character by its ASCII value |
| 7 | 581 char2nr() get ASCII value of a character |
| 1620 | 582 str2nr() convert a string to a Number |
| 583 str2float() convert a string to a Float | |
| 824 | 584 printf() format a string according to % items |
| 7 | 585 escape() escape characters in a string with a '\' |
| 1620 | 586 shellescape() escape a string for use with a shell command |
| 587 fnameescape() escape a file name for use with a Vim command | |
| 824 | 588 tr() translate characters from one set to another |
| 7 | 589 strtrans() translate a string to make it printable |
| 590 tolower() turn a string to lowercase | |
| 591 toupper() turn a string to uppercase | |
| 592 match() position where a pattern matches in a string | |
| 593 matchend() position where a pattern match ends in a string | |
| 594 matchstr() match of a pattern in a string | |
| 824 | 595 matchlist() like matchstr() and also return submatches |
| 7 | 596 stridx() first index of a short string in a long string |
| 597 strridx() last index of a short string in a long string | |
| 598 strlen() length of a string | |
| 599 substitute() substitute a pattern match with a string | |
| 600 submatch() get a specific match in a ":substitute" | |
| 601 strpart() get part of a string | |
| 602 expand() expand special keywords | |
| 603 iconv() convert text from one encoding to another | |
| 824 | 604 byteidx() byte index of a character in a string |
| 605 repeat() repeat a string multiple times | |
| 606 eval() evaluate a string expression | |
| 7 | 607 |
|
2301
6f63294a1781
Avoid use of the GTK mail_loop() so that the GtkFileChooser can be used.
Bram Moolenaar <bram@vim.org>
parents:
2207
diff
changeset
|
608 List manipulation: *list-functions* |
| 112 | 609 get() get an item without error for wrong index |
| 610 len() number of items in a List | |
| 611 empty() check if List is empty | |
| 612 insert() insert an item somewhere in a List | |
| 613 add() append an item to a List | |
| 614 extend() append a List to a List | |
| 615 remove() remove one or more items from a List | |
| 616 copy() make a shallow copy of a List | |
| 617 deepcopy() make a full copy of a List | |
| 618 filter() remove selected items from a List | |
| 619 map() change each List item | |
| 620 sort() sort a List | |
| 621 reverse() reverse the order of a List | |
| 622 split() split a String into a List | |
| 623 join() join List items into a String | |
| 824 | 624 range() return a List with a sequence of numbers |
| 112 | 625 string() String representation of a List |
| 626 call() call a function with List as arguments | |
| 323 | 627 index() index of a value in a List |
| 112 | 628 max() maximum value in a List |
| 629 min() minimum value in a List | |
| 630 count() count number of times a value appears in a List | |
| 824 | 631 repeat() repeat a List multiple times |
| 112 | 632 |
|
2301
6f63294a1781
Avoid use of the GTK mail_loop() so that the GtkFileChooser can be used.
Bram Moolenaar <bram@vim.org>
parents:
2207
diff
changeset
|
633 Dictionary manipulation: *dict-functions* |
| 323 | 634 get() get an entry without an error for a wrong key |
| 112 | 635 len() number of entries in a Dictionary |
| 636 has_key() check whether a key appears in a Dictionary | |
| 637 empty() check if Dictionary is empty | |
| 638 remove() remove an entry from a Dictionary | |
| 639 extend() add entries from one Dictionary to another | |
| 640 filter() remove selected entries from a Dictionary | |
| 641 map() change each Dictionary entry | |
| 642 keys() get List of Dictionary keys | |
| 643 values() get List of Dictionary values | |
| 644 items() get List of Dictionary key-value pairs | |
| 645 copy() make a shallow copy of a Dictionary | |
| 646 deepcopy() make a full copy of a Dictionary | |
| 647 string() String representation of a Dictionary | |
| 648 max() maximum value in a Dictionary | |
| 649 min() minimum value in a Dictionary | |
| 650 count() count number of times a value appears | |
| 651 | |
|
2301
6f63294a1781
Avoid use of the GTK mail_loop() so that the GtkFileChooser can be used.
Bram Moolenaar <bram@vim.org>
parents:
2207
diff
changeset
|
652 Floating point computation: *float-functions* |
| 1620 | 653 float2nr() convert Float to Number |
| 654 abs() absolute value (also works for Number) | |
| 655 round() round off | |
| 656 ceil() round up | |
| 657 floor() round down | |
| 658 trunc() remove value after decimal point | |
| 659 log10() logarithm to base 10 | |
| 660 pow() value of x to the exponent y | |
| 661 sqrt() square root | |
| 662 sin() sine | |
| 663 cos() cosine | |
| 664 atan() arc tangent | |
| 665 | |
|
2301
6f63294a1781
Avoid use of the GTK mail_loop() so that the GtkFileChooser can be used.
Bram Moolenaar <bram@vim.org>
parents:
2207
diff
changeset
|
666 Variables: *var-functions* |
| 824 | 667 type() type of a variable |
| 668 islocked() check if a variable is locked | |
| 669 function() get a Funcref for a function name | |
| 670 getbufvar() get a variable value from a specific buffer | |
| 671 setbufvar() set a variable in a specific buffer | |
| 831 | 672 getwinvar() get a variable from specific window |
|
2207
b17bbfa96fa0
Add the settabvar() and gettabvar() functions.
Bram Moolenaar <bram@vim.org>
parents:
2154
diff
changeset
|
673 gettabvar() get a variable from specific tab page |
| 831 | 674 gettabwinvar() get a variable from specific window & tab page |
| 824 | 675 setwinvar() set a variable in a specific window |
|
2207
b17bbfa96fa0
Add the settabvar() and gettabvar() functions.
Bram Moolenaar <bram@vim.org>
parents:
2154
diff
changeset
|
676 settabvar() set a variable in a specific tab page |
| 831 | 677 settabwinvar() set a variable in a specific window & tab page |
| 824 | 678 garbagecollect() possibly free memory |
| 679 | |
|
2301
6f63294a1781
Avoid use of the GTK mail_loop() so that the GtkFileChooser can be used.
Bram Moolenaar <bram@vim.org>
parents:
2207
diff
changeset
|
680 Cursor and mark position: *cursor-functions* *mark-functions* |
| 7 | 681 col() column number of the cursor or a mark |
| 682 virtcol() screen column of the cursor or a mark | |
| 683 line() line number of the cursor or mark | |
| 684 wincol() window column number of the cursor | |
| 685 winline() window line number of the cursor | |
| 686 cursor() position the cursor at a line/column | |
| 824 | 687 getpos() get position of cursor, mark, etc. |
| 688 setpos() set position of cursor, mark, etc. | |
| 689 byte2line() get line number at a specific byte count | |
| 690 line2byte() byte count at a specific line | |
| 691 diff_filler() get the number of filler lines above a line | |
| 692 | |
|
2301
6f63294a1781
Avoid use of the GTK mail_loop() so that the GtkFileChooser can be used.
Bram Moolenaar <bram@vim.org>
parents:
2207
diff
changeset
|
693 Working with text in the current buffer: *text-functions* |
| 161 | 694 getline() get a line or list of lines from the buffer |
| 7 | 695 setline() replace a line in the buffer |
| 161 | 696 append() append line or list of lines in the buffer |
| 7 | 697 indent() indent of a specific line |
| 698 cindent() indent according to C indenting | |
| 699 lispindent() indent according to Lisp indenting | |
| 700 nextnonblank() find next non-blank line | |
| 701 prevnonblank() find previous non-blank line | |
| 702 search() find a match for a pattern | |
| 667 | 703 searchpos() find a match for a pattern |
| 7 | 704 searchpair() find the other end of a start/skip/end |
| 667 | 705 searchpairpos() find the other end of a start/skip/end |
| 824 | 706 searchdecl() search for the declaration of a name |
| 7 | 707 |
|
2301
6f63294a1781
Avoid use of the GTK mail_loop() so that the GtkFileChooser can be used.
Bram Moolenaar <bram@vim.org>
parents:
2207
diff
changeset
|
708 *system-functions* *file-functions* |
| 7 | 709 System functions and manipulation of files: |
| 710 glob() expand wildcards | |
| 711 globpath() expand wildcards in a number of directories | |
| 824 | 712 findfile() find a file in a list of directories |
| 713 finddir() find a directory in a list of directories | |
| 7 | 714 resolve() find out where a shortcut points to |
| 715 fnamemodify() modify a file name | |
| 824 | 716 pathshorten() shorten directory names in a path |
| 717 simplify() simplify a path without changing its meaning | |
| 7 | 718 executable() check if an executable program exists |
| 719 filereadable() check if a file can be read | |
| 720 filewritable() check if a file can be written to | |
| 824 | 721 getfperm() get the permissions of a file |
| 722 getftype() get the kind of a file | |
| 7 | 723 isdirectory() check if a directory exists |
| 724 getfsize() get the size of a file | |
| 824 | 725 getcwd() get the current working directory |
| 1104 | 726 haslocaldir() check if current window used |:lcd| |
| 7 | 727 tempname() get the name of a temporary file |
| 824 | 728 mkdir() create a new directory |
| 7 | 729 delete() delete a file |
| 730 rename() rename a file | |
| 731 system() get the result of a shell command | |
| 732 hostname() name of the system | |
| 158 | 733 readfile() read a file into a List of lines |
| 734 writefile() write a List of lines into a file | |
| 7 | 735 |
|
2301
6f63294a1781
Avoid use of the GTK mail_loop() so that the GtkFileChooser can be used.
Bram Moolenaar <bram@vim.org>
parents:
2207
diff
changeset
|
736 Date and Time: *date-functions* *time-functions* |
| 824 | 737 getftime() get last modification time of a file |
| 738 localtime() get current time in seconds | |
| 739 strftime() convert time to a string | |
| 740 reltime() get the current or elapsed time accurately | |
| 741 reltimestr() convert reltime() result to a string | |
| 742 | |
|
2301
6f63294a1781
Avoid use of the GTK mail_loop() so that the GtkFileChooser can be used.
Bram Moolenaar <bram@vim.org>
parents:
2207
diff
changeset
|
743 *buffer-functions* *window-functions* *arg-functions* |
| 7 | 744 Buffers, windows and the argument list: |
| 745 argc() number of entries in the argument list | |
| 746 argidx() current position in the argument list | |
| 747 argv() get one entry from the argument list | |
| 748 bufexists() check if a buffer exists | |
| 749 buflisted() check if a buffer exists and is listed | |
| 750 bufloaded() check if a buffer exists and is loaded | |
| 751 bufname() get the name of a specific buffer | |
| 752 bufnr() get the buffer number of a specific buffer | |
| 824 | 753 tabpagebuflist() return List of buffers in a tab page |
| 754 tabpagenr() get the number of a tab page | |
| 755 tabpagewinnr() like winnr() for a specified tab page | |
| 7 | 756 winnr() get the window number for the current window |
| 757 bufwinnr() get the window number of a specific buffer | |
| 758 winbufnr() get the buffer number of a specific window | |
| 434 | 759 getbufline() get a list of lines from the specified buffer |
| 824 | 760 |
|
2301
6f63294a1781
Avoid use of the GTK mail_loop() so that the GtkFileChooser can be used.
Bram Moolenaar <bram@vim.org>
parents:
2207
diff
changeset
|
761 Command line: *command-line-functions* |
| 824 | 762 getcmdline() get the current command line |
| 763 getcmdpos() get position of the cursor in the command line | |
| 764 setcmdpos() set position of the cursor in the command line | |
| 765 getcmdtype() return the current command-line type | |
| 766 | |
|
2301
6f63294a1781
Avoid use of the GTK mail_loop() so that the GtkFileChooser can be used.
Bram Moolenaar <bram@vim.org>
parents:
2207
diff
changeset
|
767 Quickfix and location lists: *quickfix-functions* |
| 824 | 768 getqflist() list of quickfix errors |
| 769 setqflist() modify a quickfix list | |
| 770 getloclist() list of location list items | |
| 771 setloclist() modify a location list | |
| 772 | |
|
2301
6f63294a1781
Avoid use of the GTK mail_loop() so that the GtkFileChooser can be used.
Bram Moolenaar <bram@vim.org>
parents:
2207
diff
changeset
|
773 Insert mode completion: *completion-functions* |
| 824 | 774 complete() set found matches |
| 775 complete_add() add to found matches | |
| 776 complete_check() check if completion should be aborted | |
| 777 pumvisible() check if the popup menu is displayed | |
| 7 | 778 |
|
2301
6f63294a1781
Avoid use of the GTK mail_loop() so that the GtkFileChooser can be used.
Bram Moolenaar <bram@vim.org>
parents:
2207
diff
changeset
|
779 Folding: *folding-functions* |
| 7 | 780 foldclosed() check for a closed fold at a specific line |
| 781 foldclosedend() like foldclosed() but return the last line | |
| 782 foldlevel() check for the fold level at a specific line | |
| 783 foldtext() generate the line displayed for a closed fold | |
| 824 | 784 foldtextresult() get the text displayed for a closed fold |
| 785 | |
|
2301
6f63294a1781
Avoid use of the GTK mail_loop() so that the GtkFileChooser can be used.
Bram Moolenaar <bram@vim.org>
parents:
2207
diff
changeset
|
786 Syntax and highlighting: *syntax-functions* *highlighting-functions* |
| 1326 | 787 clearmatches() clear all matches defined by |matchadd()| and |
| 788 the |:match| commands | |
| 789 getmatches() get all matches defined by |matchadd()| and | |
| 790 the |:match| commands | |
| 7 | 791 hlexists() check if a highlight group exists |
| 792 hlID() get ID of a highlight group | |
| 793 synID() get syntax ID at a specific position | |
| 794 synIDattr() get a specific attribute of a syntax ID | |
| 795 synIDtrans() get translated syntax ID | |
| 2642 | 796 synstack() get list of syntax IDs at a specific position |
| 2662 | 797 synconcealed() get info about concealing |
| 824 | 798 diff_hlID() get highlight ID for diff mode at a position |
| 1326 | 799 matchadd() define a pattern to highlight (a "match") |
| 824 | 800 matcharg() get info about |:match| arguments |
| 1326 | 801 matchdelete() delete a match defined by |matchadd()| or a |
| 802 |:match| command | |
| 803 setmatches() restore a list of matches saved by | |
| 804 |getmatches()| | |
| 824 | 805 |
|
2301
6f63294a1781
Avoid use of the GTK mail_loop() so that the GtkFileChooser can be used.
Bram Moolenaar <bram@vim.org>
parents:
2207
diff
changeset
|
806 Spelling: *spell-functions* |
| 824 | 807 spellbadword() locate badly spelled word at or after cursor |
| 808 spellsuggest() return suggested spelling corrections | |
| 809 soundfold() return the sound-a-like equivalent of a word | |
| 7 | 810 |
|
2301
6f63294a1781
Avoid use of the GTK mail_loop() so that the GtkFileChooser can be used.
Bram Moolenaar <bram@vim.org>
parents:
2207
diff
changeset
|
811 History: *history-functions* |
| 7 | 812 histadd() add an item to a history |
| 813 histdel() delete an item from a history | |
| 814 histget() get an item from a history | |
| 815 histnr() get highest index of a history list | |
| 816 | |
|
2301
6f63294a1781
Avoid use of the GTK mail_loop() so that the GtkFileChooser can be used.
Bram Moolenaar <bram@vim.org>
parents:
2207
diff
changeset
|
817 Interactive: *interactive-functions* |
| 824 | 818 browse() put up a file requester |
| 819 browsedir() put up a directory requester | |
| 7 | 820 confirm() let the user make a choice |
| 821 getchar() get a character from the user | |
| 822 getcharmod() get modifiers for the last typed character | |
| 1620 | 823 feedkeys() put characters in the typeahead queue |
| 7 | 824 input() get a line from the user |
| 824 | 825 inputlist() let the user pick an entry from a list |
| 7 | 826 inputsecret() get a line from the user without showing it |
| 827 inputdialog() get a line from the user in a dialog | |
| 230 | 828 inputsave() save and clear typeahead |
| 7 | 829 inputrestore() restore typeahead |
| 830 | |
|
2301
6f63294a1781
Avoid use of the GTK mail_loop() so that the GtkFileChooser can be used.
Bram Moolenaar <bram@vim.org>
parents:
2207
diff
changeset
|
831 GUI: *gui-functions* |
| 824 | 832 getfontname() get name of current font being used |
| 833 getwinposx() X position of the GUI Vim window | |
| 834 getwinposy() Y position of the GUI Vim window | |
| 835 | |
|
2301
6f63294a1781
Avoid use of the GTK mail_loop() so that the GtkFileChooser can be used.
Bram Moolenaar <bram@vim.org>
parents:
2207
diff
changeset
|
836 Vim server: *server-functions* |
| 7 | 837 serverlist() return the list of server names |
| 838 remote_send() send command characters to a Vim server | |
| 839 remote_expr() evaluate an expression in a Vim server | |
| 840 server2client() send a reply to a client of a Vim server | |
| 841 remote_peek() check if there is a reply from a Vim server | |
| 842 remote_read() read a reply from a Vim server | |
| 843 foreground() move the Vim window to the foreground | |
| 844 remote_foreground() move the Vim server window to the foreground | |
| 845 | |
|
2301
6f63294a1781
Avoid use of the GTK mail_loop() so that the GtkFileChooser can be used.
Bram Moolenaar <bram@vim.org>
parents:
2207
diff
changeset
|
846 Window size and position: *window-size-functions* |
| 824 | 847 winheight() get height of a specific window |
| 848 winwidth() get width of a specific window | |
| 849 winrestcmd() return command to restore window sizes | |
| 850 winsaveview() get view of current window | |
| 851 winrestview() restore saved view of current window | |
| 852 | |
|
2301
6f63294a1781
Avoid use of the GTK mail_loop() so that the GtkFileChooser can be used.
Bram Moolenaar <bram@vim.org>
parents:
2207
diff
changeset
|
853 Various: *various-functions* |
| 7 | 854 mode() get current editing mode |
| 855 visualmode() last visual mode used | |
| 856 hasmapto() check if a mapping exists | |
| 857 mapcheck() check if a matching mapping exists | |
| 858 maparg() get rhs of a mapping | |
| 859 exists() check if a variable, function, etc. exists | |
| 860 has() check if a feature is supported in Vim | |
| 824 | 861 changenr() return number of most recent change |
| 7 | 862 cscope_connection() check if a cscope connection exists |
| 863 did_filetype() check if a FileType autocommand was used | |
| 864 eventhandler() check if invoked by an event handler | |
| 1620 | 865 getpid() get process ID of Vim |
| 824 | 866 |
| 7 | 867 libcall() call a function in an external library |
| 868 libcallnr() idem, returning a number | |
| 824 | 869 |
| 7 | 870 getreg() get contents of a register |
| 871 getregtype() get type of a register | |
| 872 setreg() set contents and type of a register | |
| 824 | 873 |
| 211 | 874 taglist() get list of matching tags |
| 824 | 875 tagfiles() get a list of tags files |
| 7 | 876 |
|
2050
afcf9db31561
updated for version 7.2.336
Bram Moolenaar <bram@zimbu.org>
parents:
1702
diff
changeset
|
877 mzeval() evaluate |MzScheme| expression |
|
afcf9db31561
updated for version 7.2.336
Bram Moolenaar <bram@zimbu.org>
parents:
1702
diff
changeset
|
878 |
| 7 | 879 ============================================================================== |
| 880 *41.7* Defining a function | |
| 881 | |
| 882 Vim enables you to define your own functions. The basic function declaration | |
| 883 begins as follows: > | |
| 884 | |
| 885 :function {name}({var1}, {var2}, ...) | |
| 886 : {body} | |
| 887 :endfunction | |
| 888 < | |
| 889 Note: | |
| 890 Function names must begin with a capital letter. | |
| 891 | |
| 892 Let's define a short function to return the smaller of two numbers. It starts | |
| 893 with this line: > | |
| 894 | |
| 895 :function Min(num1, num2) | |
| 896 | |
| 897 This tells Vim that the function is named "Min" and it takes two arguments: | |
| 898 "num1" and "num2". | |
| 899 The first thing you need to do is to check to see which number is smaller: | |
| 900 > | |
| 901 : if a:num1 < a:num2 | |
| 902 | |
| 903 The special prefix "a:" tells Vim that the variable is a function argument. | |
| 904 Let's assign the variable "smaller" the value of the smallest number: > | |
| 905 | |
| 906 : if a:num1 < a:num2 | |
| 907 : let smaller = a:num1 | |
| 908 : else | |
| 909 : let smaller = a:num2 | |
| 910 : endif | |
| 911 | |
| 912 The variable "smaller" is a local variable. Variables used inside a function | |
| 913 are local unless prefixed by something like "g:", "a:", or "s:". | |
| 914 | |
| 915 Note: | |
| 916 To access a global variable from inside a function you must prepend | |
| 1620 | 917 "g:" to it. Thus "g:today" inside a function is used for the global |
| 918 variable "today", and "today" is another variable, local to the | |
| 7 | 919 function. |
| 920 | |
| 921 You now use the ":return" statement to return the smallest number to the user. | |
| 922 Finally, you end the function: > | |
| 923 | |
| 924 : return smaller | |
| 925 :endfunction | |
| 926 | |
| 927 The complete function definition is as follows: > | |
| 928 | |
| 929 :function Min(num1, num2) | |
| 930 : if a:num1 < a:num2 | |
| 931 : let smaller = a:num1 | |
| 932 : else | |
| 933 : let smaller = a:num2 | |
| 934 : endif | |
| 935 : return smaller | |
| 936 :endfunction | |
| 937 | |
| 161 | 938 For people who like short functions, this does the same thing: > |
| 939 | |
| 940 :function Min(num1, num2) | |
| 941 : if a:num1 < a:num2 | |
| 942 : return a:num1 | |
| 943 : endif | |
| 944 : return a:num2 | |
| 945 :endfunction | |
| 946 | |
| 681 | 947 A user defined function is called in exactly the same way as a built-in |
| 7 | 948 function. Only the name is different. The Min function can be used like |
| 949 this: > | |
| 950 | |
| 951 :echo Min(5, 8) | |
| 952 | |
| 953 Only now will the function be executed and the lines be interpreted by Vim. | |
| 954 If there are mistakes, like using an undefined variable or function, you will | |
| 955 now get an error message. When defining the function these errors are not | |
| 956 detected. | |
| 957 | |
| 958 When a function reaches ":endfunction" or ":return" is used without an | |
| 959 argument, the function returns zero. | |
| 960 | |
| 961 To redefine a function that already exists, use the ! for the ":function" | |
| 962 command: > | |
| 963 | |
| 964 :function! Min(num1, num2, num3) | |
| 965 | |
| 966 | |
| 967 USING A RANGE | |
| 968 | |
| 969 The ":call" command can be given a line range. This can have one of two | |
| 970 meanings. When a function has been defined with the "range" keyword, it will | |
| 971 take care of the line range itself. | |
| 972 The function will be passed the variables "a:firstline" and "a:lastline". | |
| 973 These will have the line numbers from the range the function was called with. | |
| 974 Example: > | |
| 975 | |
| 976 :function Count_words() range | |
| 1620 | 977 : let lnum = a:firstline |
| 978 : let n = 0 | |
| 979 : while lnum <= a:lastline | |
| 980 : let n = n + len(split(getline(lnum))) | |
| 981 : let lnum = lnum + 1 | |
| 7 | 982 : endwhile |
| 1620 | 983 : echo "found " . n . " words" |
| 7 | 984 :endfunction |
| 985 | |
| 986 You can call this function with: > | |
| 987 | |
| 988 :10,30call Count_words() | |
| 989 | |
| 990 It will be executed once and echo the number of words. | |
| 991 The other way to use a line range is by defining a function without the | |
| 992 "range" keyword. The function will be called once for every line in the | |
| 993 range, with the cursor in that line. Example: > | |
| 994 | |
| 995 :function Number() | |
| 996 : echo "line " . line(".") . " contains: " . getline(".") | |
| 997 :endfunction | |
| 998 | |
| 999 If you call this function with: > | |
| 1000 | |
| 1001 :10,15call Number() | |
| 1002 | |
| 1003 The function will be called six times. | |
| 1004 | |
| 1005 | |
| 1006 VARIABLE NUMBER OF ARGUMENTS | |
| 1007 | |
| 1008 Vim enables you to define functions that have a variable number of arguments. | |
| 1009 The following command, for instance, defines a function that must have 1 | |
| 1010 argument (start) and can have up to 20 additional arguments: > | |
| 1011 | |
| 1012 :function Show(start, ...) | |
| 1013 | |
| 1014 The variable "a:1" contains the first optional argument, "a:2" the second, and | |
| 1015 so on. The variable "a:0" contains the number of extra arguments. | |
| 1016 For example: > | |
| 1017 | |
| 1018 :function Show(start, ...) | |
| 1019 : echohl Title | |
| 1020 : echo "Show is " . a:start | |
| 1021 : echohl None | |
| 1022 : let index = 1 | |
| 1023 : while index <= a:0 | |
| 1024 : echo " Arg " . index . " is " . a:{index} | |
| 1025 : let index = index + 1 | |
| 1026 : endwhile | |
| 1027 : echo "" | |
| 1028 :endfunction | |
| 1029 | |
| 1030 This uses the ":echohl" command to specify the highlighting used for the | |
| 1031 following ":echo" command. ":echohl None" stops it again. The ":echon" | |
| 1032 command works like ":echo", but doesn't output a line break. | |
| 1033 | |
| 161 | 1034 You can also use the a:000 variable, it is a List of all the "..." arguments. |
| 1035 See |a:000|. | |
| 1036 | |
| 7 | 1037 |
| 1038 LISTING FUNCTIONS | |
| 1039 | |
| 1040 The ":function" command lists the names and arguments of all user-defined | |
| 1041 functions: > | |
| 1042 | |
| 1043 :function | |
| 1044 < function Show(start, ...) ~ | |
| 1045 function GetVimIndent() ~ | |
| 1046 function SetSyn(name) ~ | |
| 1047 | |
| 1048 To see what a function does, use its name as an argument for ":function": > | |
| 1049 | |
| 1050 :function SetSyn | |
| 1051 < 1 if &syntax == '' ~ | |
| 1052 2 let &syntax = a:name ~ | |
| 1053 3 endif ~ | |
| 1054 endfunction ~ | |
| 1055 | |
| 1056 | |
| 1057 DEBUGGING | |
| 1058 | |
| 1059 The line number is useful for when you get an error message or when debugging. | |
| 1060 See |debug-scripts| about debugging mode. | |
| 1061 You can also set the 'verbose' option to 12 or higher to see all function | |
| 1062 calls. Set it to 15 or higher to see every executed line. | |
| 1063 | |
| 1064 | |
| 1065 DELETING A FUNCTION | |
| 1066 | |
| 1067 To delete the Show() function: > | |
| 1068 | |
| 1069 :delfunction Show | |
| 1070 | |
| 1071 You get an error when the function doesn't exist. | |
| 1072 | |
| 161 | 1073 |
| 1074 FUNCTION REFERENCES | |
| 1075 | |
| 1076 Sometimes it can be useful to have a variable point to one function or | |
| 1077 another. You can do it with the function() function. It turns the name of a | |
| 1078 function into a reference: > | |
| 1079 | |
| 1080 :let result = 0 " or 1 | |
| 1081 :function! Right() | |
| 1082 : return 'Right!' | |
| 1083 :endfunc | |
| 1084 :function! Wrong() | |
| 1085 : return 'Wrong!' | |
| 1086 :endfunc | |
| 1087 : | |
| 1088 :if result == 1 | |
| 1089 : let Afunc = function('Right') | |
| 1090 :else | |
| 1091 : let Afunc = function('Wrong') | |
| 1092 :endif | |
| 1093 :echo call(Afunc, []) | |
| 1094 < Wrong! ~ | |
| 1095 | |
| 1096 Note that the name of a variable that holds a function reference must start | |
| 1097 with a capital. Otherwise it could be confused with the name of a builtin | |
| 1098 function. | |
| 1099 The way to invoke a function that a variable refers to is with the call() | |
| 1100 function. Its first argument is the function reference, the second argument | |
| 1101 is a List with arguments. | |
| 1102 | |
| 1103 Function references are most useful in combination with a Dictionary, as is | |
| 1104 explained in the next section. | |
| 1105 | |
| 7 | 1106 ============================================================================== |
| 161 | 1107 *41.8* Lists and Dictionaries |
| 1108 | |
| 1109 So far we have used the basic types String and Number. Vim also supports two | |
| 1110 composite types: List and Dictionary. | |
| 1111 | |
| 1112 A List is an ordered sequence of things. The things can be any kind of value, | |
| 1113 thus you can make a List of numbers, a List of Lists and even a List of mixed | |
| 1114 items. To create a List with three strings: > | |
| 1115 | |
| 856 | 1116 :let alist = ['aap', 'mies', 'noot'] |
| 161 | 1117 |
| 1118 The List items are enclosed in square brackets and separated by commas. To | |
| 1119 create an empty List: > | |
| 1120 | |
| 856 | 1121 :let alist = [] |
| 161 | 1122 |
| 1123 You can add items to a List with the add() function: > | |
| 1124 | |
| 856 | 1125 :let alist = [] |
| 161 | 1126 :call add(alist, 'foo') |
| 1127 :call add(alist, 'bar') | |
| 1128 :echo alist | |
| 1129 < ['foo', 'bar'] ~ | |
| 1130 | |
| 1131 List concatenation is done with +: > | |
| 1132 | |
| 1133 :echo alist + ['foo', 'bar'] | |
| 1134 < ['foo', 'bar', 'foo', 'bar'] ~ | |
| 1135 | |
| 1136 Or, if you want to extend a List directly: > | |
| 1137 | |
| 856 | 1138 :let alist = ['one'] |
| 161 | 1139 :call extend(alist, ['two', 'three']) |
| 1140 :echo alist | |
| 1141 < ['one', 'two', 'three'] ~ | |
| 1142 | |
| 1143 Notice that using add() will have a different effect: > | |
| 1144 | |
| 856 | 1145 :let alist = ['one'] |
| 161 | 1146 :call add(alist, ['two', 'three']) |
| 1147 :echo alist | |
| 1148 < ['one', ['two', 'three']] ~ | |
| 1149 | |
| 1150 The second argument of add() is added as a single item. | |
| 1151 | |
| 1152 | |
| 1153 FOR LOOP | |
| 1154 | |
| 1155 One of the nice things you can do with a List is iterate over it: > | |
| 1156 | |
| 1157 :let alist = ['one', 'two', 'three'] | |
| 1158 :for n in alist | |
| 1159 : echo n | |
| 1160 :endfor | |
| 1161 < one ~ | |
| 1162 two ~ | |
| 1163 three ~ | |
| 1164 | |
| 1165 This will loop over each element in List "alist", assigning the value to | |
| 1166 variable "n". The generic form of a for loop is: > | |
| 1167 | |
| 1168 :for {varname} in {listexpression} | |
| 1169 : {commands} | |
| 1170 :endfor | |
| 1171 | |
| 1172 To loop a certain number of times you need a List of a specific length. The | |
| 1173 range() function creates one for you: > | |
| 1174 | |
| 1175 :for a in range(3) | |
| 1176 : echo a | |
| 1177 :endfor | |
| 1178 < 0 ~ | |
| 1179 1 ~ | |
| 1180 2 ~ | |
| 1181 | |
| 1182 Notice that the first item of the List that range() produces is zero, thus the | |
| 1183 last item is one less than the length of the list. | |
| 1184 You can also specify the maximum value, the stride and even go backwards: > | |
| 1185 | |
| 1186 :for a in range(8, 4, -2) | |
| 1187 : echo a | |
| 1188 :endfor | |
| 1189 < 8 ~ | |
| 1190 6 ~ | |
| 1191 4 ~ | |
| 1192 | |
| 1193 A more useful example, looping over lines in the buffer: > | |
| 1194 | |
| 856 | 1195 :for line in getline(1, 20) |
| 1196 : if line =~ "Date: " | |
| 1197 : echo matchstr(line, 'Date: \zs.*') | |
| 1198 : endif | |
| 1199 :endfor | |
| 161 | 1200 |
| 1201 This looks into lines 1 to 20 (inclusive) and echoes any date found in there. | |
| 1202 | |
| 1203 | |
| 1204 DICTIONARIES | |
| 1205 | |
| 1206 A Dictionary stores key-value pairs. You can quickly lookup a value if you | |
| 1207 know the key. A Dictionary is created with curly braces: > | |
| 856 | 1208 |
| 161 | 1209 :let uk2nl = {'one': 'een', 'two': 'twee', 'three': 'drie'} |
| 1210 | |
| 164 | 1211 Now you can lookup words by putting the key in square brackets: > |
| 161 | 1212 |
| 1213 :echo uk2nl['two'] | |
| 1214 < twee ~ | |
| 1215 | |
| 1216 The generic form for defining a Dictionary is: > | |
| 1217 | |
| 1218 {<key> : <value>, ...} | |
| 1219 | |
| 1220 An empty Dictionary is one without any keys: > | |
| 1221 | |
| 1222 {} | |
| 1223 | |
| 1224 The possibilities with Dictionaries are numerous. There are various functions | |
| 1225 for them as well. For example, you can obtain a list of the keys and loop | |
| 1226 over them: > | |
| 1227 | |
| 1228 :for key in keys(uk2nl) | |
| 1229 : echo key | |
| 1230 :endfor | |
| 1231 < three ~ | |
| 1232 one ~ | |
| 1233 two ~ | |
| 1234 | |
| 1620 | 1235 You will notice the keys are not ordered. You can sort the list to get a |
| 161 | 1236 specific order: > |
| 1237 | |
| 1238 :for key in sort(keys(uk2nl)) | |
| 1239 : echo key | |
| 1240 :endfor | |
| 1241 < one ~ | |
| 1242 three ~ | |
| 1243 two ~ | |
| 1244 | |
| 1245 But you can never get back the order in which items are defined. For that you | |
| 1246 need to use a List, it stores items in an ordered sequence. | |
| 1247 | |
| 1248 | |
| 1249 DICTIONARY FUNCTIONS | |
| 1250 | |
| 1251 The items in a Dictionary can normally be obtained with an index in square | |
| 1252 brackets: > | |
| 1253 | |
| 1254 :echo uk2nl['one'] | |
| 1255 < een ~ | |
| 1256 | |
| 1257 A method that does the same, but without so many punctuation characters: > | |
| 1258 | |
| 1259 :echo uk2nl.one | |
| 1260 < een ~ | |
| 1261 | |
| 1262 This only works for a key that is made of ASCII letters, digits and the | |
| 1263 underscore. You can also assign a new value this way: > | |
| 1264 | |
| 1265 :let uk2nl.four = 'vier' | |
| 1266 :echo uk2nl | |
| 1267 < {'three': 'drie', 'four': 'vier', 'one': 'een', 'two': 'twee'} ~ | |
| 1268 | |
| 1269 And now for something special: you can directly define a function and store a | |
| 1270 reference to it in the dictionary: > | |
| 1271 | |
| 1272 :function uk2nl.translate(line) dict | |
| 1273 : return join(map(split(a:line), 'get(self, v:val, "???")')) | |
| 1274 :endfunction | |
| 1275 | |
| 1276 Let's first try it out: > | |
| 1277 | |
| 1278 :echo uk2nl.translate('three two five one') | |
| 1279 < drie twee ??? een ~ | |
| 1280 | |
| 1281 The first special thing you notice is the "dict" at the end of the ":function" | |
| 1282 line. This marks the function as being used from a Dictionary. The "self" | |
| 1283 local variable will then refer to that Dictionary. | |
| 1284 Now let's break up the complicated return command: > | |
| 1285 | |
| 1286 split(a:line) | |
| 1287 | |
| 1288 The split() function takes a string, chops it into white separated words | |
| 1289 and returns a list with these words. Thus in the example it returns: > | |
| 1290 | |
| 1291 :echo split('three two five one') | |
| 1292 < ['three', 'two', 'five', 'one'] ~ | |
| 1293 | |
| 1294 This list is the first argument to the map() function. This will go through | |
| 1295 the list, evaluating its second argument with "v:val" set to the value of each | |
| 1296 item. This is a shortcut to using a for loop. This command: > | |
| 1297 | |
| 1298 :let alist = map(split(a:line), 'get(self, v:val, "???")') | |
| 1299 | |
| 1300 Is equivalent to: > | |
| 1301 | |
| 1302 :let alist = split(a:line) | |
| 1303 :for idx in range(len(alist)) | |
| 1304 : let alist[idx] = get(self, alist[idx], "???") | |
| 1305 :endfor | |
| 1306 | |
| 1307 The get() function checks if a key is present in a Dictionary. If it is, then | |
| 1308 the value is retrieved. If it isn't, then the default value is returned, in | |
| 164 | 1309 the example it's '???'. This is a convenient way to handle situations where a |
| 161 | 1310 key may not be present and you don't want an error message. |
| 1311 | |
| 1312 The join() function does the opposite of split(): it joins together a list of | |
| 1313 words, putting a space in between. | |
| 1314 This combination of split(), map() and join() is a nice way to filter a line | |
| 1315 of words in a very compact way. | |
| 1316 | |
| 1317 | |
| 1318 OBJECT ORIENTED PROGRAMMING | |
| 1319 | |
| 1320 Now that you can put both values and functions in a Dictionary, you can | |
| 1321 actually use a Dictionary like an object. | |
| 1322 Above we used a Dictionary for translating Dutch to English. We might want | |
| 1323 to do the same for other languages. Let's first make an object (aka | |
| 1324 Dictionary) that has the translate function, but no words to translate: > | |
| 1325 | |
| 1326 :let transdict = {} | |
| 1327 :function transdict.translate(line) dict | |
| 1328 : return join(map(split(a:line), 'get(self.words, v:val, "???")')) | |
| 1329 :endfunction | |
| 1330 | |
| 1331 It's slightly different from the function above, using 'self.words' to lookup | |
| 1332 word translations. But we don't have a self.words. Thus you could call this | |
| 1333 an abstract class. | |
| 1334 | |
| 1335 Now we can instantiate a Dutch translation object: > | |
| 1336 | |
| 1337 :let uk2nl = copy(transdict) | |
| 1338 :let uk2nl.words = {'one': 'een', 'two': 'twee', 'three': 'drie'} | |
| 1339 :echo uk2nl.translate('three one') | |
| 1340 < drie een ~ | |
| 1341 | |
| 1342 And a German translator: > | |
| 1343 | |
| 1344 :let uk2de = copy(transdict) | |
| 1345 :let uk2de.words = {'one': 'ein', 'two': 'zwei', 'three': 'drei'} | |
| 1346 :echo uk2de.translate('three one') | |
| 1347 < drei ein ~ | |
| 1348 | |
| 1349 You see that the copy() function is used to make a copy of the "transdict" | |
| 1350 Dictionary and then the copy is changed to add the words. The original | |
| 1351 remains the same, of course. | |
| 1352 | |
| 1353 Now you can go one step further, and use your preferred translator: > | |
| 1354 | |
| 1355 :if $LANG =~ "de" | |
| 1356 : let trans = uk2de | |
| 1357 :else | |
| 1358 : let trans = uk2nl | |
| 1359 :endif | |
| 1360 :echo trans.translate('one two three') | |
| 1361 < een twee drie ~ | |
| 1362 | |
| 1363 Here "trans" refers to one of the two objects (Dictionaries). No copy is | |
| 1364 made. More about List and Dictionary identity can be found at |list-identity| | |
| 1365 and |dict-identity|. | |
| 1366 | |
| 1367 Now you might use a language that isn't supported. You can overrule the | |
| 1368 translate() function to do nothing: > | |
| 1369 | |
| 1370 :let uk2uk = copy(transdict) | |
| 1371 :function! uk2uk.translate(line) | |
| 1372 : return a:line | |
| 1373 :endfunction | |
| 1374 :echo uk2uk.translate('three one wladiwostok') | |
| 1375 < three one wladiwostok ~ | |
| 1376 | |
| 1377 Notice that a ! was used to overwrite the existing function reference. Now | |
| 1378 use "uk2uk" when no recognized language is found: > | |
| 1379 | |
| 1380 :if $LANG =~ "de" | |
| 1381 : let trans = uk2de | |
| 1382 :elseif $LANG =~ "nl" | |
| 1383 : let trans = uk2nl | |
| 1384 :else | |
| 1385 : let trans = uk2uk | |
| 1386 :endif | |
| 1387 :echo trans.translate('one two three') | |
| 1388 < one two three ~ | |
| 1389 | |
| 1390 For further reading see |Lists| and |Dictionaries|. | |
| 1391 | |
| 1392 ============================================================================== | |
| 1393 *41.9* Exceptions | |
| 7 | 1394 |
| 1395 Let's start with an example: > | |
| 1396 | |
| 1397 :try | |
| 1398 : read ~/templates/pascal.tmpl | |
| 1399 :catch /E484:/ | |
| 1400 : echo "Sorry, the Pascal template file cannot be found." | |
| 1401 :endtry | |
| 1402 | |
| 1403 The ":read" command will fail if the file does not exist. Instead of | |
| 1404 generating an error message, this code catches the error and gives the user a | |
| 1405 nice message instead. | |
| 1406 | |
| 1407 For the commands in between ":try" and ":endtry" errors are turned into | |
| 1408 exceptions. An exception is a string. In the case of an error the string | |
| 1409 contains the error message. And every error message has a number. In this | |
| 1410 case, the error we catch contains "E484:". This number is guaranteed to stay | |
| 1411 the same (the text may change, e.g., it may be translated). | |
| 1412 | |
| 1413 When the ":read" command causes another error, the pattern "E484:" will not | |
| 1414 match in it. Thus this exception will not be caught and result in the usual | |
| 1415 error message. | |
| 1416 | |
| 1417 You might be tempted to do this: > | |
| 1418 | |
| 1419 :try | |
| 1420 : read ~/templates/pascal.tmpl | |
| 1421 :catch | |
| 1422 : echo "Sorry, the Pascal template file cannot be found." | |
| 1423 :endtry | |
| 1424 | |
| 1425 This means all errors are caught. But then you will not see errors that are | |
| 1426 useful, such as "E21: Cannot make changes, 'modifiable' is off". | |
| 1427 | |
| 1428 Another useful mechanism is the ":finally" command: > | |
| 1429 | |
| 1430 :let tmp = tempname() | |
| 1431 :try | |
| 1432 : exe ".,$write " . tmp | |
| 1433 : exe "!filter " . tmp | |
| 1434 : .,$delete | |
| 1435 : exe "$read " . tmp | |
| 1436 :finally | |
| 1437 : call delete(tmp) | |
| 1438 :endtry | |
| 1439 | |
| 1440 This filters the lines from the cursor until the end of the file through the | |
| 1441 "filter" command, which takes a file name argument. No matter if the | |
| 1442 filtering works, something goes wrong in between ":try" and ":finally" or the | |
| 1443 user cancels the filtering by pressing CTRL-C, the "call delete(tmp)" is | |
| 1444 always executed. This makes sure you don't leave the temporary file behind. | |
| 1445 | |
| 1446 More information about exception handling can be found in the reference | |
| 1447 manual: |exception-handling|. | |
| 1448 | |
| 1449 ============================================================================== | |
| 161 | 1450 *41.10* Various remarks |
| 7 | 1451 |
| 1452 Here is a summary of items that apply to Vim scripts. They are also mentioned | |
| 1453 elsewhere, but form a nice checklist. | |
| 1454 | |
| 1455 The end-of-line character depends on the system. For Unix a single <NL> | |
| 1456 character is used. For MS-DOS, Windows, OS/2 and the like, <CR><LF> is used. | |
| 1457 This is important when using mappings that end in a <CR>. See |:source_crnl|. | |
| 1458 | |
| 1459 | |
| 1460 WHITE SPACE | |
| 1461 | |
| 1462 Blank lines are allowed and ignored. | |
| 1463 | |
| 1464 Leading whitespace characters (blanks and TABs) are always ignored. The | |
| 1465 whitespaces between parameters (e.g. between the 'set' and the 'cpoptions' in | |
| 1466 the example below) are reduced to one blank character and plays the role of a | |
| 1467 separator, the whitespaces after the last (visible) character may or may not | |
| 1468 be ignored depending on the situation, see below. | |
| 1469 | |
| 1470 For a ":set" command involving the "=" (equal) sign, such as in: > | |
| 1471 | |
| 1472 :set cpoptions =aABceFst | |
| 1473 | |
| 1474 the whitespace immediately before the "=" sign is ignored. But there can be | |
| 1475 no whitespace after the "=" sign! | |
| 1476 | |
| 1477 To include a whitespace character in the value of an option, it must be | |
| 1478 escaped by a "\" (backslash) as in the following example: > | |
| 1479 | |
| 1480 :set tags=my\ nice\ file | |
| 1481 | |
| 1482 The same example written as > | |
| 1483 | |
| 1484 :set tags=my nice file | |
| 1485 | |
| 1486 will issue an error, because it is interpreted as: > | |
| 1487 | |
| 1488 :set tags=my | |
| 1489 :set nice | |
| 1490 :set file | |
| 1491 | |
| 1492 | |
| 1493 COMMENTS | |
| 1494 | |
| 1495 The character " (the double quote mark) starts a comment. Everything after | |
| 1496 and including this character until the end-of-line is considered a comment and | |
| 1497 is ignored, except for commands that don't consider comments, as shown in | |
| 1498 examples below. A comment can start on any character position on the line. | |
| 1499 | |
| 1500 There is a little "catch" with comments for some commands. Examples: > | |
| 1501 | |
| 1502 :abbrev dev development " shorthand | |
| 1503 :map <F3> o#include " insert include | |
| 1504 :execute cmd " do it | |
| 1505 :!ls *.c " list C files | |
| 1506 | |
| 1507 The abbreviation 'dev' will be expanded to 'development " shorthand'. The | |
| 1508 mapping of <F3> will actually be the whole line after the 'o# ....' including | |
| 1509 the '" insert include'. The "execute" command will give an error. The "!" | |
| 1510 command will send everything after it to the shell, causing an error for an | |
| 1511 unmatched '"' character. | |
| 1512 There can be no comment after ":map", ":abbreviate", ":execute" and "!" | |
| 1513 commands (there are a few more commands with this restriction). For the | |
| 1514 ":map", ":abbreviate" and ":execute" commands there is a trick: > | |
| 1515 | |
| 1516 :abbrev dev development|" shorthand | |
| 1517 :map <F3> o#include|" insert include | |
| 1518 :execute cmd |" do it | |
| 1519 | |
| 1520 With the '|' character the command is separated from the next one. And that | |
| 1146 | 1521 next command is only a comment. For the last command you need to do two |
| 1522 things: |:execute| and use '|': > | |
| 1523 :exe '!ls *.c' |" list C files | |
| 7 | 1524 |
| 1525 Notice that there is no white space before the '|' in the abbreviation and | |
| 1526 mapping. For these commands, any character until the end-of-line or '|' is | |
| 1527 included. As a consequence of this behavior, you don't always see that | |
| 1528 trailing whitespace is included: > | |
| 1529 | |
| 1530 :map <F4> o#include | |
| 1531 | |
| 1146 | 1532 To spot these problems, you can set the 'list' option when editing vimrc |
| 7 | 1533 files. |
| 1534 | |
| 1146 | 1535 For Unix there is one special way to comment a line, that allows making a Vim |
| 1536 script executable: > | |
| 1537 #!/usr/bin/env vim -S | |
| 1538 echo "this is a Vim script" | |
| 1539 quit | |
| 1540 | |
| 1541 The "#" command by itself lists a line with the line number. Adding an | |
| 1542 exclamation mark changes it into doing nothing, so that you can add the shell | |
| 1543 command to execute the rest of the file. |:#!| |-S| | |
| 1544 | |
| 7 | 1545 |
| 1546 PITFALLS | |
| 1547 | |
| 1548 Even bigger problem arises in the following example: > | |
| 1549 | |
| 1550 :map ,ab o#include | |
| 1551 :unmap ,ab | |
| 1552 | |
| 1553 Here the unmap command will not work, because it tries to unmap ",ab ". This | |
| 1554 does not exist as a mapped sequence. An error will be issued, which is very | |
| 1555 hard to identify, because the ending whitespace character in ":unmap ,ab " is | |
| 1556 not visible. | |
| 1557 | |
| 1558 And this is the same as what happens when one uses a comment after an 'unmap' | |
| 1559 command: > | |
| 1560 | |
| 1561 :unmap ,ab " comment | |
| 1562 | |
| 1563 Here the comment part will be ignored. However, Vim will try to unmap | |
| 1564 ',ab ', which does not exist. Rewrite it as: > | |
| 1565 | |
| 1566 :unmap ,ab| " comment | |
| 1567 | |
| 1568 | |
| 1569 RESTORING THE VIEW | |
| 1570 | |
| 1571 Sometimes you want to make a change and go back to where cursor was. | |
| 1572 Restoring the relative position would also be nice, so that the same line | |
| 1573 appears at the top of the window. | |
| 1574 This example yanks the current line, puts it above the first line in the | |
| 1575 file and then restores the view: > | |
| 1576 | |
| 1577 map ,p ma"aYHmbgg"aP`bzt`a | |
| 1578 | |
| 1579 What this does: > | |
| 1580 ma"aYHmbgg"aP`bzt`a | |
| 1581 < ma set mark a at cursor position | |
| 1582 "aY yank current line into register a | |
| 1583 Hmb go to top line in window and set mark b there | |
| 1584 gg go to first line in file | |
| 1585 "aP put the yanked line above it | |
| 1586 `b go back to top line in display | |
| 1587 zt position the text in the window as before | |
| 1588 `a go back to saved cursor position | |
| 1589 | |
| 1590 | |
| 1591 PACKAGING | |
| 1592 | |
| 1593 To avoid your function names to interfere with functions that you get from | |
| 1594 others, use this scheme: | |
| 1595 - Prepend a unique string before each function name. I often use an | |
| 1596 abbreviation. For example, "OW_" is used for the option window functions. | |
| 1597 - Put the definition of your functions together in a file. Set a global | |
| 1598 variable to indicate that the functions have been loaded. When sourcing the | |
| 1599 file again, first unload the functions. | |
| 1600 Example: > | |
| 1601 | |
| 1602 " This is the XXX package | |
| 1603 | |
| 1604 if exists("XXX_loaded") | |
| 1605 delfun XXX_one | |
| 1606 delfun XXX_two | |
| 1607 endif | |
| 1608 | |
| 1609 function XXX_one(a) | |
| 1610 ... body of function ... | |
| 1611 endfun | |
| 1612 | |
| 1613 function XXX_two(b) | |
| 1614 ... body of function ... | |
| 1615 endfun | |
| 1616 | |
| 1617 let XXX_loaded = 1 | |
| 1618 | |
| 1619 ============================================================================== | |
| 161 | 1620 *41.11* Writing a plugin *write-plugin* |
| 7 | 1621 |
| 1622 You can write a Vim script in such a way that many people can use it. This is | |
| 1623 called a plugin. Vim users can drop your script in their plugin directory and | |
| 1624 use its features right away |add-plugin|. | |
| 1625 | |
| 1626 There are actually two types of plugins: | |
| 1627 | |
| 1628 global plugins: For all types of files. | |
| 1629 filetype plugins: Only for files of a specific type. | |
| 1630 | |
| 1631 In this section the first type is explained. Most items are also relevant for | |
| 1632 writing filetype plugins. The specifics for filetype plugins are in the next | |
| 1633 section |write-filetype-plugin|. | |
| 1634 | |
| 1635 | |
| 1636 NAME | |
| 1637 | |
| 1638 First of all you must choose a name for your plugin. The features provided | |
| 1639 by the plugin should be clear from its name. And it should be unlikely that | |
| 1640 someone else writes a plugin with the same name but which does something | |
| 1641 different. And please limit the name to 8 characters, to avoid problems on | |
| 1642 old Windows systems. | |
| 1643 | |
| 1644 A script that corrects typing mistakes could be called "typecorr.vim". We | |
| 1645 will use it here as an example. | |
| 1646 | |
| 1647 For the plugin to work for everybody, it should follow a few guidelines. This | |
| 1648 will be explained step-by-step. The complete example plugin is at the end. | |
| 1649 | |
| 1650 | |
| 1651 BODY | |
| 1652 | |
| 1653 Let's start with the body of the plugin, the lines that do the actual work: > | |
| 1654 | |
| 1655 14 iabbrev teh the | |
| 1656 15 iabbrev otehr other | |
| 1657 16 iabbrev wnat want | |
| 1658 17 iabbrev synchronisation | |
| 1659 18 \ synchronization | |
| 1660 19 let s:count = 4 | |
| 1661 | |
| 1662 The actual list should be much longer, of course. | |
| 1663 | |
| 1664 The line numbers have only been added to explain a few things, don't put them | |
| 1665 in your plugin file! | |
| 1666 | |
| 1667 | |
| 1668 HEADER | |
| 1669 | |
| 1670 You will probably add new corrections to the plugin and soon have several | |
| 1671 versions laying around. And when distributing this file, people will want to | |
| 1672 know who wrote this wonderful plugin and where they can send remarks. | |
| 1673 Therefore, put a header at the top of your plugin: > | |
| 1674 | |
| 1675 1 " Vim global plugin for correcting typing mistakes | |
| 1676 2 " Last Change: 2000 Oct 15 | |
| 1677 3 " Maintainer: Bram Moolenaar <Bram@vim.org> | |
| 1678 | |
| 1679 About copyright and licensing: Since plugins are very useful and it's hardly | |
| 1680 worth restricting their distribution, please consider making your plugin | |
| 1681 either public domain or use the Vim |license|. A short note about this near | |
| 1682 the top of the plugin should be sufficient. Example: > | |
| 1683 | |
| 1684 4 " License: This file is placed in the public domain. | |
| 1685 | |
| 1686 | |
| 1687 LINE CONTINUATION, AVOIDING SIDE EFFECTS *use-cpo-save* | |
| 1688 | |
| 1689 In line 18 above, the line-continuation mechanism is used |line-continuation|. | |
| 1690 Users with 'compatible' set will run into trouble here, they will get an error | |
| 1691 message. We can't just reset 'compatible', because that has a lot of side | |
| 1692 effects. To avoid this, we will set the 'cpoptions' option to its Vim default | |
| 1693 value and restore it later. That will allow the use of line-continuation and | |
| 1694 make the script work for most people. It is done like this: > | |
| 1695 | |
| 1696 11 let s:save_cpo = &cpo | |
| 1697 12 set cpo&vim | |
| 1698 .. | |
| 1699 42 let &cpo = s:save_cpo | |
| 1700 | |
| 1701 We first store the old value of 'cpoptions' in the s:save_cpo variable. At | |
| 1702 the end of the plugin this value is restored. | |
| 1703 | |
| 1704 Notice that a script-local variable is used |s:var|. A global variable could | |
| 1705 already be in use for something else. Always use script-local variables for | |
| 1706 things that are only used in the script. | |
| 1707 | |
| 1708 | |
| 1709 NOT LOADING | |
| 1710 | |
| 1711 It's possible that a user doesn't always want to load this plugin. Or the | |
| 1712 system administrator has dropped it in the system-wide plugin directory, but a | |
| 1713 user has his own plugin he wants to use. Then the user must have a chance to | |
| 1714 disable loading this specific plugin. This will make it possible: > | |
| 1715 | |
|
2325
f177a6431514
Better implementation of creating the Color Scheme menu. (Juergen Kraemer)
Bram Moolenaar <bram@vim.org>
parents:
2301
diff
changeset
|
1716 6 if exists("g:loaded_typecorr") |
| 7 | 1717 7 finish |
| 1718 8 endif | |
|
2325
f177a6431514
Better implementation of creating the Color Scheme menu. (Juergen Kraemer)
Bram Moolenaar <bram@vim.org>
parents:
2301
diff
changeset
|
1719 9 let g:loaded_typecorr = 1 |
| 7 | 1720 |
| 1721 This also avoids that when the script is loaded twice it would cause error | |
| 1722 messages for redefining functions and cause trouble for autocommands that are | |
| 1723 added twice. | |
| 1724 | |
|
2325
f177a6431514
Better implementation of creating the Color Scheme menu. (Juergen Kraemer)
Bram Moolenaar <bram@vim.org>
parents:
2301
diff
changeset
|
1725 The name is recommended to start with "loaded_" and then the file name of the |
|
f177a6431514
Better implementation of creating the Color Scheme menu. (Juergen Kraemer)
Bram Moolenaar <bram@vim.org>
parents:
2301
diff
changeset
|
1726 plugin, literally. The "g:" is prepended just to avoid mistakes when using |
|
f177a6431514
Better implementation of creating the Color Scheme menu. (Juergen Kraemer)
Bram Moolenaar <bram@vim.org>
parents:
2301
diff
changeset
|
1727 the variable in a function (without "g:" it would be a variable local to the |
|
f177a6431514
Better implementation of creating the Color Scheme menu. (Juergen Kraemer)
Bram Moolenaar <bram@vim.org>
parents:
2301
diff
changeset
|
1728 function). |
|
f177a6431514
Better implementation of creating the Color Scheme menu. (Juergen Kraemer)
Bram Moolenaar <bram@vim.org>
parents:
2301
diff
changeset
|
1729 |
|
f177a6431514
Better implementation of creating the Color Scheme menu. (Juergen Kraemer)
Bram Moolenaar <bram@vim.org>
parents:
2301
diff
changeset
|
1730 Using "finish" stops Vim from reading the rest of the file, it's much quicker |
|
f177a6431514
Better implementation of creating the Color Scheme menu. (Juergen Kraemer)
Bram Moolenaar <bram@vim.org>
parents:
2301
diff
changeset
|
1731 than using if-endif around the whole file. |
|
f177a6431514
Better implementation of creating the Color Scheme menu. (Juergen Kraemer)
Bram Moolenaar <bram@vim.org>
parents:
2301
diff
changeset
|
1732 |
| 7 | 1733 |
| 1734 MAPPING | |
| 1735 | |
| 1736 Now let's make the plugin more interesting: We will add a mapping that adds a | |
| 1737 correction for the word under the cursor. We could just pick a key sequence | |
| 1738 for this mapping, but the user might already use it for something else. To | |
| 1739 allow the user to define which keys a mapping in a plugin uses, the <Leader> | |
| 1740 item can be used: > | |
| 1741 | |
| 1742 22 map <unique> <Leader>a <Plug>TypecorrAdd | |
| 1743 | |
| 1744 The "<Plug>TypecorrAdd" thing will do the work, more about that further on. | |
| 1745 | |
| 1746 The user can set the "mapleader" variable to the key sequence that he wants | |
| 1747 this mapping to start with. Thus if the user has done: > | |
| 1748 | |
| 1749 let mapleader = "_" | |
| 1750 | |
| 1751 the mapping will define "_a". If the user didn't do this, the default value | |
| 1752 will be used, which is a backslash. Then a map for "\a" will be defined. | |
| 1753 | |
| 1754 Note that <unique> is used, this will cause an error message if the mapping | |
| 1755 already happened to exist. |:map-<unique>| | |
| 1756 | |
| 1757 But what if the user wants to define his own key sequence? We can allow that | |
| 1758 with this mechanism: > | |
| 1759 | |
| 1760 21 if !hasmapto('<Plug>TypecorrAdd') | |
| 1761 22 map <unique> <Leader>a <Plug>TypecorrAdd | |
| 1762 23 endif | |
| 1763 | |
| 1764 This checks if a mapping to "<Plug>TypecorrAdd" already exists, and only | |
| 1765 defines the mapping from "<Leader>a" if it doesn't. The user then has a | |
| 1766 chance of putting this in his vimrc file: > | |
| 1767 | |
| 1768 map ,c <Plug>TypecorrAdd | |
| 1769 | |
| 1770 Then the mapped key sequence will be ",c" instead of "_a" or "\a". | |
| 1771 | |
| 1772 | |
| 1773 PIECES | |
| 1774 | |
| 1775 If a script gets longer, you often want to break up the work in pieces. You | |
| 1776 can use functions or mappings for this. But you don't want these functions | |
| 1777 and mappings to interfere with the ones from other scripts. For example, you | |
| 1778 could define a function Add(), but another script could try to define the same | |
| 1779 function. To avoid this, we define the function local to the script by | |
| 1780 prepending it with "s:". | |
| 1781 | |
| 1782 We will define a function that adds a new typing correction: > | |
| 1783 | |
| 1784 30 function s:Add(from, correct) | |
| 1785 31 let to = input("type the correction for " . a:from . ": ") | |
| 1786 32 exe ":iabbrev " . a:from . " " . to | |
| 1787 .. | |
| 1788 36 endfunction | |
| 1789 | |
| 1790 Now we can call the function s:Add() from within this script. If another | |
| 1791 script also defines s:Add(), it will be local to that script and can only | |
| 1792 be called from the script it was defined in. There can also be a global Add() | |
| 1793 function (without the "s:"), which is again another function. | |
| 1794 | |
| 1795 <SID> can be used with mappings. It generates a script ID, which identifies | |
| 1796 the current script. In our typing correction plugin we use it like this: > | |
| 1797 | |
| 1798 24 noremap <unique> <script> <Plug>TypecorrAdd <SID>Add | |
| 1799 .. | |
| 1800 28 noremap <SID>Add :call <SID>Add(expand("<cword>"), 1)<CR> | |
| 1801 | |
| 1802 Thus when a user types "\a", this sequence is invoked: > | |
| 1803 | |
| 1804 \a -> <Plug>TypecorrAdd -> <SID>Add -> :call <SID>Add() | |
| 1805 | |
| 1806 If another script would also map <SID>Add, it would get another script ID and | |
| 1807 thus define another mapping. | |
| 1808 | |
| 1809 Note that instead of s:Add() we use <SID>Add() here. That is because the | |
| 1810 mapping is typed by the user, thus outside of the script. The <SID> is | |
| 1811 translated to the script ID, so that Vim knows in which script to look for | |
| 1812 the Add() function. | |
| 1813 | |
| 1814 This is a bit complicated, but it's required for the plugin to work together | |
| 1815 with other plugins. The basic rule is that you use <SID>Add() in mappings and | |
| 1816 s:Add() in other places (the script itself, autocommands, user commands). | |
| 1817 | |
| 1818 We can also add a menu entry to do the same as the mapping: > | |
| 1819 | |
| 1820 26 noremenu <script> Plugin.Add\ Correction <SID>Add | |
| 1821 | |
| 1822 The "Plugin" menu is recommended for adding menu items for plugins. In this | |
| 1823 case only one item is used. When adding more items, creating a submenu is | |
| 1824 recommended. For example, "Plugin.CVS" could be used for a plugin that offers | |
| 1825 CVS operations "Plugin.CVS.checkin", "Plugin.CVS.checkout", etc. | |
| 1826 | |
| 1827 Note that in line 28 ":noremap" is used to avoid that any other mappings cause | |
| 1828 trouble. Someone may have remapped ":call", for example. In line 24 we also | |
| 1829 use ":noremap", but we do want "<SID>Add" to be remapped. This is why | |
| 1830 "<script>" is used here. This only allows mappings which are local to the | |
| 1831 script. |:map-<script>| The same is done in line 26 for ":noremenu". | |
| 1832 |:menu-<script>| | |
| 1833 | |
| 1834 | |
| 1835 <SID> AND <Plug> *using-<Plug>* | |
| 1836 | |
| 1837 Both <SID> and <Plug> are used to avoid that mappings of typed keys interfere | |
| 1838 with mappings that are only to be used from other mappings. Note the | |
| 1839 difference between using <SID> and <Plug>: | |
| 1840 | |
| 1841 <Plug> is visible outside of the script. It is used for mappings which the | |
| 1842 user might want to map a key sequence to. <Plug> is a special code | |
| 1843 that a typed key will never produce. | |
| 1844 To make it very unlikely that other plugins use the same sequence of | |
| 1845 characters, use this structure: <Plug> scriptname mapname | |
| 1846 In our example the scriptname is "Typecorr" and the mapname is "Add". | |
| 1847 This results in "<Plug>TypecorrAdd". Only the first character of | |
| 1848 scriptname and mapname is uppercase, so that we can see where mapname | |
| 1849 starts. | |
| 1850 | |
| 1851 <SID> is the script ID, a unique identifier for a script. | |
| 1852 Internally Vim translates <SID> to "<SNR>123_", where "123" can be any | |
| 1853 number. Thus a function "<SID>Add()" will have a name "<SNR>11_Add()" | |
| 1854 in one script, and "<SNR>22_Add()" in another. You can see this if | |
| 1855 you use the ":function" command to get a list of functions. The | |
| 1856 translation of <SID> in mappings is exactly the same, that's how you | |
| 1857 can call a script-local function from a mapping. | |
| 1858 | |
| 1859 | |
| 1860 USER COMMAND | |
| 1861 | |
| 1862 Now let's add a user command to add a correction: > | |
| 1863 | |
| 1864 38 if !exists(":Correct") | |
| 1865 39 command -nargs=1 Correct :call s:Add(<q-args>, 0) | |
| 1866 40 endif | |
| 1867 | |
| 1868 The user command is defined only if no command with the same name already | |
| 1869 exists. Otherwise we would get an error here. Overriding the existing user | |
| 1870 command with ":command!" is not a good idea, this would probably make the user | |
| 1871 wonder why the command he defined himself doesn't work. |:command| | |
| 1872 | |
| 1873 | |
| 1874 SCRIPT VARIABLES | |
| 1875 | |
| 1876 When a variable starts with "s:" it is a script variable. It can only be used | |
| 1877 inside a script. Outside the script it's not visible. This avoids trouble | |
| 1878 with using the same variable name in different scripts. The variables will be | |
| 1879 kept as long as Vim is running. And the same variables are used when sourcing | |
| 1880 the same script again. |s:var| | |
| 1881 | |
| 1882 The fun is that these variables can also be used in functions, autocommands | |
| 1883 and user commands that are defined in the script. In our example we can add | |
| 1884 a few lines to count the number of corrections: > | |
| 1885 | |
| 1886 19 let s:count = 4 | |
| 1887 .. | |
| 1888 30 function s:Add(from, correct) | |
| 1889 .. | |
| 1890 34 let s:count = s:count + 1 | |
| 1891 35 echo s:count . " corrections now" | |
| 1892 36 endfunction | |
| 1893 | |
| 1894 First s:count is initialized to 4 in the script itself. When later the | |
| 1895 s:Add() function is called, it increments s:count. It doesn't matter from | |
| 1896 where the function was called, since it has been defined in the script, it | |
| 1897 will use the local variables from this script. | |
| 1898 | |
| 1899 | |
| 1900 THE RESULT | |
| 1901 | |
| 1902 Here is the resulting complete example: > | |
| 1903 | |
| 1904 1 " Vim global plugin for correcting typing mistakes | |
| 1905 2 " Last Change: 2000 Oct 15 | |
| 1906 3 " Maintainer: Bram Moolenaar <Bram@vim.org> | |
| 1907 4 " License: This file is placed in the public domain. | |
| 1908 5 | |
|
2325
f177a6431514
Better implementation of creating the Color Scheme menu. (Juergen Kraemer)
Bram Moolenaar <bram@vim.org>
parents:
2301
diff
changeset
|
1909 6 if exists("g:loaded_typecorr") |
| 7 | 1910 7 finish |
| 1911 8 endif | |
|
2325
f177a6431514
Better implementation of creating the Color Scheme menu. (Juergen Kraemer)
Bram Moolenaar <bram@vim.org>
parents:
2301
diff
changeset
|
1912 9 let g:loaded_typecorr = 1 |
| 7 | 1913 10 |
| 1914 11 let s:save_cpo = &cpo | |
| 1915 12 set cpo&vim | |
| 1916 13 | |
| 1917 14 iabbrev teh the | |
| 1918 15 iabbrev otehr other | |
| 1919 16 iabbrev wnat want | |
| 1920 17 iabbrev synchronisation | |
| 1921 18 \ synchronization | |
| 1922 19 let s:count = 4 | |
| 1923 20 | |
| 1924 21 if !hasmapto('<Plug>TypecorrAdd') | |
| 1925 22 map <unique> <Leader>a <Plug>TypecorrAdd | |
| 1926 23 endif | |
| 1927 24 noremap <unique> <script> <Plug>TypecorrAdd <SID>Add | |
| 1928 25 | |
| 1929 26 noremenu <script> Plugin.Add\ Correction <SID>Add | |
| 1930 27 | |
| 1931 28 noremap <SID>Add :call <SID>Add(expand("<cword>"), 1)<CR> | |
| 1932 29 | |
| 1933 30 function s:Add(from, correct) | |
| 1934 31 let to = input("type the correction for " . a:from . ": ") | |
| 1935 32 exe ":iabbrev " . a:from . " " . to | |
| 1936 33 if a:correct | exe "normal viws\<C-R>\" \b\e" | endif | |
| 1937 34 let s:count = s:count + 1 | |
| 1938 35 echo s:count . " corrections now" | |
| 1939 36 endfunction | |
| 1940 37 | |
| 1941 38 if !exists(":Correct") | |
| 1942 39 command -nargs=1 Correct :call s:Add(<q-args>, 0) | |
| 1943 40 endif | |
| 1944 41 | |
| 1945 42 let &cpo = s:save_cpo | |
| 1946 | |
| 1947 Line 33 wasn't explained yet. It applies the new correction to the word under | |
| 1948 the cursor. The |:normal| command is used to use the new abbreviation. Note | |
| 1949 that mappings and abbreviations are expanded here, even though the function | |
| 1950 was called from a mapping defined with ":noremap". | |
| 1951 | |
| 1952 Using "unix" for the 'fileformat' option is recommended. The Vim scripts will | |
| 1953 then work everywhere. Scripts with 'fileformat' set to "dos" do not work on | |
| 1954 Unix. Also see |:source_crnl|. To be sure it is set right, do this before | |
| 1955 writing the file: > | |
| 1956 | |
| 1957 :set fileformat=unix | |
| 1958 | |
| 1959 | |
| 1960 DOCUMENTATION *write-local-help* | |
| 1961 | |
| 1962 It's a good idea to also write some documentation for your plugin. Especially | |
| 1963 when its behavior can be changed by the user. See |add-local-help| for how | |
| 1964 they are installed. | |
| 1965 | |
| 1966 Here is a simple example for a plugin help file, called "typecorr.txt": > | |
| 1967 | |
| 1968 1 *typecorr.txt* Plugin for correcting typing mistakes | |
| 1969 2 | |
| 1970 3 If you make typing mistakes, this plugin will have them corrected | |
| 1971 4 automatically. | |
| 1972 5 | |
| 1973 6 There are currently only a few corrections. Add your own if you like. | |
| 1974 7 | |
| 1975 8 Mappings: | |
| 1976 9 <Leader>a or <Plug>TypecorrAdd | |
| 1977 10 Add a correction for the word under the cursor. | |
| 1978 11 | |
| 1979 12 Commands: | |
| 1980 13 :Correct {word} | |
| 1981 14 Add a correction for {word}. | |
| 1982 15 | |
| 1983 16 *typecorr-settings* | |
| 1984 17 This plugin doesn't have any settings. | |
| 1985 | |
| 1986 The first line is actually the only one for which the format matters. It will | |
| 1987 be extracted from the help file to be put in the "LOCAL ADDITIONS:" section of | |
| 1988 help.txt |local-additions|. The first "*" must be in the first column of the | |
| 1989 first line. After adding your help file do ":help" and check that the entries | |
| 1990 line up nicely. | |
| 1991 | |
| 1992 You can add more tags inside ** in your help file. But be careful not to use | |
| 1993 existing help tags. You would probably use the name of your plugin in most of | |
| 1994 them, like "typecorr-settings" in the example. | |
| 1995 | |
| 1996 Using references to other parts of the help in || is recommended. This makes | |
| 1997 it easy for the user to find associated help. | |
| 1998 | |
| 1999 | |
| 2000 FILETYPE DETECTION *plugin-filetype* | |
| 2001 | |
| 2002 If your filetype is not already detected by Vim, you should create a filetype | |
| 2003 detection snippet in a separate file. It is usually in the form of an | |
| 2004 autocommand that sets the filetype when the file name matches a pattern. | |
| 2005 Example: > | |
| 2006 | |
| 2007 au BufNewFile,BufRead *.foo set filetype=foofoo | |
| 2008 | |
| 2009 Write this single-line file as "ftdetect/foofoo.vim" in the first directory | |
| 2010 that appears in 'runtimepath'. For Unix that would be | |
| 2011 "~/.vim/ftdetect/foofoo.vim". The convention is to use the name of the | |
| 2012 filetype for the script name. | |
| 2013 | |
| 2014 You can make more complicated checks if you like, for example to inspect the | |
| 2015 contents of the file to recognize the language. Also see |new-filetype|. | |
| 2016 | |
| 2017 | |
| 2018 SUMMARY *plugin-special* | |
| 2019 | |
| 2020 Summary of special things to use in a plugin: | |
| 2021 | |
| 2022 s:name Variables local to the script. | |
| 2023 | |
| 2024 <SID> Script-ID, used for mappings and functions local to | |
| 2025 the script. | |
| 2026 | |
| 2027 hasmapto() Function to test if the user already defined a mapping | |
| 2028 for functionality the script offers. | |
| 2029 | |
| 2030 <Leader> Value of "mapleader", which the user defines as the | |
| 2031 keys that plugin mappings start with. | |
| 2032 | |
| 2033 :map <unique> Give a warning if a mapping already exists. | |
| 2034 | |
| 2035 :noremap <script> Use only mappings local to the script, not global | |
| 2036 mappings. | |
| 2037 | |
| 2038 exists(":Cmd") Check if a user command already exists. | |
| 2039 | |
| 2040 ============================================================================== | |
| 161 | 2041 *41.12* Writing a filetype plugin *write-filetype-plugin* *ftplugin* |
| 7 | 2042 |
| 2043 A filetype plugin is like a global plugin, except that it sets options and | |
| 2044 defines mappings for the current buffer only. See |add-filetype-plugin| for | |
| 2045 how this type of plugin is used. | |
| 2046 | |
| 161 | 2047 First read the section on global plugins above |41.11|. All that is said there |
| 7 | 2048 also applies to filetype plugins. There are a few extras, which are explained |
| 2049 here. The essential thing is that a filetype plugin should only have an | |
| 2050 effect on the current buffer. | |
| 2051 | |
| 2052 | |
| 2053 DISABLING | |
| 2054 | |
| 2055 If you are writing a filetype plugin to be used by many people, they need a | |
| 2056 chance to disable loading it. Put this at the top of the plugin: > | |
| 2057 | |
| 2058 " Only do this when not done yet for this buffer | |
| 2059 if exists("b:did_ftplugin") | |
| 2060 finish | |
| 2061 endif | |
| 2062 let b:did_ftplugin = 1 | |
| 2063 | |
| 2064 This also needs to be used to avoid that the same plugin is executed twice for | |
| 2065 the same buffer (happens when using an ":edit" command without arguments). | |
| 2066 | |
| 2067 Now users can disable loading the default plugin completely by making a | |
| 2068 filetype plugin with only this line: > | |
| 2069 | |
| 2070 let b:did_ftplugin = 1 | |
| 2071 | |
| 2072 This does require that the filetype plugin directory comes before $VIMRUNTIME | |
| 2073 in 'runtimepath'! | |
| 2074 | |
| 2075 If you do want to use the default plugin, but overrule one of the settings, | |
| 2076 you can write the different setting in a script: > | |
| 2077 | |
| 2078 setlocal textwidth=70 | |
| 2079 | |
| 2080 Now write this in the "after" directory, so that it gets sourced after the | |
| 2081 distributed "vim.vim" ftplugin |after-directory|. For Unix this would be | |
| 2082 "~/.vim/after/ftplugin/vim.vim". Note that the default plugin will have set | |
| 2083 "b:did_ftplugin", but it is ignored here. | |
| 2084 | |
| 2085 | |
| 2086 OPTIONS | |
| 2087 | |
| 2088 To make sure the filetype plugin only affects the current buffer use the > | |
| 2089 | |
| 2090 :setlocal | |
| 2091 | |
| 2092 command to set options. And only set options which are local to a buffer (see | |
| 2093 the help for the option to check that). When using |:setlocal| for global | |
| 2094 options or options local to a window, the value will change for many buffers, | |
| 2095 and that is not what a filetype plugin should do. | |
| 2096 | |
| 2097 When an option has a value that is a list of flags or items, consider using | |
| 2098 "+=" and "-=" to keep the existing value. Be aware that the user may have | |
| 2099 changed an option value already. First resetting to the default value and | |
| 2100 then changing it often a good idea. Example: > | |
| 2101 | |
| 2102 :setlocal formatoptions& formatoptions+=ro | |
| 2103 | |
| 2104 | |
| 2105 MAPPINGS | |
| 2106 | |
| 2107 To make sure mappings will only work in the current buffer use the > | |
| 2108 | |
| 2109 :map <buffer> | |
| 2110 | |
| 2111 command. This needs to be combined with the two-step mapping explained above. | |
| 2112 An example of how to define functionality in a filetype plugin: > | |
| 2113 | |
| 2114 if !hasmapto('<Plug>JavaImport') | |
| 2115 map <buffer> <unique> <LocalLeader>i <Plug>JavaImport | |
| 2116 endif | |
| 2117 noremap <buffer> <unique> <Plug>JavaImport oimport ""<Left><Esc> | |
| 2118 | |
| 2119 |hasmapto()| is used to check if the user has already defined a map to | |
| 2120 <Plug>JavaImport. If not, then the filetype plugin defines the default | |
| 2121 mapping. This starts with |<LocalLeader>|, which allows the user to select | |
| 2122 the key(s) he wants filetype plugin mappings to start with. The default is a | |
| 2123 backslash. | |
| 2124 "<unique>" is used to give an error message if the mapping already exists or | |
| 2125 overlaps with an existing mapping. | |
| 2126 |:noremap| is used to avoid that any other mappings that the user has defined | |
| 2127 interferes. You might want to use ":noremap <script>" to allow remapping | |
| 2128 mappings defined in this script that start with <SID>. | |
| 2129 | |
| 2130 The user must have a chance to disable the mappings in a filetype plugin, | |
| 2131 without disabling everything. Here is an example of how this is done for a | |
| 2132 plugin for the mail filetype: > | |
| 2133 | |
| 2134 " Add mappings, unless the user didn't want this. | |
| 2135 if !exists("no_plugin_maps") && !exists("no_mail_maps") | |
| 2136 " Quote text by inserting "> " | |
| 2137 if !hasmapto('<Plug>MailQuote') | |
| 2138 vmap <buffer> <LocalLeader>q <Plug>MailQuote | |
| 2139 nmap <buffer> <LocalLeader>q <Plug>MailQuote | |
| 2140 endif | |
| 2141 vnoremap <buffer> <Plug>MailQuote :s/^/> /<CR> | |
| 2142 nnoremap <buffer> <Plug>MailQuote :.,$s/^/> /<CR> | |
| 2143 endif | |
| 2144 | |
| 2145 Two global variables are used: | |
| 2146 no_plugin_maps disables mappings for all filetype plugins | |
| 2147 no_mail_maps disables mappings for a specific filetype | |
| 2148 | |
| 2149 | |
| 2150 USER COMMANDS | |
| 2151 | |
| 2152 To add a user command for a specific file type, so that it can only be used in | |
| 2153 one buffer, use the "-buffer" argument to |:command|. Example: > | |
| 2154 | |
| 2155 :command -buffer Make make %:r.s | |
| 2156 | |
| 2157 | |
| 2158 VARIABLES | |
| 2159 | |
| 2160 A filetype plugin will be sourced for each buffer of the type it's for. Local | |
| 2161 script variables |s:var| will be shared between all invocations. Use local | |
| 2162 buffer variables |b:var| if you want a variable specifically for one buffer. | |
| 2163 | |
| 2164 | |
| 2165 FUNCTIONS | |
| 2166 | |
| 2167 When defining a function, this only needs to be done once. But the filetype | |
| 2168 plugin will be sourced every time a file with this filetype will be opened. | |
|
2207
b17bbfa96fa0
Add the settabvar() and gettabvar() functions.
Bram Moolenaar <bram@vim.org>
parents:
2154
diff
changeset
|
2169 This construct makes sure the function is only defined once: > |
| 7 | 2170 |
| 2171 :if !exists("*s:Func") | |
| 2172 : function s:Func(arg) | |
| 2173 : ... | |
| 2174 : endfunction | |
| 2175 :endif | |
| 2176 < | |
| 2177 | |
| 2178 UNDO *undo_ftplugin* | |
| 2179 | |
| 2180 When the user does ":setfiletype xyz" the effect of the previous filetype | |
| 2181 should be undone. Set the b:undo_ftplugin variable to the commands that will | |
| 2182 undo the settings in your filetype plugin. Example: > | |
| 2183 | |
| 2184 let b:undo_ftplugin = "setlocal fo< com< tw< commentstring<" | |
| 2185 \ . "| unlet b:match_ignorecase b:match_words b:match_skip" | |
| 2186 | |
| 2187 Using ":setlocal" with "<" after the option name resets the option to its | |
| 2188 global value. That is mostly the best way to reset the option value. | |
| 2189 | |
| 2190 This does require removing the "C" flag from 'cpoptions' to allow line | |
| 2191 continuation, as mentioned above |use-cpo-save|. | |
| 2192 | |
| 2193 | |
| 2194 FILE NAME | |
| 2195 | |
| 2196 The filetype must be included in the file name |ftplugin-name|. Use one of | |
| 2197 these three forms: | |
| 2198 | |
| 2199 .../ftplugin/stuff.vim | |
| 2200 .../ftplugin/stuff_foo.vim | |
| 2201 .../ftplugin/stuff/bar.vim | |
| 2202 | |
| 2203 "stuff" is the filetype, "foo" and "bar" are arbitrary names. | |
| 2204 | |
| 2205 | |
| 2206 SUMMARY *ftplugin-special* | |
| 2207 | |
| 2208 Summary of special things to use in a filetype plugin: | |
| 2209 | |
| 2210 <LocalLeader> Value of "maplocalleader", which the user defines as | |
| 2211 the keys that filetype plugin mappings start with. | |
| 2212 | |
| 2213 :map <buffer> Define a mapping local to the buffer. | |
| 2214 | |
| 2215 :noremap <script> Only remap mappings defined in this script that start | |
| 2216 with <SID>. | |
| 2217 | |
| 2218 :setlocal Set an option for the current buffer only. | |
| 2219 | |
| 2220 :command -buffer Define a user command local to the buffer. | |
| 2221 | |
| 2222 exists("*s:Func") Check if a function was already defined. | |
| 2223 | |
| 2224 Also see |plugin-special|, the special things used for all plugins. | |
| 2225 | |
| 2226 ============================================================================== | |
| 161 | 2227 *41.13* Writing a compiler plugin *write-compiler-plugin* |
| 7 | 2228 |
| 2229 A compiler plugin sets options for use with a specific compiler. The user can | |
| 2230 load it with the |:compiler| command. The main use is to set the | |
| 2231 'errorformat' and 'makeprg' options. | |
| 2232 | |
| 2233 Easiest is to have a look at examples. This command will edit all the default | |
| 2234 compiler plugins: > | |
| 2235 | |
| 2236 :next $VIMRUNTIME/compiler/*.vim | |
| 2237 | |
| 2238 Use |:next| to go to the next plugin file. | |
| 2239 | |
| 2240 There are two special items about these files. First is a mechanism to allow | |
| 2241 a user to overrule or add to the default file. The default files start with: > | |
| 2242 | |
| 2243 :if exists("current_compiler") | |
| 2244 : finish | |
| 2245 :endif | |
| 2246 :let current_compiler = "mine" | |
| 2247 | |
| 2248 When you write a compiler file and put it in your personal runtime directory | |
| 2249 (e.g., ~/.vim/compiler for Unix), you set the "current_compiler" variable to | |
| 2250 make the default file skip the settings. | |
| 570 | 2251 *:CompilerSet* |
| 7 | 2252 The second mechanism is to use ":set" for ":compiler!" and ":setlocal" for |
| 2253 ":compiler". Vim defines the ":CompilerSet" user command for this. However, | |
| 2254 older Vim versions don't, thus your plugin should define it then. This is an | |
| 2255 example: > | |
| 2256 | |
| 2257 if exists(":CompilerSet") != 2 | |
| 2258 command -nargs=* CompilerSet setlocal <args> | |
| 2259 endif | |
| 2260 CompilerSet errorformat& " use the default 'errorformat' | |
| 2261 CompilerSet makeprg=nmake | |
| 2262 | |
| 2263 When you write a compiler plugin for the Vim distribution or for a system-wide | |
| 2264 runtime directory, use the mechanism mentioned above. When | |
| 2265 "current_compiler" was already set by a user plugin nothing will be done. | |
| 2266 | |
| 2267 When you write a compiler plugin to overrule settings from a default plugin, | |
| 2268 don't check "current_compiler". This plugin is supposed to be loaded | |
| 2269 last, thus it should be in a directory at the end of 'runtimepath'. For Unix | |
| 2270 that could be ~/.vim/after/compiler. | |
| 2271 | |
| 2272 ============================================================================== | |
| 170 | 2273 *41.14* Writing a plugin that loads quickly *write-plugin-quickload* |
| 2274 | |
| 2275 A plugin may grow and become quite long. The startup delay may become | |
| 1620 | 2276 noticeable, while you hardly ever use the plugin. Then it's time for a |
| 170 | 2277 quickload plugin. |
| 2278 | |
| 2279 The basic idea is that the plugin is loaded twice. The first time user | |
| 2280 commands and mappings are defined that offer the functionality. The second | |
| 2281 time the functions that implement the functionality are defined. | |
| 2282 | |
| 2283 It may sound surprising that quickload means loading a script twice. What we | |
| 2284 mean is that it loads quickly the first time, postponing the bulk of the | |
| 2285 script to the second time, which only happens when you actually use it. When | |
| 2286 you always use the functionality it actually gets slower! | |
| 2287 | |
| 793 | 2288 Note that since Vim 7 there is an alternative: use the |autoload| |
| 2289 functionality |41.15|. | |
| 2290 | |
| 170 | 2291 The following example shows how it's done: > |
| 2292 | |
| 2293 " Vim global plugin for demonstrating quick loading | |
| 2294 " Last Change: 2005 Feb 25 | |
| 2295 " Maintainer: Bram Moolenaar <Bram@vim.org> | |
| 2296 " License: This file is placed in the public domain. | |
| 2297 | |
| 2298 if !exists("s:did_load") | |
| 2299 command -nargs=* BNRead call BufNetRead(<f-args>) | |
| 2300 map <F19> :call BufNetWrite('something')<CR> | |
| 2301 | |
| 2302 let s:did_load = 1 | |
| 2303 exe 'au FuncUndefined BufNet* source ' . expand('<sfile>') | |
| 2304 finish | |
| 2305 endif | |
| 2306 | |
| 2307 function BufNetRead(...) | |
| 2308 echo 'BufNetRead(' . string(a:000) . ')' | |
| 2309 " read functionality here | |
| 2310 endfunction | |
| 2311 | |
| 2312 function BufNetWrite(...) | |
| 2313 echo 'BufNetWrite(' . string(a:000) . ')' | |
| 2314 " write functionality here | |
| 2315 endfunction | |
| 2316 | |
| 2317 When the script is first loaded "s:did_load" is not set. The commands between | |
| 2318 the "if" and "endif" will be executed. This ends in a |:finish| command, thus | |
| 2319 the rest of the script is not executed. | |
| 2320 | |
| 2321 The second time the script is loaded "s:did_load" exists and the commands | |
| 2322 after the "endif" are executed. This defines the (possible long) | |
| 2323 BufNetRead() and BufNetWrite() functions. | |
| 2324 | |
| 2325 If you drop this script in your plugin directory Vim will execute it on | |
| 2326 startup. This is the sequence of events that happens: | |
| 2327 | |
| 2328 1. The "BNRead" command is defined and the <F19> key is mapped when the script | |
| 2329 is sourced at startup. A |FuncUndefined| autocommand is defined. The | |
| 2330 ":finish" command causes the script to terminate early. | |
| 2331 | |
| 2332 2. The user types the BNRead command or presses the <F19> key. The | |
| 2333 BufNetRead() or BufNetWrite() function will be called. | |
| 856 | 2334 |
| 170 | 2335 3. Vim can't find the function and triggers the |FuncUndefined| autocommand |
| 2336 event. Since the pattern "BufNet*" matches the invoked function, the | |
| 2337 command "source fname" will be executed. "fname" will be equal to the name | |
| 2338 of the script, no matter where it is located, because it comes from | |
| 2339 expanding "<sfile>" (see |expand()|). | |
| 2340 | |
| 2341 4. The script is sourced again, the "s:did_load" variable exists and the | |
| 2342 functions are defined. | |
| 2343 | |
| 2344 Notice that the functions that are loaded afterwards match the pattern in the | |
| 2345 |FuncUndefined| autocommand. You must make sure that no other plugin defines | |
| 2346 functions that match this pattern. | |
| 2347 | |
| 2348 ============================================================================== | |
| 2349 *41.15* Writing library scripts *write-library-script* | |
| 2350 | |
| 2351 Some functionality will be required in several places. When this becomes more | |
| 2352 than a few lines you will want to put it in one script and use it from many | |
| 2353 scripts. We will call that one script a library script. | |
| 2354 | |
| 2355 Manually loading a library script is possible, so long as you avoid loading it | |
| 2356 when it's already done. You can do this with the |exists()| function. | |
| 2357 Example: > | |
| 2358 | |
| 2359 if !exists('*MyLibFunction') | |
| 2360 runtime library/mylibscript.vim | |
| 2361 endif | |
| 2362 call MyLibFunction(arg) | |
| 2363 | |
| 2364 Here you need to know that MyLibFunction() is defined in a script | |
| 2365 "library/mylibscript.vim" in one of the directories in 'runtimepath'. | |
| 2366 | |
| 2367 To make this a bit simpler Vim offers the autoload mechanism. Then the | |
| 2368 example looks like this: > | |
| 2369 | |
| 270 | 2370 call mylib#myfunction(arg) |
| 170 | 2371 |
| 2372 That's a lot simpler, isn't it? Vim will recognize the function name and when | |
| 2373 it's not defined search for the script "autoload/mylib.vim" in 'runtimepath'. | |
| 270 | 2374 That script must define the "mylib#myfunction()" function. |
| 170 | 2375 |
| 2376 You can put many other functions in the mylib.vim script, you are free to | |
| 2377 organize your functions in library scripts. But you must use function names | |
| 323 | 2378 where the part before the '#' matches the script name. Otherwise Vim would |
| 2379 not know what script to load. | |
| 170 | 2380 |
| 681 | 2381 If you get really enthusiastic and write lots of library scripts, you may |
| 170 | 2382 want to use subdirectories. Example: > |
| 2383 | |
| 270 | 2384 call netlib#ftp#read('somefile') |
| 170 | 2385 |
| 2386 For Unix the library script used for this could be: | |
| 2387 | |
| 2388 ~/.vim/autoload/netlib/ftp.vim | |
| 2389 | |
| 2390 Where the function is defined like this: > | |
| 2391 | |
| 270 | 2392 function netlib#ftp#read(fname) |
| 170 | 2393 " Read the file fname through ftp |
| 2394 endfunction | |
| 2395 | |
| 2396 Notice that the name the function is defined with is exactly the same as the | |
| 323 | 2397 name used for calling the function. And the part before the last '#' |
| 170 | 2398 exactly matches the subdirectory and script name. |
| 2399 | |
| 2400 You can use the same mechanism for variables: > | |
| 2401 | |
| 270 | 2402 let weekdays = dutch#weekdays |
| 170 | 2403 |
| 2404 This will load the script "autoload/dutch.vim", which should contain something | |
| 2405 like: > | |
| 2406 | |
| 270 | 2407 let dutch#weekdays = ['zondag', 'maandag', 'dinsdag', 'woensdag', |
| 170 | 2408 \ 'donderdag', 'vrijdag', 'zaterdag'] |
| 2409 | |
| 2410 Further reading: |autoload|. | |
| 2411 | |
| 2412 ============================================================================== | |
| 793 | 2413 *41.16* Distributing Vim scripts *distribute-script* |
| 2414 | |
| 2415 Vim users will look for scripts on the Vim website: http://www.vim.org. | |
| 2416 If you made something that is useful for others, share it! | |
| 2417 | |
| 2418 Vim scripts can be used on any system. There might not be a tar or gzip | |
| 2419 command. If you want to pack files together and/or compress them the "zip" | |
| 2420 utility is recommended. | |
| 2421 | |
| 2422 For utmost portability use Vim itself to pack scripts together. This can be | |
| 2423 done with the Vimball utility. See |vimball|. | |
| 2424 | |
| 799 | 2425 It's good if you add a line to allow automatic updating. See |glvs-plugins|. |
| 2426 | |
| 793 | 2427 ============================================================================== |
| 7 | 2428 |
| 2429 Next chapter: |usr_42.txt| Add new menus | |
| 2430 | |
| 2431 Copyright: see |manual-copyright| vim:tw=78:ts=8:ft=help:norl: |