Mercurial > vim
annotate runtime/doc/usr_41.txt @ 2642:840c3cadb842
Updated runtime files.
| author | Bram Moolenaar <bram@vim.org> |
|---|---|
| date | Tue, 16 Nov 2010 20:34:40 +0100 |
| parents | 073ff46fe397 |
| children | 916c90b37ea9 |
| rev | line source |
|---|---|
| 2642 | 1 *usr_41.txt* For Vim version 7.3. Last change: 2010 Oct 31 |
| 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 |
| 824 | 797 diff_hlID() get highlight ID for diff mode at a position |
| 1326 | 798 matchadd() define a pattern to highlight (a "match") |
| 824 | 799 matcharg() get info about |:match| arguments |
| 1326 | 800 matchdelete() delete a match defined by |matchadd()| or a |
| 801 |:match| command | |
| 802 setmatches() restore a list of matches saved by | |
| 803 |getmatches()| | |
| 824 | 804 |
|
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
|
805 Spelling: *spell-functions* |
| 824 | 806 spellbadword() locate badly spelled word at or after cursor |
| 807 spellsuggest() return suggested spelling corrections | |
| 808 soundfold() return the sound-a-like equivalent of a word | |
| 7 | 809 |
|
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
|
810 History: *history-functions* |
| 7 | 811 histadd() add an item to a history |
| 812 histdel() delete an item from a history | |
| 813 histget() get an item from a history | |
| 814 histnr() get highest index of a history list | |
| 815 | |
|
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
|
816 Interactive: *interactive-functions* |
| 824 | 817 browse() put up a file requester |
| 818 browsedir() put up a directory requester | |
| 7 | 819 confirm() let the user make a choice |
| 820 getchar() get a character from the user | |
| 821 getcharmod() get modifiers for the last typed character | |
| 1620 | 822 feedkeys() put characters in the typeahead queue |
| 7 | 823 input() get a line from the user |
| 824 | 824 inputlist() let the user pick an entry from a list |
| 7 | 825 inputsecret() get a line from the user without showing it |
| 826 inputdialog() get a line from the user in a dialog | |
| 230 | 827 inputsave() save and clear typeahead |
| 7 | 828 inputrestore() restore typeahead |
| 829 | |
|
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
|
830 GUI: *gui-functions* |
| 824 | 831 getfontname() get name of current font being used |
| 832 getwinposx() X position of the GUI Vim window | |
| 833 getwinposy() Y position of the GUI Vim window | |
| 834 | |
|
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
|
835 Vim server: *server-functions* |
| 7 | 836 serverlist() return the list of server names |
| 837 remote_send() send command characters to a Vim server | |
| 838 remote_expr() evaluate an expression in a Vim server | |
| 839 server2client() send a reply to a client of a Vim server | |
| 840 remote_peek() check if there is a reply from a Vim server | |
| 841 remote_read() read a reply from a Vim server | |
| 842 foreground() move the Vim window to the foreground | |
| 843 remote_foreground() move the Vim server window to the foreground | |
| 844 | |
|
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
|
845 Window size and position: *window-size-functions* |
| 824 | 846 winheight() get height of a specific window |
| 847 winwidth() get width of a specific window | |
| 848 winrestcmd() return command to restore window sizes | |
| 849 winsaveview() get view of current window | |
| 850 winrestview() restore saved view of current window | |
| 851 | |
|
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
|
852 Various: *various-functions* |
| 7 | 853 mode() get current editing mode |
| 854 visualmode() last visual mode used | |
| 855 hasmapto() check if a mapping exists | |
| 856 mapcheck() check if a matching mapping exists | |
| 857 maparg() get rhs of a mapping | |
| 858 exists() check if a variable, function, etc. exists | |
| 859 has() check if a feature is supported in Vim | |
| 824 | 860 changenr() return number of most recent change |
| 7 | 861 cscope_connection() check if a cscope connection exists |
| 862 did_filetype() check if a FileType autocommand was used | |
| 863 eventhandler() check if invoked by an event handler | |
| 1620 | 864 getpid() get process ID of Vim |
| 824 | 865 |
| 7 | 866 libcall() call a function in an external library |
| 867 libcallnr() idem, returning a number | |
| 824 | 868 |
| 7 | 869 getreg() get contents of a register |
| 870 getregtype() get type of a register | |
| 871 setreg() set contents and type of a register | |
| 824 | 872 |
| 211 | 873 taglist() get list of matching tags |
| 824 | 874 tagfiles() get a list of tags files |
| 7 | 875 |
|
2050
afcf9db31561
updated for version 7.2.336
Bram Moolenaar <bram@zimbu.org>
parents:
1702
diff
changeset
|
876 mzeval() evaluate |MzScheme| expression |
|
afcf9db31561
updated for version 7.2.336
Bram Moolenaar <bram@zimbu.org>
parents:
1702
diff
changeset
|
877 |
| 7 | 878 ============================================================================== |
| 879 *41.7* Defining a function | |
| 880 | |
| 881 Vim enables you to define your own functions. The basic function declaration | |
| 882 begins as follows: > | |
| 883 | |
| 884 :function {name}({var1}, {var2}, ...) | |
| 885 : {body} | |
| 886 :endfunction | |
| 887 < | |
| 888 Note: | |
| 889 Function names must begin with a capital letter. | |
| 890 | |
| 891 Let's define a short function to return the smaller of two numbers. It starts | |
| 892 with this line: > | |
| 893 | |
| 894 :function Min(num1, num2) | |
| 895 | |
| 896 This tells Vim that the function is named "Min" and it takes two arguments: | |
| 897 "num1" and "num2". | |
| 898 The first thing you need to do is to check to see which number is smaller: | |
| 899 > | |
| 900 : if a:num1 < a:num2 | |
| 901 | |
| 902 The special prefix "a:" tells Vim that the variable is a function argument. | |
| 903 Let's assign the variable "smaller" the value of the smallest number: > | |
| 904 | |
| 905 : if a:num1 < a:num2 | |
| 906 : let smaller = a:num1 | |
| 907 : else | |
| 908 : let smaller = a:num2 | |
| 909 : endif | |
| 910 | |
| 911 The variable "smaller" is a local variable. Variables used inside a function | |
| 912 are local unless prefixed by something like "g:", "a:", or "s:". | |
| 913 | |
| 914 Note: | |
| 915 To access a global variable from inside a function you must prepend | |
| 1620 | 916 "g:" to it. Thus "g:today" inside a function is used for the global |
| 917 variable "today", and "today" is another variable, local to the | |
| 7 | 918 function. |
| 919 | |
| 920 You now use the ":return" statement to return the smallest number to the user. | |
| 921 Finally, you end the function: > | |
| 922 | |
| 923 : return smaller | |
| 924 :endfunction | |
| 925 | |
| 926 The complete function definition is as follows: > | |
| 927 | |
| 928 :function Min(num1, num2) | |
| 929 : if a:num1 < a:num2 | |
| 930 : let smaller = a:num1 | |
| 931 : else | |
| 932 : let smaller = a:num2 | |
| 933 : endif | |
| 934 : return smaller | |
| 935 :endfunction | |
| 936 | |
| 161 | 937 For people who like short functions, this does the same thing: > |
| 938 | |
| 939 :function Min(num1, num2) | |
| 940 : if a:num1 < a:num2 | |
| 941 : return a:num1 | |
| 942 : endif | |
| 943 : return a:num2 | |
| 944 :endfunction | |
| 945 | |
| 681 | 946 A user defined function is called in exactly the same way as a built-in |
| 7 | 947 function. Only the name is different. The Min function can be used like |
| 948 this: > | |
| 949 | |
| 950 :echo Min(5, 8) | |
| 951 | |
| 952 Only now will the function be executed and the lines be interpreted by Vim. | |
| 953 If there are mistakes, like using an undefined variable or function, you will | |
| 954 now get an error message. When defining the function these errors are not | |
| 955 detected. | |
| 956 | |
| 957 When a function reaches ":endfunction" or ":return" is used without an | |
| 958 argument, the function returns zero. | |
| 959 | |
| 960 To redefine a function that already exists, use the ! for the ":function" | |
| 961 command: > | |
| 962 | |
| 963 :function! Min(num1, num2, num3) | |
| 964 | |
| 965 | |
| 966 USING A RANGE | |
| 967 | |
| 968 The ":call" command can be given a line range. This can have one of two | |
| 969 meanings. When a function has been defined with the "range" keyword, it will | |
| 970 take care of the line range itself. | |
| 971 The function will be passed the variables "a:firstline" and "a:lastline". | |
| 972 These will have the line numbers from the range the function was called with. | |
| 973 Example: > | |
| 974 | |
| 975 :function Count_words() range | |
| 1620 | 976 : let lnum = a:firstline |
| 977 : let n = 0 | |
| 978 : while lnum <= a:lastline | |
| 979 : let n = n + len(split(getline(lnum))) | |
| 980 : let lnum = lnum + 1 | |
| 7 | 981 : endwhile |
| 1620 | 982 : echo "found " . n . " words" |
| 7 | 983 :endfunction |
| 984 | |
| 985 You can call this function with: > | |
| 986 | |
| 987 :10,30call Count_words() | |
| 988 | |
| 989 It will be executed once and echo the number of words. | |
| 990 The other way to use a line range is by defining a function without the | |
| 991 "range" keyword. The function will be called once for every line in the | |
| 992 range, with the cursor in that line. Example: > | |
| 993 | |
| 994 :function Number() | |
| 995 : echo "line " . line(".") . " contains: " . getline(".") | |
| 996 :endfunction | |
| 997 | |
| 998 If you call this function with: > | |
| 999 | |
| 1000 :10,15call Number() | |
| 1001 | |
| 1002 The function will be called six times. | |
| 1003 | |
| 1004 | |
| 1005 VARIABLE NUMBER OF ARGUMENTS | |
| 1006 | |
| 1007 Vim enables you to define functions that have a variable number of arguments. | |
| 1008 The following command, for instance, defines a function that must have 1 | |
| 1009 argument (start) and can have up to 20 additional arguments: > | |
| 1010 | |
| 1011 :function Show(start, ...) | |
| 1012 | |
| 1013 The variable "a:1" contains the first optional argument, "a:2" the second, and | |
| 1014 so on. The variable "a:0" contains the number of extra arguments. | |
| 1015 For example: > | |
| 1016 | |
| 1017 :function Show(start, ...) | |
| 1018 : echohl Title | |
| 1019 : echo "Show is " . a:start | |
| 1020 : echohl None | |
| 1021 : let index = 1 | |
| 1022 : while index <= a:0 | |
| 1023 : echo " Arg " . index . " is " . a:{index} | |
| 1024 : let index = index + 1 | |
| 1025 : endwhile | |
| 1026 : echo "" | |
| 1027 :endfunction | |
| 1028 | |
| 1029 This uses the ":echohl" command to specify the highlighting used for the | |
| 1030 following ":echo" command. ":echohl None" stops it again. The ":echon" | |
| 1031 command works like ":echo", but doesn't output a line break. | |
| 1032 | |
| 161 | 1033 You can also use the a:000 variable, it is a List of all the "..." arguments. |
| 1034 See |a:000|. | |
| 1035 | |
| 7 | 1036 |
| 1037 LISTING FUNCTIONS | |
| 1038 | |
| 1039 The ":function" command lists the names and arguments of all user-defined | |
| 1040 functions: > | |
| 1041 | |
| 1042 :function | |
| 1043 < function Show(start, ...) ~ | |
| 1044 function GetVimIndent() ~ | |
| 1045 function SetSyn(name) ~ | |
| 1046 | |
| 1047 To see what a function does, use its name as an argument for ":function": > | |
| 1048 | |
| 1049 :function SetSyn | |
| 1050 < 1 if &syntax == '' ~ | |
| 1051 2 let &syntax = a:name ~ | |
| 1052 3 endif ~ | |
| 1053 endfunction ~ | |
| 1054 | |
| 1055 | |
| 1056 DEBUGGING | |
| 1057 | |
| 1058 The line number is useful for when you get an error message or when debugging. | |
| 1059 See |debug-scripts| about debugging mode. | |
| 1060 You can also set the 'verbose' option to 12 or higher to see all function | |
| 1061 calls. Set it to 15 or higher to see every executed line. | |
| 1062 | |
| 1063 | |
| 1064 DELETING A FUNCTION | |
| 1065 | |
| 1066 To delete the Show() function: > | |
| 1067 | |
| 1068 :delfunction Show | |
| 1069 | |
| 1070 You get an error when the function doesn't exist. | |
| 1071 | |
| 161 | 1072 |
| 1073 FUNCTION REFERENCES | |
| 1074 | |
| 1075 Sometimes it can be useful to have a variable point to one function or | |
| 1076 another. You can do it with the function() function. It turns the name of a | |
| 1077 function into a reference: > | |
| 1078 | |
| 1079 :let result = 0 " or 1 | |
| 1080 :function! Right() | |
| 1081 : return 'Right!' | |
| 1082 :endfunc | |
| 1083 :function! Wrong() | |
| 1084 : return 'Wrong!' | |
| 1085 :endfunc | |
| 1086 : | |
| 1087 :if result == 1 | |
| 1088 : let Afunc = function('Right') | |
| 1089 :else | |
| 1090 : let Afunc = function('Wrong') | |
| 1091 :endif | |
| 1092 :echo call(Afunc, []) | |
| 1093 < Wrong! ~ | |
| 1094 | |
| 1095 Note that the name of a variable that holds a function reference must start | |
| 1096 with a capital. Otherwise it could be confused with the name of a builtin | |
| 1097 function. | |
| 1098 The way to invoke a function that a variable refers to is with the call() | |
| 1099 function. Its first argument is the function reference, the second argument | |
| 1100 is a List with arguments. | |
| 1101 | |
| 1102 Function references are most useful in combination with a Dictionary, as is | |
| 1103 explained in the next section. | |
| 1104 | |
| 7 | 1105 ============================================================================== |
| 161 | 1106 *41.8* Lists and Dictionaries |
| 1107 | |
| 1108 So far we have used the basic types String and Number. Vim also supports two | |
| 1109 composite types: List and Dictionary. | |
| 1110 | |
| 1111 A List is an ordered sequence of things. The things can be any kind of value, | |
| 1112 thus you can make a List of numbers, a List of Lists and even a List of mixed | |
| 1113 items. To create a List with three strings: > | |
| 1114 | |
| 856 | 1115 :let alist = ['aap', 'mies', 'noot'] |
| 161 | 1116 |
| 1117 The List items are enclosed in square brackets and separated by commas. To | |
| 1118 create an empty List: > | |
| 1119 | |
| 856 | 1120 :let alist = [] |
| 161 | 1121 |
| 1122 You can add items to a List with the add() function: > | |
| 1123 | |
| 856 | 1124 :let alist = [] |
| 161 | 1125 :call add(alist, 'foo') |
| 1126 :call add(alist, 'bar') | |
| 1127 :echo alist | |
| 1128 < ['foo', 'bar'] ~ | |
| 1129 | |
| 1130 List concatenation is done with +: > | |
| 1131 | |
| 1132 :echo alist + ['foo', 'bar'] | |
| 1133 < ['foo', 'bar', 'foo', 'bar'] ~ | |
| 1134 | |
| 1135 Or, if you want to extend a List directly: > | |
| 1136 | |
| 856 | 1137 :let alist = ['one'] |
| 161 | 1138 :call extend(alist, ['two', 'three']) |
| 1139 :echo alist | |
| 1140 < ['one', 'two', 'three'] ~ | |
| 1141 | |
| 1142 Notice that using add() will have a different effect: > | |
| 1143 | |
| 856 | 1144 :let alist = ['one'] |
| 161 | 1145 :call add(alist, ['two', 'three']) |
| 1146 :echo alist | |
| 1147 < ['one', ['two', 'three']] ~ | |
| 1148 | |
| 1149 The second argument of add() is added as a single item. | |
| 1150 | |
| 1151 | |
| 1152 FOR LOOP | |
| 1153 | |
| 1154 One of the nice things you can do with a List is iterate over it: > | |
| 1155 | |
| 1156 :let alist = ['one', 'two', 'three'] | |
| 1157 :for n in alist | |
| 1158 : echo n | |
| 1159 :endfor | |
| 1160 < one ~ | |
| 1161 two ~ | |
| 1162 three ~ | |
| 1163 | |
| 1164 This will loop over each element in List "alist", assigning the value to | |
| 1165 variable "n". The generic form of a for loop is: > | |
| 1166 | |
| 1167 :for {varname} in {listexpression} | |
| 1168 : {commands} | |
| 1169 :endfor | |
| 1170 | |
| 1171 To loop a certain number of times you need a List of a specific length. The | |
| 1172 range() function creates one for you: > | |
| 1173 | |
| 1174 :for a in range(3) | |
| 1175 : echo a | |
| 1176 :endfor | |
| 1177 < 0 ~ | |
| 1178 1 ~ | |
| 1179 2 ~ | |
| 1180 | |
| 1181 Notice that the first item of the List that range() produces is zero, thus the | |
| 1182 last item is one less than the length of the list. | |
| 1183 You can also specify the maximum value, the stride and even go backwards: > | |
| 1184 | |
| 1185 :for a in range(8, 4, -2) | |
| 1186 : echo a | |
| 1187 :endfor | |
| 1188 < 8 ~ | |
| 1189 6 ~ | |
| 1190 4 ~ | |
| 1191 | |
| 1192 A more useful example, looping over lines in the buffer: > | |
| 1193 | |
| 856 | 1194 :for line in getline(1, 20) |
| 1195 : if line =~ "Date: " | |
| 1196 : echo matchstr(line, 'Date: \zs.*') | |
| 1197 : endif | |
| 1198 :endfor | |
| 161 | 1199 |
| 1200 This looks into lines 1 to 20 (inclusive) and echoes any date found in there. | |
| 1201 | |
| 1202 | |
| 1203 DICTIONARIES | |
| 1204 | |
| 1205 A Dictionary stores key-value pairs. You can quickly lookup a value if you | |
| 1206 know the key. A Dictionary is created with curly braces: > | |
| 856 | 1207 |
| 161 | 1208 :let uk2nl = {'one': 'een', 'two': 'twee', 'three': 'drie'} |
| 1209 | |
| 164 | 1210 Now you can lookup words by putting the key in square brackets: > |
| 161 | 1211 |
| 1212 :echo uk2nl['two'] | |
| 1213 < twee ~ | |
| 1214 | |
| 1215 The generic form for defining a Dictionary is: > | |
| 1216 | |
| 1217 {<key> : <value>, ...} | |
| 1218 | |
| 1219 An empty Dictionary is one without any keys: > | |
| 1220 | |
| 1221 {} | |
| 1222 | |
| 1223 The possibilities with Dictionaries are numerous. There are various functions | |
| 1224 for them as well. For example, you can obtain a list of the keys and loop | |
| 1225 over them: > | |
| 1226 | |
| 1227 :for key in keys(uk2nl) | |
| 1228 : echo key | |
| 1229 :endfor | |
| 1230 < three ~ | |
| 1231 one ~ | |
| 1232 two ~ | |
| 1233 | |
| 1620 | 1234 You will notice the keys are not ordered. You can sort the list to get a |
| 161 | 1235 specific order: > |
| 1236 | |
| 1237 :for key in sort(keys(uk2nl)) | |
| 1238 : echo key | |
| 1239 :endfor | |
| 1240 < one ~ | |
| 1241 three ~ | |
| 1242 two ~ | |
| 1243 | |
| 1244 But you can never get back the order in which items are defined. For that you | |
| 1245 need to use a List, it stores items in an ordered sequence. | |
| 1246 | |
| 1247 | |
| 1248 DICTIONARY FUNCTIONS | |
| 1249 | |
| 1250 The items in a Dictionary can normally be obtained with an index in square | |
| 1251 brackets: > | |
| 1252 | |
| 1253 :echo uk2nl['one'] | |
| 1254 < een ~ | |
| 1255 | |
| 1256 A method that does the same, but without so many punctuation characters: > | |
| 1257 | |
| 1258 :echo uk2nl.one | |
| 1259 < een ~ | |
| 1260 | |
| 1261 This only works for a key that is made of ASCII letters, digits and the | |
| 1262 underscore. You can also assign a new value this way: > | |
| 1263 | |
| 1264 :let uk2nl.four = 'vier' | |
| 1265 :echo uk2nl | |
| 1266 < {'three': 'drie', 'four': 'vier', 'one': 'een', 'two': 'twee'} ~ | |
| 1267 | |
| 1268 And now for something special: you can directly define a function and store a | |
| 1269 reference to it in the dictionary: > | |
| 1270 | |
| 1271 :function uk2nl.translate(line) dict | |
| 1272 : return join(map(split(a:line), 'get(self, v:val, "???")')) | |
| 1273 :endfunction | |
| 1274 | |
| 1275 Let's first try it out: > | |
| 1276 | |
| 1277 :echo uk2nl.translate('three two five one') | |
| 1278 < drie twee ??? een ~ | |
| 1279 | |
| 1280 The first special thing you notice is the "dict" at the end of the ":function" | |
| 1281 line. This marks the function as being used from a Dictionary. The "self" | |
| 1282 local variable will then refer to that Dictionary. | |
| 1283 Now let's break up the complicated return command: > | |
| 1284 | |
| 1285 split(a:line) | |
| 1286 | |
| 1287 The split() function takes a string, chops it into white separated words | |
| 1288 and returns a list with these words. Thus in the example it returns: > | |
| 1289 | |
| 1290 :echo split('three two five one') | |
| 1291 < ['three', 'two', 'five', 'one'] ~ | |
| 1292 | |
| 1293 This list is the first argument to the map() function. This will go through | |
| 1294 the list, evaluating its second argument with "v:val" set to the value of each | |
| 1295 item. This is a shortcut to using a for loop. This command: > | |
| 1296 | |
| 1297 :let alist = map(split(a:line), 'get(self, v:val, "???")') | |
| 1298 | |
| 1299 Is equivalent to: > | |
| 1300 | |
| 1301 :let alist = split(a:line) | |
| 1302 :for idx in range(len(alist)) | |
| 1303 : let alist[idx] = get(self, alist[idx], "???") | |
| 1304 :endfor | |
| 1305 | |
| 1306 The get() function checks if a key is present in a Dictionary. If it is, then | |
| 1307 the value is retrieved. If it isn't, then the default value is returned, in | |
| 164 | 1308 the example it's '???'. This is a convenient way to handle situations where a |
| 161 | 1309 key may not be present and you don't want an error message. |
| 1310 | |
| 1311 The join() function does the opposite of split(): it joins together a list of | |
| 1312 words, putting a space in between. | |
| 1313 This combination of split(), map() and join() is a nice way to filter a line | |
| 1314 of words in a very compact way. | |
| 1315 | |
| 1316 | |
| 1317 OBJECT ORIENTED PROGRAMMING | |
| 1318 | |
| 1319 Now that you can put both values and functions in a Dictionary, you can | |
| 1320 actually use a Dictionary like an object. | |
| 1321 Above we used a Dictionary for translating Dutch to English. We might want | |
| 1322 to do the same for other languages. Let's first make an object (aka | |
| 1323 Dictionary) that has the translate function, but no words to translate: > | |
| 1324 | |
| 1325 :let transdict = {} | |
| 1326 :function transdict.translate(line) dict | |
| 1327 : return join(map(split(a:line), 'get(self.words, v:val, "???")')) | |
| 1328 :endfunction | |
| 1329 | |
| 1330 It's slightly different from the function above, using 'self.words' to lookup | |
| 1331 word translations. But we don't have a self.words. Thus you could call this | |
| 1332 an abstract class. | |
| 1333 | |
| 1334 Now we can instantiate a Dutch translation object: > | |
| 1335 | |
| 1336 :let uk2nl = copy(transdict) | |
| 1337 :let uk2nl.words = {'one': 'een', 'two': 'twee', 'three': 'drie'} | |
| 1338 :echo uk2nl.translate('three one') | |
| 1339 < drie een ~ | |
| 1340 | |
| 1341 And a German translator: > | |
| 1342 | |
| 1343 :let uk2de = copy(transdict) | |
| 1344 :let uk2de.words = {'one': 'ein', 'two': 'zwei', 'three': 'drei'} | |
| 1345 :echo uk2de.translate('three one') | |
| 1346 < drei ein ~ | |
| 1347 | |
| 1348 You see that the copy() function is used to make a copy of the "transdict" | |
| 1349 Dictionary and then the copy is changed to add the words. The original | |
| 1350 remains the same, of course. | |
| 1351 | |
| 1352 Now you can go one step further, and use your preferred translator: > | |
| 1353 | |
| 1354 :if $LANG =~ "de" | |
| 1355 : let trans = uk2de | |
| 1356 :else | |
| 1357 : let trans = uk2nl | |
| 1358 :endif | |
| 1359 :echo trans.translate('one two three') | |
| 1360 < een twee drie ~ | |
| 1361 | |
| 1362 Here "trans" refers to one of the two objects (Dictionaries). No copy is | |
| 1363 made. More about List and Dictionary identity can be found at |list-identity| | |
| 1364 and |dict-identity|. | |
| 1365 | |
| 1366 Now you might use a language that isn't supported. You can overrule the | |
| 1367 translate() function to do nothing: > | |
| 1368 | |
| 1369 :let uk2uk = copy(transdict) | |
| 1370 :function! uk2uk.translate(line) | |
| 1371 : return a:line | |
| 1372 :endfunction | |
| 1373 :echo uk2uk.translate('three one wladiwostok') | |
| 1374 < three one wladiwostok ~ | |
| 1375 | |
| 1376 Notice that a ! was used to overwrite the existing function reference. Now | |
| 1377 use "uk2uk" when no recognized language is found: > | |
| 1378 | |
| 1379 :if $LANG =~ "de" | |
| 1380 : let trans = uk2de | |
| 1381 :elseif $LANG =~ "nl" | |
| 1382 : let trans = uk2nl | |
| 1383 :else | |
| 1384 : let trans = uk2uk | |
| 1385 :endif | |
| 1386 :echo trans.translate('one two three') | |
| 1387 < one two three ~ | |
| 1388 | |
| 1389 For further reading see |Lists| and |Dictionaries|. | |
| 1390 | |
| 1391 ============================================================================== | |
| 1392 *41.9* Exceptions | |
| 7 | 1393 |
| 1394 Let's start with an example: > | |
| 1395 | |
| 1396 :try | |
| 1397 : read ~/templates/pascal.tmpl | |
| 1398 :catch /E484:/ | |
| 1399 : echo "Sorry, the Pascal template file cannot be found." | |
| 1400 :endtry | |
| 1401 | |
| 1402 The ":read" command will fail if the file does not exist. Instead of | |
| 1403 generating an error message, this code catches the error and gives the user a | |
| 1404 nice message instead. | |
| 1405 | |
| 1406 For the commands in between ":try" and ":endtry" errors are turned into | |
| 1407 exceptions. An exception is a string. In the case of an error the string | |
| 1408 contains the error message. And every error message has a number. In this | |
| 1409 case, the error we catch contains "E484:". This number is guaranteed to stay | |
| 1410 the same (the text may change, e.g., it may be translated). | |
| 1411 | |
| 1412 When the ":read" command causes another error, the pattern "E484:" will not | |
| 1413 match in it. Thus this exception will not be caught and result in the usual | |
| 1414 error message. | |
| 1415 | |
| 1416 You might be tempted to do this: > | |
| 1417 | |
| 1418 :try | |
| 1419 : read ~/templates/pascal.tmpl | |
| 1420 :catch | |
| 1421 : echo "Sorry, the Pascal template file cannot be found." | |
| 1422 :endtry | |
| 1423 | |
| 1424 This means all errors are caught. But then you will not see errors that are | |
| 1425 useful, such as "E21: Cannot make changes, 'modifiable' is off". | |
| 1426 | |
| 1427 Another useful mechanism is the ":finally" command: > | |
| 1428 | |
| 1429 :let tmp = tempname() | |
| 1430 :try | |
| 1431 : exe ".,$write " . tmp | |
| 1432 : exe "!filter " . tmp | |
| 1433 : .,$delete | |
| 1434 : exe "$read " . tmp | |
| 1435 :finally | |
| 1436 : call delete(tmp) | |
| 1437 :endtry | |
| 1438 | |
| 1439 This filters the lines from the cursor until the end of the file through the | |
| 1440 "filter" command, which takes a file name argument. No matter if the | |
| 1441 filtering works, something goes wrong in between ":try" and ":finally" or the | |
| 1442 user cancels the filtering by pressing CTRL-C, the "call delete(tmp)" is | |
| 1443 always executed. This makes sure you don't leave the temporary file behind. | |
| 1444 | |
| 1445 More information about exception handling can be found in the reference | |
| 1446 manual: |exception-handling|. | |
| 1447 | |
| 1448 ============================================================================== | |
| 161 | 1449 *41.10* Various remarks |
| 7 | 1450 |
| 1451 Here is a summary of items that apply to Vim scripts. They are also mentioned | |
| 1452 elsewhere, but form a nice checklist. | |
| 1453 | |
| 1454 The end-of-line character depends on the system. For Unix a single <NL> | |
| 1455 character is used. For MS-DOS, Windows, OS/2 and the like, <CR><LF> is used. | |
| 1456 This is important when using mappings that end in a <CR>. See |:source_crnl|. | |
| 1457 | |
| 1458 | |
| 1459 WHITE SPACE | |
| 1460 | |
| 1461 Blank lines are allowed and ignored. | |
| 1462 | |
| 1463 Leading whitespace characters (blanks and TABs) are always ignored. The | |
| 1464 whitespaces between parameters (e.g. between the 'set' and the 'cpoptions' in | |
| 1465 the example below) are reduced to one blank character and plays the role of a | |
| 1466 separator, the whitespaces after the last (visible) character may or may not | |
| 1467 be ignored depending on the situation, see below. | |
| 1468 | |
| 1469 For a ":set" command involving the "=" (equal) sign, such as in: > | |
| 1470 | |
| 1471 :set cpoptions =aABceFst | |
| 1472 | |
| 1473 the whitespace immediately before the "=" sign is ignored. But there can be | |
| 1474 no whitespace after the "=" sign! | |
| 1475 | |
| 1476 To include a whitespace character in the value of an option, it must be | |
| 1477 escaped by a "\" (backslash) as in the following example: > | |
| 1478 | |
| 1479 :set tags=my\ nice\ file | |
| 1480 | |
| 1481 The same example written as > | |
| 1482 | |
| 1483 :set tags=my nice file | |
| 1484 | |
| 1485 will issue an error, because it is interpreted as: > | |
| 1486 | |
| 1487 :set tags=my | |
| 1488 :set nice | |
| 1489 :set file | |
| 1490 | |
| 1491 | |
| 1492 COMMENTS | |
| 1493 | |
| 1494 The character " (the double quote mark) starts a comment. Everything after | |
| 1495 and including this character until the end-of-line is considered a comment and | |
| 1496 is ignored, except for commands that don't consider comments, as shown in | |
| 1497 examples below. A comment can start on any character position on the line. | |
| 1498 | |
| 1499 There is a little "catch" with comments for some commands. Examples: > | |
| 1500 | |
| 1501 :abbrev dev development " shorthand | |
| 1502 :map <F3> o#include " insert include | |
| 1503 :execute cmd " do it | |
| 1504 :!ls *.c " list C files | |
| 1505 | |
| 1506 The abbreviation 'dev' will be expanded to 'development " shorthand'. The | |
| 1507 mapping of <F3> will actually be the whole line after the 'o# ....' including | |
| 1508 the '" insert include'. The "execute" command will give an error. The "!" | |
| 1509 command will send everything after it to the shell, causing an error for an | |
| 1510 unmatched '"' character. | |
| 1511 There can be no comment after ":map", ":abbreviate", ":execute" and "!" | |
| 1512 commands (there are a few more commands with this restriction). For the | |
| 1513 ":map", ":abbreviate" and ":execute" commands there is a trick: > | |
| 1514 | |
| 1515 :abbrev dev development|" shorthand | |
| 1516 :map <F3> o#include|" insert include | |
| 1517 :execute cmd |" do it | |
| 1518 | |
| 1519 With the '|' character the command is separated from the next one. And that | |
| 1146 | 1520 next command is only a comment. For the last command you need to do two |
| 1521 things: |:execute| and use '|': > | |
| 1522 :exe '!ls *.c' |" list C files | |
| 7 | 1523 |
| 1524 Notice that there is no white space before the '|' in the abbreviation and | |
| 1525 mapping. For these commands, any character until the end-of-line or '|' is | |
| 1526 included. As a consequence of this behavior, you don't always see that | |
| 1527 trailing whitespace is included: > | |
| 1528 | |
| 1529 :map <F4> o#include | |
| 1530 | |
| 1146 | 1531 To spot these problems, you can set the 'list' option when editing vimrc |
| 7 | 1532 files. |
| 1533 | |
| 1146 | 1534 For Unix there is one special way to comment a line, that allows making a Vim |
| 1535 script executable: > | |
| 1536 #!/usr/bin/env vim -S | |
| 1537 echo "this is a Vim script" | |
| 1538 quit | |
| 1539 | |
| 1540 The "#" command by itself lists a line with the line number. Adding an | |
| 1541 exclamation mark changes it into doing nothing, so that you can add the shell | |
| 1542 command to execute the rest of the file. |:#!| |-S| | |
| 1543 | |
| 7 | 1544 |
| 1545 PITFALLS | |
| 1546 | |
| 1547 Even bigger problem arises in the following example: > | |
| 1548 | |
| 1549 :map ,ab o#include | |
| 1550 :unmap ,ab | |
| 1551 | |
| 1552 Here the unmap command will not work, because it tries to unmap ",ab ". This | |
| 1553 does not exist as a mapped sequence. An error will be issued, which is very | |
| 1554 hard to identify, because the ending whitespace character in ":unmap ,ab " is | |
| 1555 not visible. | |
| 1556 | |
| 1557 And this is the same as what happens when one uses a comment after an 'unmap' | |
| 1558 command: > | |
| 1559 | |
| 1560 :unmap ,ab " comment | |
| 1561 | |
| 1562 Here the comment part will be ignored. However, Vim will try to unmap | |
| 1563 ',ab ', which does not exist. Rewrite it as: > | |
| 1564 | |
| 1565 :unmap ,ab| " comment | |
| 1566 | |
| 1567 | |
| 1568 RESTORING THE VIEW | |
| 1569 | |
| 1570 Sometimes you want to make a change and go back to where cursor was. | |
| 1571 Restoring the relative position would also be nice, so that the same line | |
| 1572 appears at the top of the window. | |
| 1573 This example yanks the current line, puts it above the first line in the | |
| 1574 file and then restores the view: > | |
| 1575 | |
| 1576 map ,p ma"aYHmbgg"aP`bzt`a | |
| 1577 | |
| 1578 What this does: > | |
| 1579 ma"aYHmbgg"aP`bzt`a | |
| 1580 < ma set mark a at cursor position | |
| 1581 "aY yank current line into register a | |
| 1582 Hmb go to top line in window and set mark b there | |
| 1583 gg go to first line in file | |
| 1584 "aP put the yanked line above it | |
| 1585 `b go back to top line in display | |
| 1586 zt position the text in the window as before | |
| 1587 `a go back to saved cursor position | |
| 1588 | |
| 1589 | |
| 1590 PACKAGING | |
| 1591 | |
| 1592 To avoid your function names to interfere with functions that you get from | |
| 1593 others, use this scheme: | |
| 1594 - Prepend a unique string before each function name. I often use an | |
| 1595 abbreviation. For example, "OW_" is used for the option window functions. | |
| 1596 - Put the definition of your functions together in a file. Set a global | |
| 1597 variable to indicate that the functions have been loaded. When sourcing the | |
| 1598 file again, first unload the functions. | |
| 1599 Example: > | |
| 1600 | |
| 1601 " This is the XXX package | |
| 1602 | |
| 1603 if exists("XXX_loaded") | |
| 1604 delfun XXX_one | |
| 1605 delfun XXX_two | |
| 1606 endif | |
| 1607 | |
| 1608 function XXX_one(a) | |
| 1609 ... body of function ... | |
| 1610 endfun | |
| 1611 | |
| 1612 function XXX_two(b) | |
| 1613 ... body of function ... | |
| 1614 endfun | |
| 1615 | |
| 1616 let XXX_loaded = 1 | |
| 1617 | |
| 1618 ============================================================================== | |
| 161 | 1619 *41.11* Writing a plugin *write-plugin* |
| 7 | 1620 |
| 1621 You can write a Vim script in such a way that many people can use it. This is | |
| 1622 called a plugin. Vim users can drop your script in their plugin directory and | |
| 1623 use its features right away |add-plugin|. | |
| 1624 | |
| 1625 There are actually two types of plugins: | |
| 1626 | |
| 1627 global plugins: For all types of files. | |
| 1628 filetype plugins: Only for files of a specific type. | |
| 1629 | |
| 1630 In this section the first type is explained. Most items are also relevant for | |
| 1631 writing filetype plugins. The specifics for filetype plugins are in the next | |
| 1632 section |write-filetype-plugin|. | |
| 1633 | |
| 1634 | |
| 1635 NAME | |
| 1636 | |
| 1637 First of all you must choose a name for your plugin. The features provided | |
| 1638 by the plugin should be clear from its name. And it should be unlikely that | |
| 1639 someone else writes a plugin with the same name but which does something | |
| 1640 different. And please limit the name to 8 characters, to avoid problems on | |
| 1641 old Windows systems. | |
| 1642 | |
| 1643 A script that corrects typing mistakes could be called "typecorr.vim". We | |
| 1644 will use it here as an example. | |
| 1645 | |
| 1646 For the plugin to work for everybody, it should follow a few guidelines. This | |
| 1647 will be explained step-by-step. The complete example plugin is at the end. | |
| 1648 | |
| 1649 | |
| 1650 BODY | |
| 1651 | |
| 1652 Let's start with the body of the plugin, the lines that do the actual work: > | |
| 1653 | |
| 1654 14 iabbrev teh the | |
| 1655 15 iabbrev otehr other | |
| 1656 16 iabbrev wnat want | |
| 1657 17 iabbrev synchronisation | |
| 1658 18 \ synchronization | |
| 1659 19 let s:count = 4 | |
| 1660 | |
| 1661 The actual list should be much longer, of course. | |
| 1662 | |
| 1663 The line numbers have only been added to explain a few things, don't put them | |
| 1664 in your plugin file! | |
| 1665 | |
| 1666 | |
| 1667 HEADER | |
| 1668 | |
| 1669 You will probably add new corrections to the plugin and soon have several | |
| 1670 versions laying around. And when distributing this file, people will want to | |
| 1671 know who wrote this wonderful plugin and where they can send remarks. | |
| 1672 Therefore, put a header at the top of your plugin: > | |
| 1673 | |
| 1674 1 " Vim global plugin for correcting typing mistakes | |
| 1675 2 " Last Change: 2000 Oct 15 | |
| 1676 3 " Maintainer: Bram Moolenaar <Bram@vim.org> | |
| 1677 | |
| 1678 About copyright and licensing: Since plugins are very useful and it's hardly | |
| 1679 worth restricting their distribution, please consider making your plugin | |
| 1680 either public domain or use the Vim |license|. A short note about this near | |
| 1681 the top of the plugin should be sufficient. Example: > | |
| 1682 | |
| 1683 4 " License: This file is placed in the public domain. | |
| 1684 | |
| 1685 | |
| 1686 LINE CONTINUATION, AVOIDING SIDE EFFECTS *use-cpo-save* | |
| 1687 | |
| 1688 In line 18 above, the line-continuation mechanism is used |line-continuation|. | |
| 1689 Users with 'compatible' set will run into trouble here, they will get an error | |
| 1690 message. We can't just reset 'compatible', because that has a lot of side | |
| 1691 effects. To avoid this, we will set the 'cpoptions' option to its Vim default | |
| 1692 value and restore it later. That will allow the use of line-continuation and | |
| 1693 make the script work for most people. It is done like this: > | |
| 1694 | |
| 1695 11 let s:save_cpo = &cpo | |
| 1696 12 set cpo&vim | |
| 1697 .. | |
| 1698 42 let &cpo = s:save_cpo | |
| 1699 | |
| 1700 We first store the old value of 'cpoptions' in the s:save_cpo variable. At | |
| 1701 the end of the plugin this value is restored. | |
| 1702 | |
| 1703 Notice that a script-local variable is used |s:var|. A global variable could | |
| 1704 already be in use for something else. Always use script-local variables for | |
| 1705 things that are only used in the script. | |
| 1706 | |
| 1707 | |
| 1708 NOT LOADING | |
| 1709 | |
| 1710 It's possible that a user doesn't always want to load this plugin. Or the | |
| 1711 system administrator has dropped it in the system-wide plugin directory, but a | |
| 1712 user has his own plugin he wants to use. Then the user must have a chance to | |
| 1713 disable loading this specific plugin. This will make it possible: > | |
| 1714 | |
|
2325
f177a6431514
Better implementation of creating the Color Scheme menu. (Juergen Kraemer)
Bram Moolenaar <bram@vim.org>
parents:
2301
diff
changeset
|
1715 6 if exists("g:loaded_typecorr") |
| 7 | 1716 7 finish |
| 1717 8 endif | |
|
2325
f177a6431514
Better implementation of creating the Color Scheme menu. (Juergen Kraemer)
Bram Moolenaar <bram@vim.org>
parents:
2301
diff
changeset
|
1718 9 let g:loaded_typecorr = 1 |
| 7 | 1719 |
| 1720 This also avoids that when the script is loaded twice it would cause error | |
| 1721 messages for redefining functions and cause trouble for autocommands that are | |
| 1722 added twice. | |
| 1723 | |
|
2325
f177a6431514
Better implementation of creating the Color Scheme menu. (Juergen Kraemer)
Bram Moolenaar <bram@vim.org>
parents:
2301
diff
changeset
|
1724 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
|
1725 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
|
1726 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
|
1727 function). |
|
f177a6431514
Better implementation of creating the Color Scheme menu. (Juergen Kraemer)
Bram Moolenaar <bram@vim.org>
parents:
2301
diff
changeset
|
1728 |
|
f177a6431514
Better implementation of creating the Color Scheme menu. (Juergen Kraemer)
Bram Moolenaar <bram@vim.org>
parents:
2301
diff
changeset
|
1729 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
|
1730 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
|
1731 |
| 7 | 1732 |
| 1733 MAPPING | |
| 1734 | |
| 1735 Now let's make the plugin more interesting: We will add a mapping that adds a | |
| 1736 correction for the word under the cursor. We could just pick a key sequence | |
| 1737 for this mapping, but the user might already use it for something else. To | |
| 1738 allow the user to define which keys a mapping in a plugin uses, the <Leader> | |
| 1739 item can be used: > | |
| 1740 | |
| 1741 22 map <unique> <Leader>a <Plug>TypecorrAdd | |
| 1742 | |
| 1743 The "<Plug>TypecorrAdd" thing will do the work, more about that further on. | |
| 1744 | |
| 1745 The user can set the "mapleader" variable to the key sequence that he wants | |
| 1746 this mapping to start with. Thus if the user has done: > | |
| 1747 | |
| 1748 let mapleader = "_" | |
| 1749 | |
| 1750 the mapping will define "_a". If the user didn't do this, the default value | |
| 1751 will be used, which is a backslash. Then a map for "\a" will be defined. | |
| 1752 | |
| 1753 Note that <unique> is used, this will cause an error message if the mapping | |
| 1754 already happened to exist. |:map-<unique>| | |
| 1755 | |
| 1756 But what if the user wants to define his own key sequence? We can allow that | |
| 1757 with this mechanism: > | |
| 1758 | |
| 1759 21 if !hasmapto('<Plug>TypecorrAdd') | |
| 1760 22 map <unique> <Leader>a <Plug>TypecorrAdd | |
| 1761 23 endif | |
| 1762 | |
| 1763 This checks if a mapping to "<Plug>TypecorrAdd" already exists, and only | |
| 1764 defines the mapping from "<Leader>a" if it doesn't. The user then has a | |
| 1765 chance of putting this in his vimrc file: > | |
| 1766 | |
| 1767 map ,c <Plug>TypecorrAdd | |
| 1768 | |
| 1769 Then the mapped key sequence will be ",c" instead of "_a" or "\a". | |
| 1770 | |
| 1771 | |
| 1772 PIECES | |
| 1773 | |
| 1774 If a script gets longer, you often want to break up the work in pieces. You | |
| 1775 can use functions or mappings for this. But you don't want these functions | |
| 1776 and mappings to interfere with the ones from other scripts. For example, you | |
| 1777 could define a function Add(), but another script could try to define the same | |
| 1778 function. To avoid this, we define the function local to the script by | |
| 1779 prepending it with "s:". | |
| 1780 | |
| 1781 We will define a function that adds a new typing correction: > | |
| 1782 | |
| 1783 30 function s:Add(from, correct) | |
| 1784 31 let to = input("type the correction for " . a:from . ": ") | |
| 1785 32 exe ":iabbrev " . a:from . " " . to | |
| 1786 .. | |
| 1787 36 endfunction | |
| 1788 | |
| 1789 Now we can call the function s:Add() from within this script. If another | |
| 1790 script also defines s:Add(), it will be local to that script and can only | |
| 1791 be called from the script it was defined in. There can also be a global Add() | |
| 1792 function (without the "s:"), which is again another function. | |
| 1793 | |
| 1794 <SID> can be used with mappings. It generates a script ID, which identifies | |
| 1795 the current script. In our typing correction plugin we use it like this: > | |
| 1796 | |
| 1797 24 noremap <unique> <script> <Plug>TypecorrAdd <SID>Add | |
| 1798 .. | |
| 1799 28 noremap <SID>Add :call <SID>Add(expand("<cword>"), 1)<CR> | |
| 1800 | |
| 1801 Thus when a user types "\a", this sequence is invoked: > | |
| 1802 | |
| 1803 \a -> <Plug>TypecorrAdd -> <SID>Add -> :call <SID>Add() | |
| 1804 | |
| 1805 If another script would also map <SID>Add, it would get another script ID and | |
| 1806 thus define another mapping. | |
| 1807 | |
| 1808 Note that instead of s:Add() we use <SID>Add() here. That is because the | |
| 1809 mapping is typed by the user, thus outside of the script. The <SID> is | |
| 1810 translated to the script ID, so that Vim knows in which script to look for | |
| 1811 the Add() function. | |
| 1812 | |
| 1813 This is a bit complicated, but it's required for the plugin to work together | |
| 1814 with other plugins. The basic rule is that you use <SID>Add() in mappings and | |
| 1815 s:Add() in other places (the script itself, autocommands, user commands). | |
| 1816 | |
| 1817 We can also add a menu entry to do the same as the mapping: > | |
| 1818 | |
| 1819 26 noremenu <script> Plugin.Add\ Correction <SID>Add | |
| 1820 | |
| 1821 The "Plugin" menu is recommended for adding menu items for plugins. In this | |
| 1822 case only one item is used. When adding more items, creating a submenu is | |
| 1823 recommended. For example, "Plugin.CVS" could be used for a plugin that offers | |
| 1824 CVS operations "Plugin.CVS.checkin", "Plugin.CVS.checkout", etc. | |
| 1825 | |
| 1826 Note that in line 28 ":noremap" is used to avoid that any other mappings cause | |
| 1827 trouble. Someone may have remapped ":call", for example. In line 24 we also | |
| 1828 use ":noremap", but we do want "<SID>Add" to be remapped. This is why | |
| 1829 "<script>" is used here. This only allows mappings which are local to the | |
| 1830 script. |:map-<script>| The same is done in line 26 for ":noremenu". | |
| 1831 |:menu-<script>| | |
| 1832 | |
| 1833 | |
| 1834 <SID> AND <Plug> *using-<Plug>* | |
| 1835 | |
| 1836 Both <SID> and <Plug> are used to avoid that mappings of typed keys interfere | |
| 1837 with mappings that are only to be used from other mappings. Note the | |
| 1838 difference between using <SID> and <Plug>: | |
| 1839 | |
| 1840 <Plug> is visible outside of the script. It is used for mappings which the | |
| 1841 user might want to map a key sequence to. <Plug> is a special code | |
| 1842 that a typed key will never produce. | |
| 1843 To make it very unlikely that other plugins use the same sequence of | |
| 1844 characters, use this structure: <Plug> scriptname mapname | |
| 1845 In our example the scriptname is "Typecorr" and the mapname is "Add". | |
| 1846 This results in "<Plug>TypecorrAdd". Only the first character of | |
| 1847 scriptname and mapname is uppercase, so that we can see where mapname | |
| 1848 starts. | |
| 1849 | |
| 1850 <SID> is the script ID, a unique identifier for a script. | |
| 1851 Internally Vim translates <SID> to "<SNR>123_", where "123" can be any | |
| 1852 number. Thus a function "<SID>Add()" will have a name "<SNR>11_Add()" | |
| 1853 in one script, and "<SNR>22_Add()" in another. You can see this if | |
| 1854 you use the ":function" command to get a list of functions. The | |
| 1855 translation of <SID> in mappings is exactly the same, that's how you | |
| 1856 can call a script-local function from a mapping. | |
| 1857 | |
| 1858 | |
| 1859 USER COMMAND | |
| 1860 | |
| 1861 Now let's add a user command to add a correction: > | |
| 1862 | |
| 1863 38 if !exists(":Correct") | |
| 1864 39 command -nargs=1 Correct :call s:Add(<q-args>, 0) | |
| 1865 40 endif | |
| 1866 | |
| 1867 The user command is defined only if no command with the same name already | |
| 1868 exists. Otherwise we would get an error here. Overriding the existing user | |
| 1869 command with ":command!" is not a good idea, this would probably make the user | |
| 1870 wonder why the command he defined himself doesn't work. |:command| | |
| 1871 | |
| 1872 | |
| 1873 SCRIPT VARIABLES | |
| 1874 | |
| 1875 When a variable starts with "s:" it is a script variable. It can only be used | |
| 1876 inside a script. Outside the script it's not visible. This avoids trouble | |
| 1877 with using the same variable name in different scripts. The variables will be | |
| 1878 kept as long as Vim is running. And the same variables are used when sourcing | |
| 1879 the same script again. |s:var| | |
| 1880 | |
| 1881 The fun is that these variables can also be used in functions, autocommands | |
| 1882 and user commands that are defined in the script. In our example we can add | |
| 1883 a few lines to count the number of corrections: > | |
| 1884 | |
| 1885 19 let s:count = 4 | |
| 1886 .. | |
| 1887 30 function s:Add(from, correct) | |
| 1888 .. | |
| 1889 34 let s:count = s:count + 1 | |
| 1890 35 echo s:count . " corrections now" | |
| 1891 36 endfunction | |
| 1892 | |
| 1893 First s:count is initialized to 4 in the script itself. When later the | |
| 1894 s:Add() function is called, it increments s:count. It doesn't matter from | |
| 1895 where the function was called, since it has been defined in the script, it | |
| 1896 will use the local variables from this script. | |
| 1897 | |
| 1898 | |
| 1899 THE RESULT | |
| 1900 | |
| 1901 Here is the resulting complete example: > | |
| 1902 | |
| 1903 1 " Vim global plugin for correcting typing mistakes | |
| 1904 2 " Last Change: 2000 Oct 15 | |
| 1905 3 " Maintainer: Bram Moolenaar <Bram@vim.org> | |
| 1906 4 " License: This file is placed in the public domain. | |
| 1907 5 | |
|
2325
f177a6431514
Better implementation of creating the Color Scheme menu. (Juergen Kraemer)
Bram Moolenaar <bram@vim.org>
parents:
2301
diff
changeset
|
1908 6 if exists("g:loaded_typecorr") |
| 7 | 1909 7 finish |
| 1910 8 endif | |
|
2325
f177a6431514
Better implementation of creating the Color Scheme menu. (Juergen Kraemer)
Bram Moolenaar <bram@vim.org>
parents:
2301
diff
changeset
|
1911 9 let g:loaded_typecorr = 1 |
| 7 | 1912 10 |
| 1913 11 let s:save_cpo = &cpo | |
| 1914 12 set cpo&vim | |
| 1915 13 | |
| 1916 14 iabbrev teh the | |
| 1917 15 iabbrev otehr other | |
| 1918 16 iabbrev wnat want | |
| 1919 17 iabbrev synchronisation | |
| 1920 18 \ synchronization | |
| 1921 19 let s:count = 4 | |
| 1922 20 | |
| 1923 21 if !hasmapto('<Plug>TypecorrAdd') | |
| 1924 22 map <unique> <Leader>a <Plug>TypecorrAdd | |
| 1925 23 endif | |
| 1926 24 noremap <unique> <script> <Plug>TypecorrAdd <SID>Add | |
| 1927 25 | |
| 1928 26 noremenu <script> Plugin.Add\ Correction <SID>Add | |
| 1929 27 | |
| 1930 28 noremap <SID>Add :call <SID>Add(expand("<cword>"), 1)<CR> | |
| 1931 29 | |
| 1932 30 function s:Add(from, correct) | |
| 1933 31 let to = input("type the correction for " . a:from . ": ") | |
| 1934 32 exe ":iabbrev " . a:from . " " . to | |
| 1935 33 if a:correct | exe "normal viws\<C-R>\" \b\e" | endif | |
| 1936 34 let s:count = s:count + 1 | |
| 1937 35 echo s:count . " corrections now" | |
| 1938 36 endfunction | |
| 1939 37 | |
| 1940 38 if !exists(":Correct") | |
| 1941 39 command -nargs=1 Correct :call s:Add(<q-args>, 0) | |
| 1942 40 endif | |
| 1943 41 | |
| 1944 42 let &cpo = s:save_cpo | |
| 1945 | |
| 1946 Line 33 wasn't explained yet. It applies the new correction to the word under | |
| 1947 the cursor. The |:normal| command is used to use the new abbreviation. Note | |
| 1948 that mappings and abbreviations are expanded here, even though the function | |
| 1949 was called from a mapping defined with ":noremap". | |
| 1950 | |
| 1951 Using "unix" for the 'fileformat' option is recommended. The Vim scripts will | |
| 1952 then work everywhere. Scripts with 'fileformat' set to "dos" do not work on | |
| 1953 Unix. Also see |:source_crnl|. To be sure it is set right, do this before | |
| 1954 writing the file: > | |
| 1955 | |
| 1956 :set fileformat=unix | |
| 1957 | |
| 1958 | |
| 1959 DOCUMENTATION *write-local-help* | |
| 1960 | |
| 1961 It's a good idea to also write some documentation for your plugin. Especially | |
| 1962 when its behavior can be changed by the user. See |add-local-help| for how | |
| 1963 they are installed. | |
| 1964 | |
| 1965 Here is a simple example for a plugin help file, called "typecorr.txt": > | |
| 1966 | |
| 1967 1 *typecorr.txt* Plugin for correcting typing mistakes | |
| 1968 2 | |
| 1969 3 If you make typing mistakes, this plugin will have them corrected | |
| 1970 4 automatically. | |
| 1971 5 | |
| 1972 6 There are currently only a few corrections. Add your own if you like. | |
| 1973 7 | |
| 1974 8 Mappings: | |
| 1975 9 <Leader>a or <Plug>TypecorrAdd | |
| 1976 10 Add a correction for the word under the cursor. | |
| 1977 11 | |
| 1978 12 Commands: | |
| 1979 13 :Correct {word} | |
| 1980 14 Add a correction for {word}. | |
| 1981 15 | |
| 1982 16 *typecorr-settings* | |
| 1983 17 This plugin doesn't have any settings. | |
| 1984 | |
| 1985 The first line is actually the only one for which the format matters. It will | |
| 1986 be extracted from the help file to be put in the "LOCAL ADDITIONS:" section of | |
| 1987 help.txt |local-additions|. The first "*" must be in the first column of the | |
| 1988 first line. After adding your help file do ":help" and check that the entries | |
| 1989 line up nicely. | |
| 1990 | |
| 1991 You can add more tags inside ** in your help file. But be careful not to use | |
| 1992 existing help tags. You would probably use the name of your plugin in most of | |
| 1993 them, like "typecorr-settings" in the example. | |
| 1994 | |
| 1995 Using references to other parts of the help in || is recommended. This makes | |
| 1996 it easy for the user to find associated help. | |
| 1997 | |
| 1998 | |
| 1999 FILETYPE DETECTION *plugin-filetype* | |
| 2000 | |
| 2001 If your filetype is not already detected by Vim, you should create a filetype | |
| 2002 detection snippet in a separate file. It is usually in the form of an | |
| 2003 autocommand that sets the filetype when the file name matches a pattern. | |
| 2004 Example: > | |
| 2005 | |
| 2006 au BufNewFile,BufRead *.foo set filetype=foofoo | |
| 2007 | |
| 2008 Write this single-line file as "ftdetect/foofoo.vim" in the first directory | |
| 2009 that appears in 'runtimepath'. For Unix that would be | |
| 2010 "~/.vim/ftdetect/foofoo.vim". The convention is to use the name of the | |
| 2011 filetype for the script name. | |
| 2012 | |
| 2013 You can make more complicated checks if you like, for example to inspect the | |
| 2014 contents of the file to recognize the language. Also see |new-filetype|. | |
| 2015 | |
| 2016 | |
| 2017 SUMMARY *plugin-special* | |
| 2018 | |
| 2019 Summary of special things to use in a plugin: | |
| 2020 | |
| 2021 s:name Variables local to the script. | |
| 2022 | |
| 2023 <SID> Script-ID, used for mappings and functions local to | |
| 2024 the script. | |
| 2025 | |
| 2026 hasmapto() Function to test if the user already defined a mapping | |
| 2027 for functionality the script offers. | |
| 2028 | |
| 2029 <Leader> Value of "mapleader", which the user defines as the | |
| 2030 keys that plugin mappings start with. | |
| 2031 | |
| 2032 :map <unique> Give a warning if a mapping already exists. | |
| 2033 | |
| 2034 :noremap <script> Use only mappings local to the script, not global | |
| 2035 mappings. | |
| 2036 | |
| 2037 exists(":Cmd") Check if a user command already exists. | |
| 2038 | |
| 2039 ============================================================================== | |
| 161 | 2040 *41.12* Writing a filetype plugin *write-filetype-plugin* *ftplugin* |
| 7 | 2041 |
| 2042 A filetype plugin is like a global plugin, except that it sets options and | |
| 2043 defines mappings for the current buffer only. See |add-filetype-plugin| for | |
| 2044 how this type of plugin is used. | |
| 2045 | |
| 161 | 2046 First read the section on global plugins above |41.11|. All that is said there |
| 7 | 2047 also applies to filetype plugins. There are a few extras, which are explained |
| 2048 here. The essential thing is that a filetype plugin should only have an | |
| 2049 effect on the current buffer. | |
| 2050 | |
| 2051 | |
| 2052 DISABLING | |
| 2053 | |
| 2054 If you are writing a filetype plugin to be used by many people, they need a | |
| 2055 chance to disable loading it. Put this at the top of the plugin: > | |
| 2056 | |
| 2057 " Only do this when not done yet for this buffer | |
| 2058 if exists("b:did_ftplugin") | |
| 2059 finish | |
| 2060 endif | |
| 2061 let b:did_ftplugin = 1 | |
| 2062 | |
| 2063 This also needs to be used to avoid that the same plugin is executed twice for | |
| 2064 the same buffer (happens when using an ":edit" command without arguments). | |
| 2065 | |
| 2066 Now users can disable loading the default plugin completely by making a | |
| 2067 filetype plugin with only this line: > | |
| 2068 | |
| 2069 let b:did_ftplugin = 1 | |
| 2070 | |
| 2071 This does require that the filetype plugin directory comes before $VIMRUNTIME | |
| 2072 in 'runtimepath'! | |
| 2073 | |
| 2074 If you do want to use the default plugin, but overrule one of the settings, | |
| 2075 you can write the different setting in a script: > | |
| 2076 | |
| 2077 setlocal textwidth=70 | |
| 2078 | |
| 2079 Now write this in the "after" directory, so that it gets sourced after the | |
| 2080 distributed "vim.vim" ftplugin |after-directory|. For Unix this would be | |
| 2081 "~/.vim/after/ftplugin/vim.vim". Note that the default plugin will have set | |
| 2082 "b:did_ftplugin", but it is ignored here. | |
| 2083 | |
| 2084 | |
| 2085 OPTIONS | |
| 2086 | |
| 2087 To make sure the filetype plugin only affects the current buffer use the > | |
| 2088 | |
| 2089 :setlocal | |
| 2090 | |
| 2091 command to set options. And only set options which are local to a buffer (see | |
| 2092 the help for the option to check that). When using |:setlocal| for global | |
| 2093 options or options local to a window, the value will change for many buffers, | |
| 2094 and that is not what a filetype plugin should do. | |
| 2095 | |
| 2096 When an option has a value that is a list of flags or items, consider using | |
| 2097 "+=" and "-=" to keep the existing value. Be aware that the user may have | |
| 2098 changed an option value already. First resetting to the default value and | |
| 2099 then changing it often a good idea. Example: > | |
| 2100 | |
| 2101 :setlocal formatoptions& formatoptions+=ro | |
| 2102 | |
| 2103 | |
| 2104 MAPPINGS | |
| 2105 | |
| 2106 To make sure mappings will only work in the current buffer use the > | |
| 2107 | |
| 2108 :map <buffer> | |
| 2109 | |
| 2110 command. This needs to be combined with the two-step mapping explained above. | |
| 2111 An example of how to define functionality in a filetype plugin: > | |
| 2112 | |
| 2113 if !hasmapto('<Plug>JavaImport') | |
| 2114 map <buffer> <unique> <LocalLeader>i <Plug>JavaImport | |
| 2115 endif | |
| 2116 noremap <buffer> <unique> <Plug>JavaImport oimport ""<Left><Esc> | |
| 2117 | |
| 2118 |hasmapto()| is used to check if the user has already defined a map to | |
| 2119 <Plug>JavaImport. If not, then the filetype plugin defines the default | |
| 2120 mapping. This starts with |<LocalLeader>|, which allows the user to select | |
| 2121 the key(s) he wants filetype plugin mappings to start with. The default is a | |
| 2122 backslash. | |
| 2123 "<unique>" is used to give an error message if the mapping already exists or | |
| 2124 overlaps with an existing mapping. | |
| 2125 |:noremap| is used to avoid that any other mappings that the user has defined | |
| 2126 interferes. You might want to use ":noremap <script>" to allow remapping | |
| 2127 mappings defined in this script that start with <SID>. | |
| 2128 | |
| 2129 The user must have a chance to disable the mappings in a filetype plugin, | |
| 2130 without disabling everything. Here is an example of how this is done for a | |
| 2131 plugin for the mail filetype: > | |
| 2132 | |
| 2133 " Add mappings, unless the user didn't want this. | |
| 2134 if !exists("no_plugin_maps") && !exists("no_mail_maps") | |
| 2135 " Quote text by inserting "> " | |
| 2136 if !hasmapto('<Plug>MailQuote') | |
| 2137 vmap <buffer> <LocalLeader>q <Plug>MailQuote | |
| 2138 nmap <buffer> <LocalLeader>q <Plug>MailQuote | |
| 2139 endif | |
| 2140 vnoremap <buffer> <Plug>MailQuote :s/^/> /<CR> | |
| 2141 nnoremap <buffer> <Plug>MailQuote :.,$s/^/> /<CR> | |
| 2142 endif | |
| 2143 | |
| 2144 Two global variables are used: | |
| 2145 no_plugin_maps disables mappings for all filetype plugins | |
| 2146 no_mail_maps disables mappings for a specific filetype | |
| 2147 | |
| 2148 | |
| 2149 USER COMMANDS | |
| 2150 | |
| 2151 To add a user command for a specific file type, so that it can only be used in | |
| 2152 one buffer, use the "-buffer" argument to |:command|. Example: > | |
| 2153 | |
| 2154 :command -buffer Make make %:r.s | |
| 2155 | |
| 2156 | |
| 2157 VARIABLES | |
| 2158 | |
| 2159 A filetype plugin will be sourced for each buffer of the type it's for. Local | |
| 2160 script variables |s:var| will be shared between all invocations. Use local | |
| 2161 buffer variables |b:var| if you want a variable specifically for one buffer. | |
| 2162 | |
| 2163 | |
| 2164 FUNCTIONS | |
| 2165 | |
| 2166 When defining a function, this only needs to be done once. But the filetype | |
| 2167 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
|
2168 This construct makes sure the function is only defined once: > |
| 7 | 2169 |
| 2170 :if !exists("*s:Func") | |
| 2171 : function s:Func(arg) | |
| 2172 : ... | |
| 2173 : endfunction | |
| 2174 :endif | |
| 2175 < | |
| 2176 | |
| 2177 UNDO *undo_ftplugin* | |
| 2178 | |
| 2179 When the user does ":setfiletype xyz" the effect of the previous filetype | |
| 2180 should be undone. Set the b:undo_ftplugin variable to the commands that will | |
| 2181 undo the settings in your filetype plugin. Example: > | |
| 2182 | |
| 2183 let b:undo_ftplugin = "setlocal fo< com< tw< commentstring<" | |
| 2184 \ . "| unlet b:match_ignorecase b:match_words b:match_skip" | |
| 2185 | |
| 2186 Using ":setlocal" with "<" after the option name resets the option to its | |
| 2187 global value. That is mostly the best way to reset the option value. | |
| 2188 | |
| 2189 This does require removing the "C" flag from 'cpoptions' to allow line | |
| 2190 continuation, as mentioned above |use-cpo-save|. | |
| 2191 | |
| 2192 | |
| 2193 FILE NAME | |
| 2194 | |
| 2195 The filetype must be included in the file name |ftplugin-name|. Use one of | |
| 2196 these three forms: | |
| 2197 | |
| 2198 .../ftplugin/stuff.vim | |
| 2199 .../ftplugin/stuff_foo.vim | |
| 2200 .../ftplugin/stuff/bar.vim | |
| 2201 | |
| 2202 "stuff" is the filetype, "foo" and "bar" are arbitrary names. | |
| 2203 | |
| 2204 | |
| 2205 SUMMARY *ftplugin-special* | |
| 2206 | |
| 2207 Summary of special things to use in a filetype plugin: | |
| 2208 | |
| 2209 <LocalLeader> Value of "maplocalleader", which the user defines as | |
| 2210 the keys that filetype plugin mappings start with. | |
| 2211 | |
| 2212 :map <buffer> Define a mapping local to the buffer. | |
| 2213 | |
| 2214 :noremap <script> Only remap mappings defined in this script that start | |
| 2215 with <SID>. | |
| 2216 | |
| 2217 :setlocal Set an option for the current buffer only. | |
| 2218 | |
| 2219 :command -buffer Define a user command local to the buffer. | |
| 2220 | |
| 2221 exists("*s:Func") Check if a function was already defined. | |
| 2222 | |
| 2223 Also see |plugin-special|, the special things used for all plugins. | |
| 2224 | |
| 2225 ============================================================================== | |
| 161 | 2226 *41.13* Writing a compiler plugin *write-compiler-plugin* |
| 7 | 2227 |
| 2228 A compiler plugin sets options for use with a specific compiler. The user can | |
| 2229 load it with the |:compiler| command. The main use is to set the | |
| 2230 'errorformat' and 'makeprg' options. | |
| 2231 | |
| 2232 Easiest is to have a look at examples. This command will edit all the default | |
| 2233 compiler plugins: > | |
| 2234 | |
| 2235 :next $VIMRUNTIME/compiler/*.vim | |
| 2236 | |
| 2237 Use |:next| to go to the next plugin file. | |
| 2238 | |
| 2239 There are two special items about these files. First is a mechanism to allow | |
| 2240 a user to overrule or add to the default file. The default files start with: > | |
| 2241 | |
| 2242 :if exists("current_compiler") | |
| 2243 : finish | |
| 2244 :endif | |
| 2245 :let current_compiler = "mine" | |
| 2246 | |
| 2247 When you write a compiler file and put it in your personal runtime directory | |
| 2248 (e.g., ~/.vim/compiler for Unix), you set the "current_compiler" variable to | |
| 2249 make the default file skip the settings. | |
| 570 | 2250 *:CompilerSet* |
| 7 | 2251 The second mechanism is to use ":set" for ":compiler!" and ":setlocal" for |
| 2252 ":compiler". Vim defines the ":CompilerSet" user command for this. However, | |
| 2253 older Vim versions don't, thus your plugin should define it then. This is an | |
| 2254 example: > | |
| 2255 | |
| 2256 if exists(":CompilerSet") != 2 | |
| 2257 command -nargs=* CompilerSet setlocal <args> | |
| 2258 endif | |
| 2259 CompilerSet errorformat& " use the default 'errorformat' | |
| 2260 CompilerSet makeprg=nmake | |
| 2261 | |
| 2262 When you write a compiler plugin for the Vim distribution or for a system-wide | |
| 2263 runtime directory, use the mechanism mentioned above. When | |
| 2264 "current_compiler" was already set by a user plugin nothing will be done. | |
| 2265 | |
| 2266 When you write a compiler plugin to overrule settings from a default plugin, | |
| 2267 don't check "current_compiler". This plugin is supposed to be loaded | |
| 2268 last, thus it should be in a directory at the end of 'runtimepath'. For Unix | |
| 2269 that could be ~/.vim/after/compiler. | |
| 2270 | |
| 2271 ============================================================================== | |
| 170 | 2272 *41.14* Writing a plugin that loads quickly *write-plugin-quickload* |
| 2273 | |
| 2274 A plugin may grow and become quite long. The startup delay may become | |
| 1620 | 2275 noticeable, while you hardly ever use the plugin. Then it's time for a |
| 170 | 2276 quickload plugin. |
| 2277 | |
| 2278 The basic idea is that the plugin is loaded twice. The first time user | |
| 2279 commands and mappings are defined that offer the functionality. The second | |
| 2280 time the functions that implement the functionality are defined. | |
| 2281 | |
| 2282 It may sound surprising that quickload means loading a script twice. What we | |
| 2283 mean is that it loads quickly the first time, postponing the bulk of the | |
| 2284 script to the second time, which only happens when you actually use it. When | |
| 2285 you always use the functionality it actually gets slower! | |
| 2286 | |
| 793 | 2287 Note that since Vim 7 there is an alternative: use the |autoload| |
| 2288 functionality |41.15|. | |
| 2289 | |
| 170 | 2290 The following example shows how it's done: > |
| 2291 | |
| 2292 " Vim global plugin for demonstrating quick loading | |
| 2293 " Last Change: 2005 Feb 25 | |
| 2294 " Maintainer: Bram Moolenaar <Bram@vim.org> | |
| 2295 " License: This file is placed in the public domain. | |
| 2296 | |
| 2297 if !exists("s:did_load") | |
| 2298 command -nargs=* BNRead call BufNetRead(<f-args>) | |
| 2299 map <F19> :call BufNetWrite('something')<CR> | |
| 2300 | |
| 2301 let s:did_load = 1 | |
| 2302 exe 'au FuncUndefined BufNet* source ' . expand('<sfile>') | |
| 2303 finish | |
| 2304 endif | |
| 2305 | |
| 2306 function BufNetRead(...) | |
| 2307 echo 'BufNetRead(' . string(a:000) . ')' | |
| 2308 " read functionality here | |
| 2309 endfunction | |
| 2310 | |
| 2311 function BufNetWrite(...) | |
| 2312 echo 'BufNetWrite(' . string(a:000) . ')' | |
| 2313 " write functionality here | |
| 2314 endfunction | |
| 2315 | |
| 2316 When the script is first loaded "s:did_load" is not set. The commands between | |
| 2317 the "if" and "endif" will be executed. This ends in a |:finish| command, thus | |
| 2318 the rest of the script is not executed. | |
| 2319 | |
| 2320 The second time the script is loaded "s:did_load" exists and the commands | |
| 2321 after the "endif" are executed. This defines the (possible long) | |
| 2322 BufNetRead() and BufNetWrite() functions. | |
| 2323 | |
| 2324 If you drop this script in your plugin directory Vim will execute it on | |
| 2325 startup. This is the sequence of events that happens: | |
| 2326 | |
| 2327 1. The "BNRead" command is defined and the <F19> key is mapped when the script | |
| 2328 is sourced at startup. A |FuncUndefined| autocommand is defined. The | |
| 2329 ":finish" command causes the script to terminate early. | |
| 2330 | |
| 2331 2. The user types the BNRead command or presses the <F19> key. The | |
| 2332 BufNetRead() or BufNetWrite() function will be called. | |
| 856 | 2333 |
| 170 | 2334 3. Vim can't find the function and triggers the |FuncUndefined| autocommand |
| 2335 event. Since the pattern "BufNet*" matches the invoked function, the | |
| 2336 command "source fname" will be executed. "fname" will be equal to the name | |
| 2337 of the script, no matter where it is located, because it comes from | |
| 2338 expanding "<sfile>" (see |expand()|). | |
| 2339 | |
| 2340 4. The script is sourced again, the "s:did_load" variable exists and the | |
| 2341 functions are defined. | |
| 2342 | |
| 2343 Notice that the functions that are loaded afterwards match the pattern in the | |
| 2344 |FuncUndefined| autocommand. You must make sure that no other plugin defines | |
| 2345 functions that match this pattern. | |
| 2346 | |
| 2347 ============================================================================== | |
| 2348 *41.15* Writing library scripts *write-library-script* | |
| 2349 | |
| 2350 Some functionality will be required in several places. When this becomes more | |
| 2351 than a few lines you will want to put it in one script and use it from many | |
| 2352 scripts. We will call that one script a library script. | |
| 2353 | |
| 2354 Manually loading a library script is possible, so long as you avoid loading it | |
| 2355 when it's already done. You can do this with the |exists()| function. | |
| 2356 Example: > | |
| 2357 | |
| 2358 if !exists('*MyLibFunction') | |
| 2359 runtime library/mylibscript.vim | |
| 2360 endif | |
| 2361 call MyLibFunction(arg) | |
| 2362 | |
| 2363 Here you need to know that MyLibFunction() is defined in a script | |
| 2364 "library/mylibscript.vim" in one of the directories in 'runtimepath'. | |
| 2365 | |
| 2366 To make this a bit simpler Vim offers the autoload mechanism. Then the | |
| 2367 example looks like this: > | |
| 2368 | |
| 270 | 2369 call mylib#myfunction(arg) |
| 170 | 2370 |
| 2371 That's a lot simpler, isn't it? Vim will recognize the function name and when | |
| 2372 it's not defined search for the script "autoload/mylib.vim" in 'runtimepath'. | |
| 270 | 2373 That script must define the "mylib#myfunction()" function. |
| 170 | 2374 |
| 2375 You can put many other functions in the mylib.vim script, you are free to | |
| 2376 organize your functions in library scripts. But you must use function names | |
| 323 | 2377 where the part before the '#' matches the script name. Otherwise Vim would |
| 2378 not know what script to load. | |
| 170 | 2379 |
| 681 | 2380 If you get really enthusiastic and write lots of library scripts, you may |
| 170 | 2381 want to use subdirectories. Example: > |
| 2382 | |
| 270 | 2383 call netlib#ftp#read('somefile') |
| 170 | 2384 |
| 2385 For Unix the library script used for this could be: | |
| 2386 | |
| 2387 ~/.vim/autoload/netlib/ftp.vim | |
| 2388 | |
| 2389 Where the function is defined like this: > | |
| 2390 | |
| 270 | 2391 function netlib#ftp#read(fname) |
| 170 | 2392 " Read the file fname through ftp |
| 2393 endfunction | |
| 2394 | |
| 2395 Notice that the name the function is defined with is exactly the same as the | |
| 323 | 2396 name used for calling the function. And the part before the last '#' |
| 170 | 2397 exactly matches the subdirectory and script name. |
| 2398 | |
| 2399 You can use the same mechanism for variables: > | |
| 2400 | |
| 270 | 2401 let weekdays = dutch#weekdays |
| 170 | 2402 |
| 2403 This will load the script "autoload/dutch.vim", which should contain something | |
| 2404 like: > | |
| 2405 | |
| 270 | 2406 let dutch#weekdays = ['zondag', 'maandag', 'dinsdag', 'woensdag', |
| 170 | 2407 \ 'donderdag', 'vrijdag', 'zaterdag'] |
| 2408 | |
| 2409 Further reading: |autoload|. | |
| 2410 | |
| 2411 ============================================================================== | |
| 793 | 2412 *41.16* Distributing Vim scripts *distribute-script* |
| 2413 | |
| 2414 Vim users will look for scripts on the Vim website: http://www.vim.org. | |
| 2415 If you made something that is useful for others, share it! | |
| 2416 | |
| 2417 Vim scripts can be used on any system. There might not be a tar or gzip | |
| 2418 command. If you want to pack files together and/or compress them the "zip" | |
| 2419 utility is recommended. | |
| 2420 | |
| 2421 For utmost portability use Vim itself to pack scripts together. This can be | |
| 2422 done with the Vimball utility. See |vimball|. | |
| 2423 | |
| 799 | 2424 It's good if you add a line to allow automatic updating. See |glvs-plugins|. |
| 2425 | |
| 793 | 2426 ============================================================================== |
| 7 | 2427 |
| 2428 Next chapter: |usr_42.txt| Add new menus | |
| 2429 | |
| 2430 Copyright: see |manual-copyright| vim:tw=78:ts=8:ft=help:norl: |