Mercurial > vim
annotate runtime/doc/usr_41.txt @ 25445:65f04b6effd5 v8.2.3259
patch 8.2.3259: when 'indentexpr' causes an error did_throw may hang
Commit: https://github.com/vim/vim/commit/620c959c6c00e469c4d3b1ab2e08e4767ee142a4
Author: Bram Moolenaar <Bram@vim.org>
Date: Sat Jul 31 21:32:31 2021 +0200
patch 8.2.3259: when 'indentexpr' causes an error did_throw may hang
Problem: When 'indentexpr' causes an error the did_throw flag may remain
set.
Solution: Reset did_throw and show the error. (closes #8677)
author | Bram Moolenaar <Bram@vim.org> |
---|---|
date | Sat, 31 Jul 2021 21:45:04 +0200 |
parents | bdda48f01a68 |
children | 446f478d6fb1 |
rev | line source |
---|---|
25402 | 1 *usr_41.txt* For Vim version 8.2. Last change: 2021 Jul 19 |
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 | |
20856 | 44 If you are familiar with Python, you can find a comparison between |
45 Python and Vim script here, with pointers to other documents: | |
46 https://gist.github.com/yegappan/16d964a37ead0979b05e655aa036cad0 | |
21676 | 47 And if you are familiar with JavaScript: |
20856 | 48 https://w0rp.com/blog/post/vim-script-for-the-javascripter/ |
20687
770a8e9c4781
patch 8.2.0897: list of functions in patched version is outdated
Bram Moolenaar <Bram@vim.org>
parents:
20643
diff
changeset
|
49 |
7 | 50 Let's start with a simple example: > |
51 | |
52 :let i = 1 | |
53 :while i < 5 | |
54 : echo "count is" i | |
161 | 55 : let i += 1 |
7 | 56 :endwhile |
57 < | |
58 Note: | |
59 The ":" characters are not really needed here. You only need to use | |
60 them when you type a command. In a Vim script file they can be left | |
61 out. We will use them here anyway to make clear these are colon | |
62 commands and make them stand out from Normal mode commands. | |
161 | 63 Note: |
64 You can try out the examples by yanking the lines from the text here | |
65 and executing them with :@" | |
66 | |
67 The output of the example code is: | |
68 | |
69 count is 1 ~ | |
70 count is 2 ~ | |
71 count is 3 ~ | |
72 count is 4 ~ | |
73 | |
74 In the first line the ":let" command assigns a value to a variable. The | |
75 generic form is: > | |
7 | 76 |
77 :let {variable} = {expression} | |
78 | |
79 In this case the variable name is "i" and the expression is a simple value, | |
80 the number one. | |
81 The ":while" command starts a loop. The generic form is: > | |
82 | |
83 :while {condition} | |
84 : {statements} | |
85 :endwhile | |
86 | |
87 The statements until the matching ":endwhile" are executed for as long as the | |
88 condition is true. The condition used here is the expression "i < 5". This | |
89 is true when the variable i is smaller than five. | |
90 Note: | |
91 If you happen to write a while loop that keeps on running, you can | |
92 interrupt it by pressing CTRL-C (CTRL-Break on MS-Windows). | |
161 | 93 |
94 The ":echo" command prints its arguments. In this case the string "count is" | |
95 and the value of the variable i. Since i is one, this will print: | |
96 | |
97 count is 1 ~ | |
98 | |
99 Then there is the ":let i += 1" command. This does the same thing as | |
100 ":let i = i + 1". This adds one to the variable i and assigns the new value | |
101 to the same variable. | |
20856 | 102 Note: this is how it works in legacy Vim script, which is what we discuss in |
103 this file. In Vim9 script it's a bit different, see |usr_46.txt|. | |
161 | 104 |
105 The example was given to explain the commands, but would you really want to | |
11062 | 106 make such a loop, it can be written much more compact: > |
112 | 107 |
108 :for i in range(1, 4) | |
109 : echo "count is" i | |
110 :endfor | |
111 | |
161 | 112 We won't explain how |:for| and |range()| work until later. Follow the links |
113 if you are impatient. | |
112 | 114 |
7 | 115 |
16871 | 116 FOUR KINDS OF NUMBERS |
117 | |
24520 | 118 Numbers can be decimal, hexadecimal, octal or binary. |
119 | |
120 A hexadecimal number starts with "0x" or "0X". For example "0x1f" is decimal | |
121 31. | |
122 | |
123 An octal number starts with "0o", "0O" or a zero and another digit. "0o17" is | |
124 decimal 15. Using just a zero prefix is not supported in Vim9 script. | |
125 | |
126 A binary number starts with "0b" or "0B". For example "0b101" is decimal 5. | |
127 | |
128 A decimal number is just digits. Careful: don't put a zero before a decimal | |
129 number, it will be interpreted as an octal number in legacy script! | |
130 | |
131 The ":echo" command always prints decimal numbers. Example: > | |
7 | 132 |
23573 | 133 :echo 0x7f 0o36 |
7 | 134 < 127 30 ~ |
135 | |
16871 | 136 A number is made negative with a minus sign. This also works for hexadecimal, |
137 octal and binary numbers. A minus sign is also used for subtraction. Compare | |
138 this with the previous example: > | |
7 | 139 |
23573 | 140 :echo 0x7f -0o36 |
7 | 141 < 97 ~ |
142 | |
143 White space in an expression is ignored. However, it's recommended to use it | |
144 for separating items, to make the expression easier to read. For example, to | |
161 | 145 avoid the confusion with a negative number above, put a space between the |
146 minus sign and the following number: > | |
7 | 147 |
23573 | 148 :echo 0x7f - 0o36 |
7 | 149 |
150 ============================================================================== | |
151 *41.2* Variables | |
152 | |
153 A variable name consists of ASCII letters, digits and the underscore. It | |
154 cannot start with a digit. Valid variable names are: | |
155 | |
156 counter | |
157 _aap3 | |
158 very_long_variable_name_with_underscores | |
159 FuncLength | |
160 LENGTH | |
161 | |
162 Invalid names are "foo+bar" and "6var". | |
163 These variables are global. To see a list of currently defined variables | |
164 use this command: > | |
165 | |
166 :let | |
167 | |
168 You can use global variables everywhere. This also means that when the | |
169 variable "count" is used in one script file, it might also be used in another | |
170 file. This leads to confusion at least, and real problems at worst. To avoid | |
171 this, you can use a variable local to a script file by prepending "s:". For | |
172 example, one script contains this code: > | |
173 | |
174 :let s:count = 1 | |
175 :while s:count < 5 | |
176 : source other.vim | |
161 | 177 : let s:count += 1 |
7 | 178 :endwhile |
179 | |
180 Since "s:count" is local to this script, you can be sure that sourcing the | |
181 "other.vim" script will not change this variable. If "other.vim" also uses an | |
182 "s:count" variable, it will be a different copy, local to that script. More | |
183 about script-local variables here: |script-variable|. | |
184 | |
185 There are more kinds of variables, see |internal-variables|. The most often | |
186 used ones are: | |
187 | |
188 b:name variable local to a buffer | |
189 w:name variable local to a window | |
190 g:name global variable (also in a function) | |
191 v:name variable predefined by Vim | |
192 | |
193 | |
194 DELETING VARIABLES | |
195 | |
196 Variables take up memory and show up in the output of the ":let" command. To | |
197 delete a variable use the ":unlet" command. Example: > | |
198 | |
199 :unlet s:count | |
200 | |
201 This deletes the script-local variable "s:count" to free up the memory it | |
202 uses. If you are not sure if the variable exists, and don't want an error | |
203 message when it doesn't, append !: > | |
204 | |
205 :unlet! s:count | |
206 | |
207 When a script finishes, the local variables used there will not be | |
208 automatically freed. The next time the script executes, it can still use the | |
209 old value. Example: > | |
210 | |
211 :if !exists("s:call_count") | |
212 : let s:call_count = 0 | |
213 :endif | |
214 :let s:call_count = s:call_count + 1 | |
215 :echo "called" s:call_count "times" | |
216 | |
217 The "exists()" function checks if a variable has already been defined. Its | |
218 argument is the name of the variable you want to check. Not the variable | |
219 itself! If you would do this: > | |
220 | |
221 :if !exists(s:call_count) | |
222 | |
223 Then the value of s:call_count will be used as the name of the variable that | |
224 exists() checks. That's not what you want. | |
225 The exclamation mark ! negates a value. When the value was true, it | |
226 becomes false. When it was false, it becomes true. You can read it as "not". | |
227 Thus "if !exists()" can be read as "if not exists()". | |
161 | 228 What Vim calls true is anything that is not zero. Zero is false. |
856 | 229 Note: |
161 | 230 Vim automatically converts a string to a number when it is looking for |
231 a number. When using a string that doesn't start with a digit the | |
232 resulting number is zero. Thus look out for this: > | |
233 :if "true" | |
234 < The "true" will be interpreted as a zero, thus as false! | |
7 | 235 |
236 | |
237 STRING VARIABLES AND CONSTANTS | |
238 | |
239 So far only numbers were used for the variable value. Strings can be used as | |
161 | 240 well. Numbers and strings are the basic types of variables that Vim supports. |
241 The type is dynamic, it is set each time when assigning a value to the | |
242 variable with ":let". More about types in |41.8|. | |
7 | 243 To assign a string value to a variable, you need to use a string constant. |
244 There are two types of these. First the string in double quotes: > | |
245 | |
246 :let name = "peter" | |
247 :echo name | |
248 < peter ~ | |
249 | |
250 If you want to include a double quote inside the string, put a backslash in | |
251 front of it: > | |
252 | |
253 :let name = "\"peter\"" | |
254 :echo name | |
255 < "peter" ~ | |
256 | |
257 To avoid the need for a backslash, you can use a string in single quotes: > | |
258 | |
259 :let name = '"peter"' | |
260 :echo name | |
261 < "peter" ~ | |
262 | |
161 | 263 Inside a single-quote string all the characters are as they are. Only the |
264 single quote itself is special: you need to use two to get one. A backslash | |
265 is taken literally, thus you can't use it to change the meaning of the | |
7 | 266 character after it. |
267 In double-quote strings it is possible to use special characters. Here are | |
268 a few useful ones: | |
269 | |
270 \t <Tab> | |
271 \n <NL>, line break | |
272 \r <CR>, <Enter> | |
273 \e <Esc> | |
274 \b <BS>, backspace | |
275 \" " | |
276 \\ \, backslash | |
277 \<Esc> <Esc> | |
278 \<C-W> CTRL-W | |
279 | |
280 The last two are just examples. The "\<name>" form can be used to include | |
281 the special key "name". | |
282 See |expr-quote| for the full list of special items in a string. | |
283 | |
284 ============================================================================== | |
285 *41.3* Expressions | |
286 | |
287 Vim has a rich, yet simple way to handle expressions. You can read the | |
288 definition here: |expression-syntax|. Here we will show the most common | |
289 items. | |
290 The numbers, strings and variables mentioned above are expressions by | |
291 themselves. Thus everywhere an expression is expected, you can use a number, | |
292 string or variable. Other basic items in an expression are: | |
293 | |
294 $NAME environment variable | |
295 &name option | |
296 @r register | |
297 | |
298 Examples: > | |
299 | |
300 :echo "The value of 'tabstop' is" &ts | |
301 :echo "Your home directory is" $HOME | |
302 :if @a > 5 | |
303 | |
304 The &name form can be used to save an option value, set it to a new value, | |
305 do something and restore the old value. Example: > | |
306 | |
307 :let save_ic = &ic | |
308 :set noic | |
309 :/The Start/,$delete | |
310 :let &ic = save_ic | |
311 | |
312 This makes sure the "The Start" pattern is used with the 'ignorecase' option | |
161 | 313 off. Still, it keeps the value that the user had set. (Another way to do |
314 this would be to add "\C" to the pattern, see |/\C|.) | |
7 | 315 |
316 | |
317 MATHEMATICS | |
318 | |
319 It becomes more interesting if we combine these basic items. Let's start with | |
320 mathematics on numbers: | |
321 | |
322 a + b add | |
323 a - b subtract | |
324 a * b multiply | |
325 a / b divide | |
326 a % b modulo | |
327 | |
328 The usual precedence is used. Example: > | |
329 | |
330 :echo 10 + 5 * 2 | |
331 < 20 ~ | |
332 | |
2709 | 333 Grouping is done with parentheses. No surprises here. Example: > |
7 | 334 |
335 :echo (10 + 5) * 2 | |
336 < 30 ~ | |
337 | |
22171 | 338 Strings can be concatenated with ".." (see |expr6|). Example: > |
339 | |
340 :echo "foo" .. "bar" | |
7 | 341 < foobar ~ |
342 | |
343 When the ":echo" command gets multiple arguments, it separates them with a | |
344 space. In the example the argument is a single expression, thus no space is | |
345 inserted. | |
346 | |
347 Borrowed from the C language is the conditional expression: | |
348 | |
349 a ? b : c | |
350 | |
351 If "a" evaluates to true "b" is used, otherwise "c" is used. Example: > | |
352 | |
353 :let i = 4 | |
354 :echo i > 5 ? "i is big" : "i is small" | |
355 < i is small ~ | |
356 | |
357 The three parts of the constructs are always evaluated first, thus you could | |
358 see it work as: | |
359 | |
360 (a) ? (b) : (c) | |
361 | |
362 ============================================================================== | |
363 *41.4* Conditionals | |
364 | |
365 The ":if" commands executes the following statements, until the matching | |
366 ":endif", only when a condition is met. The generic form is: | |
367 | |
368 :if {condition} | |
369 {statements} | |
370 :endif | |
371 | |
372 Only when the expression {condition} evaluates to true (non-zero) will the | |
373 {statements} be executed. These must still be valid commands. If they | |
374 contain garbage, Vim won't be able to find the ":endif". | |
375 You can also use ":else". The generic form for this is: | |
376 | |
377 :if {condition} | |
378 {statements} | |
379 :else | |
380 {statements} | |
381 :endif | |
382 | |
383 The second {statements} is only executed if the first one isn't. | |
384 Finally, there is ":elseif": | |
385 | |
386 :if {condition} | |
387 {statements} | |
388 :elseif {condition} | |
389 {statements} | |
390 :endif | |
391 | |
392 This works just like using ":else" and then "if", but without the need for an | |
393 extra ":endif". | |
394 A useful example for your vimrc file is checking the 'term' option and | |
395 doing something depending upon its value: > | |
396 | |
397 :if &term == "xterm" | |
398 : " Do stuff for xterm | |
399 :elseif &term == "vt100" | |
400 : " Do stuff for a vt100 terminal | |
401 :else | |
402 : " Do something for other terminals | |
403 :endif | |
404 | |
405 | |
406 LOGIC OPERATIONS | |
407 | |
408 We already used some of them in the examples. These are the most often used | |
409 ones: | |
410 | |
411 a == b equal to | |
412 a != b not equal to | |
413 a > b greater than | |
414 a >= b greater than or equal to | |
415 a < b less than | |
416 a <= b less than or equal to | |
417 | |
418 The result is one if the condition is met and zero otherwise. An example: > | |
419 | |
161 | 420 :if v:version >= 700 |
7 | 421 : echo "congratulations" |
422 :else | |
423 : echo "you are using an old version, upgrade!" | |
424 :endif | |
425 | |
426 Here "v:version" is a variable defined by Vim, which has the value of the Vim | |
427 version. 600 is for version 6.0. Version 6.1 has the value 601. This is | |
428 very useful to write a script that works with multiple versions of Vim. | |
429 |v:version| | |
430 | |
431 The logic operators work both for numbers and strings. When comparing two | |
432 strings, the mathematical difference is used. This compares byte values, | |
433 which may not be right for some languages. | |
434 When comparing a string with a number, the string is first converted to a | |
435 number. This is a bit tricky, because when a string doesn't look like a | |
436 number, the number zero is used. Example: > | |
437 | |
438 :if 0 == "one" | |
439 : echo "yes" | |
440 :endif | |
441 | |
442 This will echo "yes", because "one" doesn't look like a number, thus it is | |
443 converted to the number zero. | |
444 | |
445 For strings there are two more items: | |
446 | |
447 a =~ b matches with | |
448 a !~ b does not match with | |
449 | |
450 The left item "a" is used as a string. The right item "b" is used as a | |
451 pattern, like what's used for searching. Example: > | |
452 | |
453 :if str =~ " " | |
454 : echo "str contains a space" | |
455 :endif | |
456 :if str !~ '\.$' | |
457 : echo "str does not end in a full stop" | |
458 :endif | |
459 | |
460 Notice the use of a single-quote string for the pattern. This is useful, | |
161 | 461 because backslashes would need to be doubled in a double-quote string and |
462 patterns tend to contain many backslashes. | |
7 | 463 |
464 The 'ignorecase' option is used when comparing strings. When you don't want | |
465 that, append "#" to match case and "?" to ignore case. Thus "==?" compares | |
466 two strings to be equal while ignoring case. And "!~#" checks if a pattern | |
467 doesn't match, also checking the case of letters. For the full table see | |
468 |expr-==|. | |
469 | |
470 | |
471 MORE LOOPING | |
472 | |
473 The ":while" command was already mentioned. Two more statements can be used | |
474 in between the ":while" and the ":endwhile": | |
475 | |
476 :continue Jump back to the start of the while loop; the | |
477 loop continues. | |
478 :break Jump forward to the ":endwhile"; the loop is | |
479 discontinued. | |
480 | |
481 Example: > | |
482 | |
483 :while counter < 40 | |
484 : call do_something() | |
485 : if skip_flag | |
486 : continue | |
487 : endif | |
488 : if finished_flag | |
489 : break | |
490 : endif | |
491 : sleep 50m | |
492 :endwhile | |
493 | |
494 The ":sleep" command makes Vim take a nap. The "50m" specifies fifty | |
495 milliseconds. Another example is ":sleep 4", which sleeps for four seconds. | |
496 | |
161 | 497 Even more looping can be done with the ":for" command, see below in |41.8|. |
498 | |
7 | 499 ============================================================================== |
500 *41.5* Executing an expression | |
501 | |
502 So far the commands in the script were executed by Vim directly. The | |
503 ":execute" command allows executing the result of an expression. This is a | |
504 very powerful way to build commands and execute them. | |
505 An example is to jump to a tag, which is contained in a variable: > | |
506 | |
22171 | 507 :execute "tag " .. tag_name |
508 | |
509 The ".." is used to concatenate the string "tag " with the value of variable | |
7 | 510 "tag_name". Suppose "tag_name" has the value "get_cmd", then the command that |
511 will be executed is: > | |
512 | |
513 :tag get_cmd | |
514 | |
515 The ":execute" command can only execute colon commands. The ":normal" command | |
516 executes Normal mode commands. However, its argument is not an expression but | |
517 the literal command characters. Example: > | |
518 | |
519 :normal gg=G | |
520 | |
521 This jumps to the first line and formats all lines with the "=" operator. | |
522 To make ":normal" work with an expression, combine ":execute" with it. | |
523 Example: > | |
524 | |
22171 | 525 :execute "normal " .. normal_commands |
7 | 526 |
527 The variable "normal_commands" must contain the Normal mode commands. | |
528 Make sure that the argument for ":normal" is a complete command. Otherwise | |
529 Vim will run into the end of the argument and abort the command. For example, | |
530 if you start Insert mode, you must leave Insert mode as well. This works: > | |
531 | |
532 :execute "normal Inew text \<Esc>" | |
533 | |
534 This inserts "new text " in the current line. Notice the use of the special | |
535 key "\<Esc>". This avoids having to enter a real <Esc> character in your | |
536 script. | |
537 | |
161 | 538 If you don't want to execute a string but evaluate it to get its expression |
539 value, you can use the eval() function: > | |
540 | |
541 :let optname = "path" | |
22171 | 542 :let optval = eval('&' .. optname) |
161 | 543 |
544 A "&" character is prepended to "path", thus the argument to eval() is | |
545 "&path". The result will then be the value of the 'path' option. | |
546 The same thing can be done with: > | |
22171 | 547 :exe 'let optval = &' .. optname |
161 | 548 |
7 | 549 ============================================================================== |
550 *41.6* Using functions | |
551 | |
552 Vim defines many functions and provides a large amount of functionality that | |
553 way. A few examples will be given in this section. You can find the whole | |
554 list here: |functions|. | |
555 | |
556 A function is called with the ":call" command. The parameters are passed in | |
2709 | 557 between parentheses separated by commas. Example: > |
7 | 558 |
559 :call search("Date: ", "W") | |
560 | |
561 This calls the search() function, with arguments "Date: " and "W". The | |
562 search() function uses its first argument as a search pattern and the second | |
563 one as flags. The "W" flag means the search doesn't wrap around the end of | |
564 the file. | |
565 | |
566 A function can be called in an expression. Example: > | |
567 | |
568 :let line = getline(".") | |
569 :let repl = substitute(line, '\a', "*", "g") | |
570 :call setline(".", repl) | |
571 | |
161 | 572 The getline() function obtains a line from the current buffer. Its argument |
573 is a specification of the line number. In this case "." is used, which means | |
574 the line where the cursor is. | |
7 | 575 The substitute() function does something similar to the ":substitute" |
576 command. The first argument is the string on which to perform the | |
577 substitution. The second argument is the pattern, the third the replacement | |
578 string. Finally, the last arguments are the flags. | |
579 The setline() function sets the line, specified by the first argument, to a | |
580 new string, the second argument. In this example the line under the cursor is | |
581 replaced with the result of the substitute(). Thus the effect of the three | |
582 statements is equal to: > | |
583 | |
584 :substitute/\a/*/g | |
585 | |
586 Using the functions becomes more interesting when you do more work before and | |
587 after the substitute() call. | |
588 | |
589 | |
590 FUNCTIONS *function-list* | |
591 | |
592 There are many functions. We will mention them here, grouped by what they are | |
593 used for. You can find an alphabetical list here: |functions|. Use CTRL-] on | |
594 the function name to jump to detailed help on it. | |
595 | |
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
|
596 String manipulation: *string-functions* |
16235
219c58b3879c
patch 8.1.1122: char2nr() does not handle composing characters
Bram Moolenaar <Bram@vim.org>
parents:
16208
diff
changeset
|
597 nr2char() get a character by its number value |
219c58b3879c
patch 8.1.1122: char2nr() does not handle composing characters
Bram Moolenaar <Bram@vim.org>
parents:
16208
diff
changeset
|
598 list2str() get a character string from a list of numbers |
219c58b3879c
patch 8.1.1122: char2nr() does not handle composing characters
Bram Moolenaar <Bram@vim.org>
parents:
16208
diff
changeset
|
599 char2nr() get number value of a character |
219c58b3879c
patch 8.1.1122: char2nr() does not handle composing characters
Bram Moolenaar <Bram@vim.org>
parents:
16208
diff
changeset
|
600 str2list() get list of numbers from a string |
1620 | 601 str2nr() convert a string to a Number |
602 str2float() convert a string to a Float | |
824 | 603 printf() format a string according to % items |
7 | 604 escape() escape characters in a string with a '\' |
1620 | 605 shellescape() escape a string for use with a shell command |
606 fnameescape() escape a file name for use with a Vim command | |
824 | 607 tr() translate characters from one set to another |
7 | 608 strtrans() translate a string to make it printable |
609 tolower() turn a string to lowercase | |
610 toupper() turn a string to uppercase | |
21973
85add08e6a2d
patch 8.2.1536: cannot get the class of a character; emoji widths are wrong
Bram Moolenaar <Bram@vim.org>
parents:
21971
diff
changeset
|
611 charclass() class of a character |
7 | 612 match() position where a pattern matches in a string |
613 matchend() position where a pattern match ends in a string | |
22232
f22acf6472da
patch 8.2.1665: cannot do fuzzy string matching
Bram Moolenaar <Bram@vim.org>
parents:
22171
diff
changeset
|
614 matchfuzzy() fuzzy matches a string in a list of strings |
22355
0491b9cafd44
patch 8.2.1726: fuzzy matching only works on strings
Bram Moolenaar <Bram@vim.org>
parents:
22232
diff
changeset
|
615 matchfuzzypos() fuzzy matches a string in a list of strings |
7 | 616 matchstr() match of a pattern in a string |
9644
9f7bcc2c3b97
commit https://github.com/vim/vim/commit/6f1d9a096bf22d50c727dca73abbfb8e3ff55176
Christian Brabandt <cb@256bit.org>
parents:
9464
diff
changeset
|
617 matchstrpos() match and positions of a pattern in a string |
824 | 618 matchlist() like matchstr() and also return submatches |
7 | 619 stridx() first index of a short string in a long string |
620 strridx() last index of a short string in a long string | |
5618 | 621 strlen() length of a string in bytes |
24130
c3d1f65365c4
patch 8.2.2606: strchars() defaults to counting composing characters
Bram Moolenaar <Bram@vim.org>
parents:
23931
diff
changeset
|
622 strcharlen() length of a string in characters |
c3d1f65365c4
patch 8.2.2606: strchars() defaults to counting composing characters
Bram Moolenaar <Bram@vim.org>
parents:
23931
diff
changeset
|
623 strchars() number of characters in a string |
5618 | 624 strwidth() size of string when displayed |
625 strdisplaywidth() size of string when displayed, deals with tabs | |
21971
0bc43a704f56
patch 8.2.1535: it is not possible to specify cell widths of characters
Bram Moolenaar <Bram@vim.org>
parents:
21825
diff
changeset
|
626 setcellwidths() set character cell width overrides |
7 | 627 substitute() substitute a pattern match with a string |
2908 | 628 submatch() get a specific match in ":s" and substitute() |
9286
64035abb986b
commit https://github.com/vim/vim/commit/c95a302a4c42ec8230473cd4a5e0064d0a143aa8
Christian Brabandt <cb@256bit.org>
parents:
9227
diff
changeset
|
629 strpart() get part of a string using byte index |
64035abb986b
commit https://github.com/vim/vim/commit/c95a302a4c42ec8230473cd4a5e0064d0a143aa8
Christian Brabandt <cb@256bit.org>
parents:
9227
diff
changeset
|
630 strcharpart() get part of a string using char index |
23604
1816ea68c022
patch 8.2.2344: using inclusive index for slice is not always desired
Bram Moolenaar <Bram@vim.org>
parents:
23602
diff
changeset
|
631 slice() take a slice of a string, using char index in |
1816ea68c022
patch 8.2.2344: using inclusive index for slice is not always desired
Bram Moolenaar <Bram@vim.org>
parents:
23602
diff
changeset
|
632 Vim9 script |
9286
64035abb986b
commit https://github.com/vim/vim/commit/c95a302a4c42ec8230473cd4a5e0064d0a143aa8
Christian Brabandt <cb@256bit.org>
parents:
9227
diff
changeset
|
633 strgetchar() get character from a string using char index |
7 | 634 expand() expand special keywords |
17020
1841c03a9b5e
patch 8.1.1510: a plugin cannot easily expand a command like done internally
Bram Moolenaar <Bram@vim.org>
parents:
16871
diff
changeset
|
635 expandcmd() expand a command like done for `:edit` |
7 | 636 iconv() convert text from one encoding to another |
824 | 637 byteidx() byte index of a character in a string |
5618 | 638 byteidxcomp() like byteidx() but count composing characters |
23380
2351b40af967
patch 8.2.2233: cannot convert a byte index into a character index
Bram Moolenaar <Bram@vim.org>
parents:
23305
diff
changeset
|
639 charidx() character index of a byte in a string |
824 | 640 repeat() repeat a string multiple times |
641 eval() evaluate a string expression | |
9464
be72f4201a1d
commit https://github.com/vim/vim/commit/063b9d15abea041a5bfff3ffc4e219e26fd1d4fa
Christian Brabandt <cb@256bit.org>
parents:
9319
diff
changeset
|
642 execute() execute an Ex command and get the output |
16871 | 643 win_execute() like execute() but in a specified window |
15068 | 644 trim() trim characters from a string |
21989
52e970719f4b
patch 8.2.1544: cannot translate messages in a Vim script
Bram Moolenaar <Bram@vim.org>
parents:
21973
diff
changeset
|
645 gettext() lookup message translation |
7 | 646 |
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
|
647 List manipulation: *list-functions* |
112 | 648 get() get an item without error for wrong index |
649 len() number of items in a List | |
650 empty() check if List is empty | |
651 insert() insert an item somewhere in a List | |
652 add() append an item to a List | |
653 extend() append a List to a List | |
23588
510088f8c66f
patch 8.2.2336: Vim9: not possible to extend dictionary with different type
Bram Moolenaar <Bram@vim.org>
parents:
23573
diff
changeset
|
654 extendnew() make a new List and append items |
112 | 655 remove() remove one or more items from a List |
656 copy() make a shallow copy of a List | |
657 deepcopy() make a full copy of a List | |
658 filter() remove selected items from a List | |
659 map() change each List item | |
22844
36fc73078bce
patch 8.2.1969: Vim9: map() may change the list or dict item type
Bram Moolenaar <Bram@vim.org>
parents:
22355
diff
changeset
|
660 mapnew() make a new List with changed items |
20687
770a8e9c4781
patch 8.2.0897: list of functions in patched version is outdated
Bram Moolenaar <Bram@vim.org>
parents:
20643
diff
changeset
|
661 reduce() reduce a List to a value |
23604
1816ea68c022
patch 8.2.2344: using inclusive index for slice is not always desired
Bram Moolenaar <Bram@vim.org>
parents:
23602
diff
changeset
|
662 slice() take a slice of a List |
112 | 663 sort() sort a List |
664 reverse() reverse the order of a List | |
5763 | 665 uniq() remove copies of repeated adjacent items |
112 | 666 split() split a String into a List |
667 join() join List items into a String | |
824 | 668 range() return a List with a sequence of numbers |
112 | 669 string() String representation of a List |
670 call() call a function with List as arguments | |
323 | 671 index() index of a value in a List |
112 | 672 max() maximum value in a List |
673 min() minimum value in a List | |
674 count() count number of times a value appears in a List | |
824 | 675 repeat() repeat a List multiple times |
20766
821925509d8c
patch 8.2.0935: flattening a list with existing code is slow
Bram Moolenaar <Bram@vim.org>
parents:
20743
diff
changeset
|
676 flatten() flatten a List |
23816
525c9e218c69
patch 8.2.2449: Vim9: flatten() always changes the list type
Bram Moolenaar <Bram@vim.org>
parents:
23666
diff
changeset
|
677 flattennew() flatten a copy of a List |
112 | 678 |
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
|
679 Dictionary manipulation: *dict-functions* |
323 | 680 get() get an entry without an error for a wrong key |
112 | 681 len() number of entries in a Dictionary |
682 has_key() check whether a key appears in a Dictionary | |
683 empty() check if Dictionary is empty | |
684 remove() remove an entry from a Dictionary | |
685 extend() add entries from one Dictionary to another | |
23588
510088f8c66f
patch 8.2.2336: Vim9: not possible to extend dictionary with different type
Bram Moolenaar <Bram@vim.org>
parents:
23573
diff
changeset
|
686 extendnew() make a new Dictionary and append items |
112 | 687 filter() remove selected entries from a Dictionary |
688 map() change each Dictionary entry | |
22844
36fc73078bce
patch 8.2.1969: Vim9: map() may change the list or dict item type
Bram Moolenaar <Bram@vim.org>
parents:
22355
diff
changeset
|
689 mapnew() make a new Dictionary with changed items |
112 | 690 keys() get List of Dictionary keys |
691 values() get List of Dictionary values | |
692 items() get List of Dictionary key-value pairs | |
693 copy() make a shallow copy of a Dictionary | |
694 deepcopy() make a full copy of a Dictionary | |
695 string() String representation of a Dictionary | |
696 max() maximum value in a Dictionary | |
697 min() minimum value in a Dictionary | |
698 count() count number of times a value appears | |
699 | |
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
|
700 Floating point computation: *float-functions* |
1620 | 701 float2nr() convert Float to Number |
702 abs() absolute value (also works for Number) | |
703 round() round off | |
704 ceil() round up | |
705 floor() round down | |
706 trunc() remove value after decimal point | |
5618 | 707 fmod() remainder of division |
708 exp() exponential | |
709 log() natural logarithm (logarithm to base e) | |
1620 | 710 log10() logarithm to base 10 |
711 pow() value of x to the exponent y | |
712 sqrt() square root | |
713 sin() sine | |
714 cos() cosine | |
2725 | 715 tan() tangent |
716 asin() arc sine | |
717 acos() arc cosine | |
1620 | 718 atan() arc tangent |
2725 | 719 atan2() arc tangent |
720 sinh() hyperbolic sine | |
721 cosh() hyperbolic cosine | |
722 tanh() hyperbolic tangent | |
20687
770a8e9c4781
patch 8.2.0897: list of functions in patched version is outdated
Bram Moolenaar <Bram@vim.org>
parents:
20643
diff
changeset
|
723 isinf() check for infinity |
9286
64035abb986b
commit https://github.com/vim/vim/commit/c95a302a4c42ec8230473cd4a5e0064d0a143aa8
Christian Brabandt <cb@256bit.org>
parents:
9227
diff
changeset
|
724 isnan() check for not a number |
1620 | 725 |
3237 | 726 Other computation: *bitwise-function* |
727 and() bitwise AND | |
728 invert() bitwise invert | |
729 or() bitwise OR | |
730 xor() bitwise XOR | |
5618 | 731 sha256() SHA-256 hash |
20687
770a8e9c4781
patch 8.2.0897: list of functions in patched version is outdated
Bram Moolenaar <Bram@vim.org>
parents:
20643
diff
changeset
|
732 rand() get a pseudo-random number |
770a8e9c4781
patch 8.2.0897: list of functions in patched version is outdated
Bram Moolenaar <Bram@vim.org>
parents:
20643
diff
changeset
|
733 srand() initialize seed used by rand() |
3237 | 734 |
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
|
735 Variables: *var-functions* |
23594
d3e064f54890
patch 8.2.2339: cannot get the type of a value as a string
Bram Moolenaar <Bram@vim.org>
parents:
23588
diff
changeset
|
736 type() type of a variable as a number |
d3e064f54890
patch 8.2.2339: cannot get the type of a value as a string
Bram Moolenaar <Bram@vim.org>
parents:
23588
diff
changeset
|
737 typename() type of a variable as text |
824 | 738 islocked() check if a variable is locked |
11062 | 739 funcref() get a Funcref for a function reference |
824 | 740 function() get a Funcref for a function name |
741 getbufvar() get a variable value from a specific buffer | |
742 setbufvar() set a variable in a specific buffer | |
831 | 743 getwinvar() get a variable from specific window |
2207
b17bbfa96fa0
Add the settabvar() and gettabvar() functions.
Bram Moolenaar <bram@vim.org>
parents:
2154
diff
changeset
|
744 gettabvar() get a variable from specific tab page |
831 | 745 gettabwinvar() get a variable from specific window & tab page |
824 | 746 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
|
747 settabvar() set a variable in a specific tab page |
831 | 748 settabwinvar() set a variable in a specific window & tab page |
824 | 749 garbagecollect() possibly free memory |
750 | |
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
|
751 Cursor and mark position: *cursor-functions* *mark-functions* |
7 | 752 col() column number of the cursor or a mark |
753 virtcol() screen column of the cursor or a mark | |
754 line() line number of the cursor or mark | |
755 wincol() window column number of the cursor | |
756 winline() window line number of the cursor | |
757 cursor() position the cursor at a line/column | |
5618 | 758 screencol() get screen column of the cursor |
759 screenrow() get screen row of the cursor | |
17292
8a095d343c59
patch 8.1.1645: cannot use a popup window for a balloon
Bram Moolenaar <Bram@vim.org>
parents:
17257
diff
changeset
|
760 screenpos() screen row and col of a text character |
5968 | 761 getcurpos() get position of the cursor |
824 | 762 getpos() get position of cursor, mark, etc. |
763 setpos() set position of cursor, mark, etc. | |
20615
8eed1e9389bb
patch 8.2.0861: cannot easily get all the current marks
Bram Moolenaar <Bram@vim.org>
parents:
19721
diff
changeset
|
764 getmarklist() list of global/local marks |
824 | 765 byte2line() get line number at a specific byte count |
766 line2byte() byte count at a specific line | |
767 diff_filler() get the number of filler lines above a line | |
5618 | 768 screenattr() get attribute at a screen line/row |
769 screenchar() get character code at a screen line/row | |
16133
eb087f8a26a8
patch 8.1.1071: cannot get composing characters from the screen
Bram Moolenaar <Bram@vim.org>
parents:
16127
diff
changeset
|
770 screenchars() get character codes at a screen line/row |
eb087f8a26a8
patch 8.1.1071: cannot get composing characters from the screen
Bram Moolenaar <Bram@vim.org>
parents:
16127
diff
changeset
|
771 screenstring() get string of characters at a screen line/row |
23563
87671ccc6c6b
patch 8.2.2324: not easy to get mark en cursor posotion by character count
Bram Moolenaar <Bram@vim.org>
parents:
23380
diff
changeset
|
772 charcol() character number of the cursor or a mark |
87671ccc6c6b
patch 8.2.2324: not easy to get mark en cursor posotion by character count
Bram Moolenaar <Bram@vim.org>
parents:
23380
diff
changeset
|
773 getcharpos() get character position of cursor, mark, etc. |
87671ccc6c6b
patch 8.2.2324: not easy to get mark en cursor posotion by character count
Bram Moolenaar <Bram@vim.org>
parents:
23380
diff
changeset
|
774 setcharpos() set character position of cursor, mark, etc. |
87671ccc6c6b
patch 8.2.2324: not easy to get mark en cursor posotion by character count
Bram Moolenaar <Bram@vim.org>
parents:
23380
diff
changeset
|
775 getcursorcharpos() get character position of the cursor |
87671ccc6c6b
patch 8.2.2324: not easy to get mark en cursor posotion by character count
Bram Moolenaar <Bram@vim.org>
parents:
23380
diff
changeset
|
776 setcursorcharpos() set character position of the cursor |
824 | 777 |
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
|
778 Working with text in the current buffer: *text-functions* |
161 | 779 getline() get a line or list of lines from the buffer |
7 | 780 setline() replace a line in the buffer |
161 | 781 append() append line or list of lines in the buffer |
7 | 782 indent() indent of a specific line |
783 cindent() indent according to C indenting | |
784 lispindent() indent according to Lisp indenting | |
785 nextnonblank() find next non-blank line | |
786 prevnonblank() find previous non-blank line | |
787 search() find a match for a pattern | |
667 | 788 searchpos() find a match for a pattern |
20687
770a8e9c4781
patch 8.2.0897: list of functions in patched version is outdated
Bram Moolenaar <Bram@vim.org>
parents:
20643
diff
changeset
|
789 searchcount() get number of matches before/after the cursor |
7 | 790 searchpair() find the other end of a start/skip/end |
667 | 791 searchpairpos() find the other end of a start/skip/end |
824 | 792 searchdecl() search for the declaration of a name |
9286
64035abb986b
commit https://github.com/vim/vim/commit/c95a302a4c42ec8230473cd4a5e0064d0a143aa8
Christian Brabandt <cb@256bit.org>
parents:
9227
diff
changeset
|
793 getcharsearch() return character search information |
64035abb986b
commit https://github.com/vim/vim/commit/c95a302a4c42ec8230473cd4a5e0064d0a143aa8
Christian Brabandt <cb@256bit.org>
parents:
9227
diff
changeset
|
794 setcharsearch() set character search information |
7 | 795 |
17257
cb0ca75f0c26
patch 8.1.1628: popup window functions not in list of functions
Bram Moolenaar <Bram@vim.org>
parents:
17020
diff
changeset
|
796 Working with text in another buffer: |
cb0ca75f0c26
patch 8.1.1628: popup window functions not in list of functions
Bram Moolenaar <Bram@vim.org>
parents:
17020
diff
changeset
|
797 getbufline() get a list of lines from the specified buffer |
cb0ca75f0c26
patch 8.1.1628: popup window functions not in list of functions
Bram Moolenaar <Bram@vim.org>
parents:
17020
diff
changeset
|
798 setbufline() replace a line in the specified buffer |
cb0ca75f0c26
patch 8.1.1628: popup window functions not in list of functions
Bram Moolenaar <Bram@vim.org>
parents:
17020
diff
changeset
|
799 appendbufline() append a list of lines in the specified buffer |
cb0ca75f0c26
patch 8.1.1628: popup window functions not in list of functions
Bram Moolenaar <Bram@vim.org>
parents:
17020
diff
changeset
|
800 deletebufline() delete lines from a specified buffer |
cb0ca75f0c26
patch 8.1.1628: popup window functions not in list of functions
Bram Moolenaar <Bram@vim.org>
parents:
17020
diff
changeset
|
801 |
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
|
802 *system-functions* *file-functions* |
7 | 803 System functions and manipulation of files: |
804 glob() expand wildcards | |
805 globpath() expand wildcards in a number of directories | |
9286
64035abb986b
commit https://github.com/vim/vim/commit/c95a302a4c42ec8230473cd4a5e0064d0a143aa8
Christian Brabandt <cb@256bit.org>
parents:
9227
diff
changeset
|
806 glob2regpat() convert a glob pattern into a search pattern |
824 | 807 findfile() find a file in a list of directories |
808 finddir() find a directory in a list of directories | |
7 | 809 resolve() find out where a shortcut points to |
810 fnamemodify() modify a file name | |
824 | 811 pathshorten() shorten directory names in a path |
812 simplify() simplify a path without changing its meaning | |
7 | 813 executable() check if an executable program exists |
5814 | 814 exepath() full path of an executable program |
7 | 815 filereadable() check if a file can be read |
816 filewritable() check if a file can be written to | |
824 | 817 getfperm() get the permissions of a file |
9286
64035abb986b
commit https://github.com/vim/vim/commit/c95a302a4c42ec8230473cd4a5e0064d0a143aa8
Christian Brabandt <cb@256bit.org>
parents:
9227
diff
changeset
|
818 setfperm() set the permissions of a file |
824 | 819 getftype() get the kind of a file |
7 | 820 isdirectory() check if a directory exists |
821 getfsize() get the size of a file | |
824 | 822 getcwd() get the current working directory |
16427
8c3a1bd270bb
patch 8.1.1218: cannot set a directory for a tab page
Bram Moolenaar <Bram@vim.org>
parents:
16267
diff
changeset
|
823 haslocaldir() check if current window used |:lcd| or |:tcd| |
7 | 824 tempname() get the name of a temporary file |
824 | 825 mkdir() create a new directory |
16576
bcc343175103
patch 8.1.1291: not easy to change directory and restore
Bram Moolenaar <Bram@vim.org>
parents:
16517
diff
changeset
|
826 chdir() change current working directory |
7 | 827 delete() delete a file |
828 rename() rename a file | |
5814 | 829 system() get the result of a shell command as a string |
830 systemlist() get the result of a shell command as a list | |
16604
1e0a5f09fdf1
patch 8.1.1305: there is no easy way to manipulate environment variables
Bram Moolenaar <Bram@vim.org>
parents:
16576
diff
changeset
|
831 environ() get all environment variables |
1e0a5f09fdf1
patch 8.1.1305: there is no easy way to manipulate environment variables
Bram Moolenaar <Bram@vim.org>
parents:
16576
diff
changeset
|
832 getenv() get one environment variable |
1e0a5f09fdf1
patch 8.1.1305: there is no easy way to manipulate environment variables
Bram Moolenaar <Bram@vim.org>
parents:
16576
diff
changeset
|
833 setenv() set an environment variable |
7 | 834 hostname() name of the system |
158 | 835 readfile() read a file into a List of lines |
23602
7b3317e959e3
patch 8.2.2343: Vim9: return type of readfile() is any
Bram Moolenaar <Bram@vim.org>
parents:
23594
diff
changeset
|
836 readblob() read a file into a Blob |
16267 | 837 readdir() get a List of file names in a directory |
20643
c2beb6baa42c
patch 8.2.0875: getting attributes for directory entries is slow
Bram Moolenaar <Bram@vim.org>
parents:
20615
diff
changeset
|
838 readdirex() get a List of file information in a directory |
15729 | 839 writefile() write a List of lines or Blob into a file |
7 | 840 |
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
|
841 Date and Time: *date-functions* *time-functions* |
824 | 842 getftime() get last modification time of a file |
843 localtime() get current time in seconds | |
844 strftime() convert time to a string | |
18669
9007e9896303
patch 8.1.2326: cannot parse a date/time string
Bram Moolenaar <Bram@vim.org>
parents:
18639
diff
changeset
|
845 strptime() convert a date/time string to time |
824 | 846 reltime() get the current or elapsed time accurately |
847 reltimestr() convert reltime() result to a string | |
8876
47f17f66da3d
commit https://github.com/vim/vim/commit/03413f44167c4b5cd0012def9bb331e2518c83cf
Christian Brabandt <cb@256bit.org>
parents:
8795
diff
changeset
|
848 reltimefloat() convert reltime() result to a Float |
824 | 849 |
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
|
850 *buffer-functions* *window-functions* *arg-functions* |
7 | 851 Buffers, windows and the argument list: |
852 argc() number of entries in the argument list | |
853 argidx() current position in the argument list | |
5942 | 854 arglistid() get id of the argument list |
7 | 855 argv() get one entry from the argument list |
17257
cb0ca75f0c26
patch 8.1.1628: popup window functions not in list of functions
Bram Moolenaar <Bram@vim.org>
parents:
17020
diff
changeset
|
856 bufadd() add a file to the list of buffers |
7 | 857 bufexists() check if a buffer exists |
858 buflisted() check if a buffer exists and is listed | |
17257
cb0ca75f0c26
patch 8.1.1628: popup window functions not in list of functions
Bram Moolenaar <Bram@vim.org>
parents:
17020
diff
changeset
|
859 bufload() ensure a buffer is loaded |
7 | 860 bufloaded() check if a buffer exists and is loaded |
861 bufname() get the name of a specific buffer | |
862 bufnr() get the buffer number of a specific buffer | |
824 | 863 tabpagebuflist() return List of buffers in a tab page |
864 tabpagenr() get the number of a tab page | |
865 tabpagewinnr() like winnr() for a specified tab page | |
7 | 866 winnr() get the window number for the current window |
9227
ecb621205ed1
commit https://github.com/vim/vim/commit/82af8710bf8d1caeeceafb1370a052cb7d92f076
Christian Brabandt <cb@256bit.org>
parents:
8876
diff
changeset
|
867 bufwinid() get the window ID of a specific buffer |
7 | 868 bufwinnr() get the window number of a specific buffer |
869 winbufnr() get the buffer number of a specific window | |
16638
4790302965fc
patch 8.1.1321: no docs or tests for listener functions
Bram Moolenaar <Bram@vim.org>
parents:
16610
diff
changeset
|
870 listener_add() add a callback to listen to changes |
16808 | 871 listener_flush() invoke listener callbacks |
16638
4790302965fc
patch 8.1.1321: no docs or tests for listener functions
Bram Moolenaar <Bram@vim.org>
parents:
16610
diff
changeset
|
872 listener_remove() remove a listener callback |
9286
64035abb986b
commit https://github.com/vim/vim/commit/c95a302a4c42ec8230473cd4a5e0064d0a143aa8
Christian Brabandt <cb@256bit.org>
parents:
9227
diff
changeset
|
873 win_findbuf() find windows containing a buffer |
64035abb986b
commit https://github.com/vim/vim/commit/c95a302a4c42ec8230473cd4a5e0064d0a143aa8
Christian Brabandt <cb@256bit.org>
parents:
9227
diff
changeset
|
874 win_getid() get window ID of a window |
20687
770a8e9c4781
patch 8.2.0897: list of functions in patched version is outdated
Bram Moolenaar <Bram@vim.org>
parents:
20643
diff
changeset
|
875 win_gettype() get type of window |
9286
64035abb986b
commit https://github.com/vim/vim/commit/c95a302a4c42ec8230473cd4a5e0064d0a143aa8
Christian Brabandt <cb@256bit.org>
parents:
9227
diff
changeset
|
876 win_gotoid() go to window with ID |
64035abb986b
commit https://github.com/vim/vim/commit/c95a302a4c42ec8230473cd4a5e0064d0a143aa8
Christian Brabandt <cb@256bit.org>
parents:
9227
diff
changeset
|
877 win_id2tabwin() get tab and window nr from window ID |
64035abb986b
commit https://github.com/vim/vim/commit/c95a302a4c42ec8230473cd4a5e0064d0a143aa8
Christian Brabandt <cb@256bit.org>
parents:
9227
diff
changeset
|
878 win_id2win() get window nr from window ID |
20687
770a8e9c4781
patch 8.2.0897: list of functions in patched version is outdated
Bram Moolenaar <Bram@vim.org>
parents:
20643
diff
changeset
|
879 win_splitmove() move window to a split of another window |
9858
3e96d9ed2ca1
commit https://github.com/vim/vim/commit/b5ae48e9ffd3b8eb6ca4057de11f1bddcde8ce6f
Christian Brabandt <cb@256bit.org>
parents:
9644
diff
changeset
|
880 getbufinfo() get a list with buffer information |
3e96d9ed2ca1
commit https://github.com/vim/vim/commit/b5ae48e9ffd3b8eb6ca4057de11f1bddcde8ce6f
Christian Brabandt <cb@256bit.org>
parents:
9644
diff
changeset
|
881 gettabinfo() get a list with tab page information |
3e96d9ed2ca1
commit https://github.com/vim/vim/commit/b5ae48e9ffd3b8eb6ca4057de11f1bddcde8ce6f
Christian Brabandt <cb@256bit.org>
parents:
9644
diff
changeset
|
882 getwininfo() get a list with window information |
13280
fbda23eb0996
patch 8.0.1514: getting the list of changes is not easy
Christian Brabandt <cb@256bit.org>
parents:
13246
diff
changeset
|
883 getchangelist() get a list of change list entries |
13246
dd3b2ecf91f6
patch 8.0.1497: getting the jump list requires parsing the output of :jumps
Christian Brabandt <cb@256bit.org>
parents:
13051
diff
changeset
|
884 getjumplist() get a list of jump list entries |
14637 | 885 swapinfo() information about a swap file |
15068 | 886 swapname() get the swap file path of a buffer |
824 | 887 |
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
|
888 Command line: *command-line-functions* |
824 | 889 getcmdline() get the current command line |
890 getcmdpos() get position of the cursor in the command line | |
891 setcmdpos() set position of the cursor in the command line | |
892 getcmdtype() return the current command-line type | |
6153 | 893 getcmdwintype() return the current command-line window type |
9644
9f7bcc2c3b97
commit https://github.com/vim/vim/commit/6f1d9a096bf22d50c727dca73abbfb8e3ff55176
Christian Brabandt <cb@256bit.org>
parents:
9464
diff
changeset
|
894 getcompletion() list of command-line completion matches |
23853
a9ed31ab85c3
patch 8.2.2468: not easy to get the full command name from a shortened one
Bram Moolenaar <Bram@vim.org>
parents:
23816
diff
changeset
|
895 fullcommand() get full command name |
824 | 896 |
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
|
897 Quickfix and location lists: *quickfix-functions* |
824 | 898 getqflist() list of quickfix errors |
899 setqflist() modify a quickfix list | |
900 getloclist() list of location list items | |
901 setloclist() modify a location list | |
902 | |
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
|
903 Insert mode completion: *completion-functions* |
824 | 904 complete() set found matches |
905 complete_add() add to found matches | |
906 complete_check() check if completion should be aborted | |
16127
0375e54f0adc
patch 8.1.1068: cannot get all the information about current completion
Bram Moolenaar <Bram@vim.org>
parents:
15729
diff
changeset
|
907 complete_info() get current completion information |
824 | 908 pumvisible() check if the popup menu is displayed |
18186 | 909 pum_getpos() position and size of popup menu if visible |
7 | 910 |
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
|
911 Folding: *folding-functions* |
7 | 912 foldclosed() check for a closed fold at a specific line |
913 foldclosedend() like foldclosed() but return the last line | |
914 foldlevel() check for the fold level at a specific line | |
915 foldtext() generate the line displayed for a closed fold | |
824 | 916 foldtextresult() get the text displayed for a closed fold |
917 | |
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
|
918 Syntax and highlighting: *syntax-functions* *highlighting-functions* |
1326 | 919 clearmatches() clear all matches defined by |matchadd()| and |
920 the |:match| commands | |
921 getmatches() get all matches defined by |matchadd()| and | |
922 the |:match| commands | |
7 | 923 hlexists() check if a highlight group exists |
924 hlID() get ID of a highlight group | |
925 synID() get syntax ID at a specific position | |
926 synIDattr() get a specific attribute of a syntax ID | |
927 synIDtrans() get translated syntax ID | |
2642 | 928 synstack() get list of syntax IDs at a specific position |
2662 | 929 synconcealed() get info about concealing |
824 | 930 diff_hlID() get highlight ID for diff mode at a position |
1326 | 931 matchadd() define a pattern to highlight (a "match") |
5979 | 932 matchaddpos() define a list of positions to highlight |
824 | 933 matcharg() get info about |:match| arguments |
1326 | 934 matchdelete() delete a match defined by |matchadd()| or a |
935 |:match| command | |
936 setmatches() restore a list of matches saved by | |
937 |getmatches()| | |
824 | 938 |
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
|
939 Spelling: *spell-functions* |
824 | 940 spellbadword() locate badly spelled word at or after cursor |
941 spellsuggest() return suggested spelling corrections | |
942 soundfold() return the sound-a-like equivalent of a word | |
7 | 943 |
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
|
944 History: *history-functions* |
7 | 945 histadd() add an item to a history |
946 histdel() delete an item from a history | |
947 histget() get an item from a history | |
948 histnr() get highest index of a history list | |
949 | |
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
|
950 Interactive: *interactive-functions* |
824 | 951 browse() put up a file requester |
952 browsedir() put up a directory requester | |
7 | 953 confirm() let the user make a choice |
954 getchar() get a character from the user | |
24840
c7aa7acb23bb
patch 8.2.2958: function list test fails
Bram Moolenaar <Bram@vim.org>
parents:
24520
diff
changeset
|
955 getcharstr() get a character from the user as a string |
7 | 956 getcharmod() get modifiers for the last typed character |
18639 | 957 getmousepos() get last known mouse position |
20687
770a8e9c4781
patch 8.2.0897: list of functions in patched version is outdated
Bram Moolenaar <Bram@vim.org>
parents:
20643
diff
changeset
|
958 echoraw() output characters as-is |
1620 | 959 feedkeys() put characters in the typeahead queue |
7 | 960 input() get a line from the user |
824 | 961 inputlist() let the user pick an entry from a list |
7 | 962 inputsecret() get a line from the user without showing it |
963 inputdialog() get a line from the user in a dialog | |
230 | 964 inputsave() save and clear typeahead |
7 | 965 inputrestore() restore typeahead |
966 | |
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
|
967 GUI: *gui-functions* |
824 | 968 getfontname() get name of current font being used |
13437 | 969 getwinpos() position of the Vim window |
970 getwinposx() X position of the Vim window | |
971 getwinposy() Y position of the Vim window | |
11062 | 972 balloon_show() set the balloon content |
12909 | 973 balloon_split() split a message for a balloon |
16604
1e0a5f09fdf1
patch 8.1.1305: there is no easy way to manipulate environment variables
Bram Moolenaar <Bram@vim.org>
parents:
16576
diff
changeset
|
974 balloon_gettext() get the text in the balloon |
824 | 975 |
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
|
976 Vim server: *server-functions* |
7 | 977 serverlist() return the list of server names |
12756
3b26420fc639
Long overdue runtime update.
Christian Brabandt <cb@256bit.org>
parents:
12254
diff
changeset
|
978 remote_startserver() run a server |
7 | 979 remote_send() send command characters to a Vim server |
980 remote_expr() evaluate an expression in a Vim server | |
981 server2client() send a reply to a client of a Vim server | |
982 remote_peek() check if there is a reply from a Vim server | |
983 remote_read() read a reply from a Vim server | |
984 foreground() move the Vim window to the foreground | |
985 remote_foreground() move the Vim server window to the foreground | |
986 | |
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
|
987 Window size and position: *window-size-functions* |
824 | 988 winheight() get height of a specific window |
989 winwidth() get width of a specific window | |
13051 | 990 win_screenpos() get screen position of a window |
15068 | 991 winlayout() get layout of windows in a tab page |
824 | 992 winrestcmd() return command to restore window sizes |
993 winsaveview() get view of current window | |
994 winrestview() restore saved view of current window | |
995 | |
19657
da791e5c0139
patch 8.2.0385: menu functionality insufficiently tested
Bram Moolenaar <Bram@vim.org>
parents:
19384
diff
changeset
|
996 Mappings and Menus: *mapping-functions* |
25378
890fd8211202
patch 8.2.3226: new digraph functions use old naming scheme
Bram Moolenaar <Bram@vim.org>
parents:
25294
diff
changeset
|
997 digraph_get() get |digraph| |
890fd8211202
patch 8.2.3226: new digraph functions use old naming scheme
Bram Moolenaar <Bram@vim.org>
parents:
25294
diff
changeset
|
998 digraph_getlist() get all |digraph|s |
890fd8211202
patch 8.2.3226: new digraph functions use old naming scheme
Bram Moolenaar <Bram@vim.org>
parents:
25294
diff
changeset
|
999 digraph_set() register |digraph| |
890fd8211202
patch 8.2.3226: new digraph functions use old naming scheme
Bram Moolenaar <Bram@vim.org>
parents:
25294
diff
changeset
|
1000 digraph_setlist() register multiple |digraph|s |
4159 | 1001 hasmapto() check if a mapping exists |
1002 mapcheck() check if a matching mapping exists | |
1003 maparg() get rhs of a mapping | |
20687
770a8e9c4781
patch 8.2.0897: list of functions in patched version is outdated
Bram Moolenaar <Bram@vim.org>
parents:
20643
diff
changeset
|
1004 mapset() restore a mapping |
19657
da791e5c0139
patch 8.2.0385: menu functionality insufficiently tested
Bram Moolenaar <Bram@vim.org>
parents:
19384
diff
changeset
|
1005 menu_info() get information about a menu item |
4159 | 1006 wildmenumode() check if the wildmode is active |
1007 | |
7279
b5e9810b389d
commit https://github.com/vim/vim/commit/683fa185a4b4ed7595e5942901548b8239ed5cdb
Christian Brabandt <cb@256bit.org>
parents:
6153
diff
changeset
|
1008 Testing: *test-functions* |
8673
ed7251c3e2d3
commit https://github.com/vim/vim/commit/e18c0b39815c5a746887a509c2cd9f11fadaba07
Christian Brabandt <cb@256bit.org>
parents:
8061
diff
changeset
|
1009 assert_equal() assert that two expressions values are equal |
15068 | 1010 assert_equalfile() assert that two file contents are equal |
8876
47f17f66da3d
commit https://github.com/vim/vim/commit/03413f44167c4b5cd0012def9bb331e2518c83cf
Christian Brabandt <cb@256bit.org>
parents:
8795
diff
changeset
|
1011 assert_notequal() assert that two expressions values are not equal |
9644
9f7bcc2c3b97
commit https://github.com/vim/vim/commit/6f1d9a096bf22d50c727dca73abbfb8e3ff55176
Christian Brabandt <cb@256bit.org>
parents:
9464
diff
changeset
|
1012 assert_inrange() assert that an expression is inside a range |
8795
aba2d0a01290
commit https://github.com/vim/vim/commit/7db8f6f4f85e5d0526d23107b2a5e2334dc23354
Christian Brabandt <cb@256bit.org>
parents:
8793
diff
changeset
|
1013 assert_match() assert that a pattern matches the value |
8876
47f17f66da3d
commit https://github.com/vim/vim/commit/03413f44167c4b5cd0012def9bb331e2518c83cf
Christian Brabandt <cb@256bit.org>
parents:
8795
diff
changeset
|
1014 assert_notmatch() assert that a pattern does not match the value |
7279
b5e9810b389d
commit https://github.com/vim/vim/commit/683fa185a4b4ed7595e5942901548b8239ed5cdb
Christian Brabandt <cb@256bit.org>
parents:
6153
diff
changeset
|
1015 assert_false() assert that an expression is false |
b5e9810b389d
commit https://github.com/vim/vim/commit/683fa185a4b4ed7595e5942901548b8239ed5cdb
Christian Brabandt <cb@256bit.org>
parents:
6153
diff
changeset
|
1016 assert_true() assert that an expression is true |
8673
ed7251c3e2d3
commit https://github.com/vim/vim/commit/e18c0b39815c5a746887a509c2cd9f11fadaba07
Christian Brabandt <cb@256bit.org>
parents:
8061
diff
changeset
|
1017 assert_exception() assert that a command throws an exception |
13341
acd7eaa13d2b
Updated runtime files.
Christian Brabandt <cb@256bit.org>
parents:
13280
diff
changeset
|
1018 assert_beeps() assert that a command beeps |
24313
10c39822f496
patch 8.2.2697: function list test fails
Bram Moolenaar <Bram@vim.org>
parents:
24278
diff
changeset
|
1019 assert_nobeep() assert that a command does not cause a beep |
13341
acd7eaa13d2b
Updated runtime files.
Christian Brabandt <cb@256bit.org>
parents:
13280
diff
changeset
|
1020 assert_fails() assert that a command fails |
11229
146a1e213b60
Update runtime files. Add Rust support.
Christian Brabandt <cb@256bit.org>
parents:
11160
diff
changeset
|
1021 assert_report() report a test failure |
9286
64035abb986b
commit https://github.com/vim/vim/commit/c95a302a4c42ec8230473cd4a5e0064d0a143aa8
Christian Brabandt <cb@256bit.org>
parents:
9227
diff
changeset
|
1022 test_alloc_fail() make memory allocation fail |
9644
9f7bcc2c3b97
commit https://github.com/vim/vim/commit/6f1d9a096bf22d50c727dca73abbfb8e3ff55176
Christian Brabandt <cb@256bit.org>
parents:
9464
diff
changeset
|
1023 test_autochdir() enable 'autochdir' during startup |
11160 | 1024 test_override() test with Vim internal overrides |
1025 test_garbagecollect_now() free memory right now | |
20687
770a8e9c4781
patch 8.2.0897: list of functions in patched version is outdated
Bram Moolenaar <Bram@vim.org>
parents:
20643
diff
changeset
|
1026 test_garbagecollect_soon() set a flag to free memory soon |
16808 | 1027 test_getvalue() get value of an internal variable |
25006
496221916885
patch 8.2.3040: GUI: dropping files not tested
Bram Moolenaar <Bram@vim.org>
parents:
24982
diff
changeset
|
1028 test_gui_drop_files() drop file(s) in a window |
24982
4cb423b9250d
patch 8.2.3028: GUI mouse events not tested
Bram Moolenaar <Bram@vim.org>
parents:
24911
diff
changeset
|
1029 test_gui_mouse_event() add a GUI mouse event to the input buffer |
11062 | 1030 test_ignore_error() ignore a specific error message |
15729 | 1031 test_null_blob() return a null Blob |
9286
64035abb986b
commit https://github.com/vim/vim/commit/c95a302a4c42ec8230473cd4a5e0064d0a143aa8
Christian Brabandt <cb@256bit.org>
parents:
9227
diff
changeset
|
1032 test_null_channel() return a null Channel |
64035abb986b
commit https://github.com/vim/vim/commit/c95a302a4c42ec8230473cd4a5e0064d0a143aa8
Christian Brabandt <cb@256bit.org>
parents:
9227
diff
changeset
|
1033 test_null_dict() return a null Dict |
20687
770a8e9c4781
patch 8.2.0897: list of functions in patched version is outdated
Bram Moolenaar <Bram@vim.org>
parents:
20643
diff
changeset
|
1034 test_null_function() return a null Funcref |
9286
64035abb986b
commit https://github.com/vim/vim/commit/c95a302a4c42ec8230473cd4a5e0064d0a143aa8
Christian Brabandt <cb@256bit.org>
parents:
9227
diff
changeset
|
1035 test_null_job() return a null Job |
64035abb986b
commit https://github.com/vim/vim/commit/c95a302a4c42ec8230473cd4a5e0064d0a143aa8
Christian Brabandt <cb@256bit.org>
parents:
9227
diff
changeset
|
1036 test_null_list() return a null List |
64035abb986b
commit https://github.com/vim/vim/commit/c95a302a4c42ec8230473cd4a5e0064d0a143aa8
Christian Brabandt <cb@256bit.org>
parents:
9227
diff
changeset
|
1037 test_null_partial() return a null Partial function |
64035abb986b
commit https://github.com/vim/vim/commit/c95a302a4c42ec8230473cd4a5e0064d0a143aa8
Christian Brabandt <cb@256bit.org>
parents:
9227
diff
changeset
|
1038 test_null_string() return a null String |
11062 | 1039 test_settime() set the time Vim uses internally |
16517
9484fc00ac6b
patch 8.1.1262: cannot simulate a mouse click in a test
Bram Moolenaar <Bram@vim.org>
parents:
16427
diff
changeset
|
1040 test_setmouse() set the mouse position |
15068 | 1041 test_feedinput() add key sequence to input buffer |
1042 test_option_not_set() reset flag indicating option was set | |
1043 test_scrollbar() simulate scrollbar movement in the GUI | |
20687
770a8e9c4781
patch 8.2.0897: list of functions in patched version is outdated
Bram Moolenaar <Bram@vim.org>
parents:
20643
diff
changeset
|
1044 test_refcount() return an expression's reference count |
770a8e9c4781
patch 8.2.0897: list of functions in patched version is outdated
Bram Moolenaar <Bram@vim.org>
parents:
20643
diff
changeset
|
1045 test_srand_seed() set the seed value for srand() |
770a8e9c4781
patch 8.2.0897: list of functions in patched version is outdated
Bram Moolenaar <Bram@vim.org>
parents:
20643
diff
changeset
|
1046 test_unknown() return a value with unknown type |
770a8e9c4781
patch 8.2.0897: list of functions in patched version is outdated
Bram Moolenaar <Bram@vim.org>
parents:
20643
diff
changeset
|
1047 test_void() return a value with void type |
9286
64035abb986b
commit https://github.com/vim/vim/commit/c95a302a4c42ec8230473cd4a5e0064d0a143aa8
Christian Brabandt <cb@256bit.org>
parents:
9227
diff
changeset
|
1048 |
64035abb986b
commit https://github.com/vim/vim/commit/c95a302a4c42ec8230473cd4a5e0064d0a143aa8
Christian Brabandt <cb@256bit.org>
parents:
9227
diff
changeset
|
1049 Inter-process communication: *channel-functions* |
10449
222b1432814e
commit https://github.com/vim/vim/commit/5162822914372fc916a93f85848c0c82209e7cec
Christian Brabandt <cb@256bit.org>
parents:
10198
diff
changeset
|
1050 ch_canread() check if there is something to read |
7924
00d64eb49ce1
commit https://github.com/vim/vim/commit/681baaf4a4c81418693dcafb81421a8614832e91
Christian Brabandt <cb@256bit.org>
parents:
7790
diff
changeset
|
1051 ch_open() open a channel |
00d64eb49ce1
commit https://github.com/vim/vim/commit/681baaf4a4c81418693dcafb81421a8614832e91
Christian Brabandt <cb@256bit.org>
parents:
7790
diff
changeset
|
1052 ch_close() close a channel |
10140
b11ceef7116e
commit https://github.com/vim/vim/commit/64d8e25bf6efe5f18b032563521c3ce278c316ab
Christian Brabandt <cb@256bit.org>
parents:
9858
diff
changeset
|
1053 ch_close_in() close the in part of a channel |
9286
64035abb986b
commit https://github.com/vim/vim/commit/c95a302a4c42ec8230473cd4a5e0064d0a143aa8
Christian Brabandt <cb@256bit.org>
parents:
9227
diff
changeset
|
1054 ch_read() read a message from a channel |
15512 | 1055 ch_readblob() read a Blob from a channel |
9286
64035abb986b
commit https://github.com/vim/vim/commit/c95a302a4c42ec8230473cd4a5e0064d0a143aa8
Christian Brabandt <cb@256bit.org>
parents:
9227
diff
changeset
|
1056 ch_readraw() read a raw message from a channel |
7924
00d64eb49ce1
commit https://github.com/vim/vim/commit/681baaf4a4c81418693dcafb81421a8614832e91
Christian Brabandt <cb@256bit.org>
parents:
7790
diff
changeset
|
1057 ch_sendexpr() send a JSON message over a channel |
00d64eb49ce1
commit https://github.com/vim/vim/commit/681baaf4a4c81418693dcafb81421a8614832e91
Christian Brabandt <cb@256bit.org>
parents:
7790
diff
changeset
|
1058 ch_sendraw() send a raw message over a channel |
20687
770a8e9c4781
patch 8.2.0897: list of functions in patched version is outdated
Bram Moolenaar <Bram@vim.org>
parents:
20643
diff
changeset
|
1059 ch_evalexpr() evaluate an expression over channel |
770a8e9c4781
patch 8.2.0897: list of functions in patched version is outdated
Bram Moolenaar <Bram@vim.org>
parents:
20643
diff
changeset
|
1060 ch_evalraw() evaluate a raw string over channel |
9286
64035abb986b
commit https://github.com/vim/vim/commit/c95a302a4c42ec8230473cd4a5e0064d0a143aa8
Christian Brabandt <cb@256bit.org>
parents:
9227
diff
changeset
|
1061 ch_status() get status of a channel |
64035abb986b
commit https://github.com/vim/vim/commit/c95a302a4c42ec8230473cd4a5e0064d0a143aa8
Christian Brabandt <cb@256bit.org>
parents:
9227
diff
changeset
|
1062 ch_getbufnr() get the buffer number of a channel |
64035abb986b
commit https://github.com/vim/vim/commit/c95a302a4c42ec8230473cd4a5e0064d0a143aa8
Christian Brabandt <cb@256bit.org>
parents:
9227
diff
changeset
|
1063 ch_getjob() get the job associated with a channel |
64035abb986b
commit https://github.com/vim/vim/commit/c95a302a4c42ec8230473cd4a5e0064d0a143aa8
Christian Brabandt <cb@256bit.org>
parents:
9227
diff
changeset
|
1064 ch_info() get channel information |
64035abb986b
commit https://github.com/vim/vim/commit/c95a302a4c42ec8230473cd4a5e0064d0a143aa8
Christian Brabandt <cb@256bit.org>
parents:
9227
diff
changeset
|
1065 ch_log() write a message in the channel log file |
64035abb986b
commit https://github.com/vim/vim/commit/c95a302a4c42ec8230473cd4a5e0064d0a143aa8
Christian Brabandt <cb@256bit.org>
parents:
9227
diff
changeset
|
1066 ch_logfile() set the channel log file |
64035abb986b
commit https://github.com/vim/vim/commit/c95a302a4c42ec8230473cd4a5e0064d0a143aa8
Christian Brabandt <cb@256bit.org>
parents:
9227
diff
changeset
|
1067 ch_setoptions() set the options for a channel |
9319
1472ed67c36f
commit https://github.com/vim/vim/commit/a02a551e18209423584fcb923e93c6be18f3aa45
Christian Brabandt <cb@256bit.org>
parents:
9286
diff
changeset
|
1068 json_encode() encode an expression to a JSON string |
1472ed67c36f
commit https://github.com/vim/vim/commit/a02a551e18209423584fcb923e93c6be18f3aa45
Christian Brabandt <cb@256bit.org>
parents:
9286
diff
changeset
|
1069 json_decode() decode a JSON string to Vim types |
9286
64035abb986b
commit https://github.com/vim/vim/commit/c95a302a4c42ec8230473cd4a5e0064d0a143aa8
Christian Brabandt <cb@256bit.org>
parents:
9227
diff
changeset
|
1070 js_encode() encode an expression to a JSON string |
64035abb986b
commit https://github.com/vim/vim/commit/c95a302a4c42ec8230473cd4a5e0064d0a143aa8
Christian Brabandt <cb@256bit.org>
parents:
9227
diff
changeset
|
1071 js_decode() decode a JSON string to Vim types |
64035abb986b
commit https://github.com/vim/vim/commit/c95a302a4c42ec8230473cd4a5e0064d0a143aa8
Christian Brabandt <cb@256bit.org>
parents:
9227
diff
changeset
|
1072 |
20687
770a8e9c4781
patch 8.2.0897: list of functions in patched version is outdated
Bram Moolenaar <Bram@vim.org>
parents:
20643
diff
changeset
|
1073 Jobs: *job-functions* |
9286
64035abb986b
commit https://github.com/vim/vim/commit/c95a302a4c42ec8230473cd4a5e0064d0a143aa8
Christian Brabandt <cb@256bit.org>
parents:
9227
diff
changeset
|
1074 job_start() start a job |
64035abb986b
commit https://github.com/vim/vim/commit/c95a302a4c42ec8230473cd4a5e0064d0a143aa8
Christian Brabandt <cb@256bit.org>
parents:
9227
diff
changeset
|
1075 job_stop() stop a job |
64035abb986b
commit https://github.com/vim/vim/commit/c95a302a4c42ec8230473cd4a5e0064d0a143aa8
Christian Brabandt <cb@256bit.org>
parents:
9227
diff
changeset
|
1076 job_status() get the status of a job |
64035abb986b
commit https://github.com/vim/vim/commit/c95a302a4c42ec8230473cd4a5e0064d0a143aa8
Christian Brabandt <cb@256bit.org>
parents:
9227
diff
changeset
|
1077 job_getchannel() get the channel used by a job |
64035abb986b
commit https://github.com/vim/vim/commit/c95a302a4c42ec8230473cd4a5e0064d0a143aa8
Christian Brabandt <cb@256bit.org>
parents:
9227
diff
changeset
|
1078 job_info() get information about a job |
64035abb986b
commit https://github.com/vim/vim/commit/c95a302a4c42ec8230473cd4a5e0064d0a143aa8
Christian Brabandt <cb@256bit.org>
parents:
9227
diff
changeset
|
1079 job_setoptions() set options for a job |
64035abb986b
commit https://github.com/vim/vim/commit/c95a302a4c42ec8230473cd4a5e0064d0a143aa8
Christian Brabandt <cb@256bit.org>
parents:
9227
diff
changeset
|
1080 |
15209
3a99b2e6d136
patch 8.1.0614: placing signs can be complicated
Bram Moolenaar <Bram@vim.org>
parents:
15194
diff
changeset
|
1081 Signs: *sign-functions* |
3a99b2e6d136
patch 8.1.0614: placing signs can be complicated
Bram Moolenaar <Bram@vim.org>
parents:
15194
diff
changeset
|
1082 sign_define() define or update a sign |
3a99b2e6d136
patch 8.1.0614: placing signs can be complicated
Bram Moolenaar <Bram@vim.org>
parents:
15194
diff
changeset
|
1083 sign_getdefined() get a list of defined signs |
3a99b2e6d136
patch 8.1.0614: placing signs can be complicated
Bram Moolenaar <Bram@vim.org>
parents:
15194
diff
changeset
|
1084 sign_getplaced() get a list of placed signs |
15418
51b3c36b0523
patch 8.1.0717: there is no function for the ":sign jump" command
Bram Moolenaar <Bram@vim.org>
parents:
15209
diff
changeset
|
1085 sign_jump() jump to a sign |
15209
3a99b2e6d136
patch 8.1.0614: placing signs can be complicated
Bram Moolenaar <Bram@vim.org>
parents:
15194
diff
changeset
|
1086 sign_place() place a sign |
17366
9843fbfa0ee5
patch 8.1.1682: placing a larger number of signs is slow
Bram Moolenaar <Bram@vim.org>
parents:
17292
diff
changeset
|
1087 sign_placelist() place a list of signs |
15209
3a99b2e6d136
patch 8.1.0614: placing signs can be complicated
Bram Moolenaar <Bram@vim.org>
parents:
15194
diff
changeset
|
1088 sign_undefine() undefine a sign |
3a99b2e6d136
patch 8.1.0614: placing signs can be complicated
Bram Moolenaar <Bram@vim.org>
parents:
15194
diff
changeset
|
1089 sign_unplace() unplace a sign |
17366
9843fbfa0ee5
patch 8.1.1682: placing a larger number of signs is slow
Bram Moolenaar <Bram@vim.org>
parents:
17292
diff
changeset
|
1090 sign_unplacelist() unplace a list of signs |
15209
3a99b2e6d136
patch 8.1.0614: placing signs can be complicated
Bram Moolenaar <Bram@vim.org>
parents:
15194
diff
changeset
|
1091 |
12254 | 1092 Terminal window: *terminal-functions* |
1093 term_start() open a terminal window and run a job | |
1094 term_list() get the list of terminal buffers | |
1095 term_sendkeys() send keystrokes to a terminal | |
1096 term_wait() wait for screen to be updated | |
1097 term_getjob() get the job associated with a terminal | |
1098 term_scrape() get row of a terminal screen | |
1099 term_getline() get a line of text from a terminal | |
1100 term_getattr() get the value of attribute {what} | |
1101 term_getcursor() get the cursor position of a terminal | |
1102 term_getscrolled() get the scroll count of a terminal | |
1103 term_getaltscreen() get the alternate screen flag | |
1104 term_getsize() get the size of a terminal | |
1105 term_getstatus() get the status of a terminal | |
1106 term_gettitle() get the title of a terminal | |
1107 term_gettty() get the tty name of a terminal | |
13735 | 1108 term_setansicolors() set 16 ANSI colors, used for GUI |
1109 term_getansicolors() get 16 ANSI colors, used for GUI | |
15068 | 1110 term_dumpdiff() display difference between two screen dumps |
1111 term_dumpload() load a terminal screen dump in a window | |
1112 term_dumpwrite() dump contents of a terminal screen to a file | |
1113 term_setkill() set signal to stop job in a terminal | |
1114 term_setrestore() set command to restore a terminal | |
1115 term_setsize() set the size of a terminal | |
20687
770a8e9c4781
patch 8.2.0897: list of functions in patched version is outdated
Bram Moolenaar <Bram@vim.org>
parents:
20643
diff
changeset
|
1116 term_setapi() set terminal JSON API function name prefix |
12254 | 1117 |
17257
cb0ca75f0c26
patch 8.1.1628: popup window functions not in list of functions
Bram Moolenaar <Bram@vim.org>
parents:
17020
diff
changeset
|
1118 Popup window: *popup-window-functions* |
cb0ca75f0c26
patch 8.1.1628: popup window functions not in list of functions
Bram Moolenaar <Bram@vim.org>
parents:
17020
diff
changeset
|
1119 popup_create() create popup centered in the screen |
cb0ca75f0c26
patch 8.1.1628: popup window functions not in list of functions
Bram Moolenaar <Bram@vim.org>
parents:
17020
diff
changeset
|
1120 popup_atcursor() create popup just above the cursor position, |
cb0ca75f0c26
patch 8.1.1628: popup window functions not in list of functions
Bram Moolenaar <Bram@vim.org>
parents:
17020
diff
changeset
|
1121 closes when the cursor moves away |
17292
8a095d343c59
patch 8.1.1645: cannot use a popup window for a balloon
Bram Moolenaar <Bram@vim.org>
parents:
17257
diff
changeset
|
1122 popup_beval() at the position indicated by v:beval_ |
8a095d343c59
patch 8.1.1645: cannot use a popup window for a balloon
Bram Moolenaar <Bram@vim.org>
parents:
17257
diff
changeset
|
1123 variables, closes when the mouse moves away |
17257
cb0ca75f0c26
patch 8.1.1628: popup window functions not in list of functions
Bram Moolenaar <Bram@vim.org>
parents:
17020
diff
changeset
|
1124 popup_notification() show a notification for three seconds |
cb0ca75f0c26
patch 8.1.1628: popup window functions not in list of functions
Bram Moolenaar <Bram@vim.org>
parents:
17020
diff
changeset
|
1125 popup_dialog() create popup centered with padding and border |
cb0ca75f0c26
patch 8.1.1628: popup window functions not in list of functions
Bram Moolenaar <Bram@vim.org>
parents:
17020
diff
changeset
|
1126 popup_menu() prompt for selecting an item from a list |
cb0ca75f0c26
patch 8.1.1628: popup window functions not in list of functions
Bram Moolenaar <Bram@vim.org>
parents:
17020
diff
changeset
|
1127 popup_hide() hide a popup temporarily |
cb0ca75f0c26
patch 8.1.1628: popup window functions not in list of functions
Bram Moolenaar <Bram@vim.org>
parents:
17020
diff
changeset
|
1128 popup_show() show a previously hidden popup |
cb0ca75f0c26
patch 8.1.1628: popup window functions not in list of functions
Bram Moolenaar <Bram@vim.org>
parents:
17020
diff
changeset
|
1129 popup_move() change the position and size of a popup |
cb0ca75f0c26
patch 8.1.1628: popup window functions not in list of functions
Bram Moolenaar <Bram@vim.org>
parents:
17020
diff
changeset
|
1130 popup_setoptions() override options of a popup |
cb0ca75f0c26
patch 8.1.1628: popup window functions not in list of functions
Bram Moolenaar <Bram@vim.org>
parents:
17020
diff
changeset
|
1131 popup_settext() replace the popup buffer contents |
cb0ca75f0c26
patch 8.1.1628: popup window functions not in list of functions
Bram Moolenaar <Bram@vim.org>
parents:
17020
diff
changeset
|
1132 popup_close() close one popup |
cb0ca75f0c26
patch 8.1.1628: popup window functions not in list of functions
Bram Moolenaar <Bram@vim.org>
parents:
17020
diff
changeset
|
1133 popup_clear() close all popups |
cb0ca75f0c26
patch 8.1.1628: popup window functions not in list of functions
Bram Moolenaar <Bram@vim.org>
parents:
17020
diff
changeset
|
1134 popup_filter_menu() select from a list of items |
20687
770a8e9c4781
patch 8.2.0897: list of functions in patched version is outdated
Bram Moolenaar <Bram@vim.org>
parents:
20643
diff
changeset
|
1135 popup_filter_yesno() block until 'y' or 'n' is pressed |
17257
cb0ca75f0c26
patch 8.1.1628: popup window functions not in list of functions
Bram Moolenaar <Bram@vim.org>
parents:
17020
diff
changeset
|
1136 popup_getoptions() get current options for a popup |
cb0ca75f0c26
patch 8.1.1628: popup window functions not in list of functions
Bram Moolenaar <Bram@vim.org>
parents:
17020
diff
changeset
|
1137 popup_getpos() get actual position and size of a popup |
20687
770a8e9c4781
patch 8.2.0897: list of functions in patched version is outdated
Bram Moolenaar <Bram@vim.org>
parents:
20643
diff
changeset
|
1138 popup_findinfo() get window ID for popup info window |
770a8e9c4781
patch 8.2.0897: list of functions in patched version is outdated
Bram Moolenaar <Bram@vim.org>
parents:
20643
diff
changeset
|
1139 popup_findpreview() get window ID for popup preview window |
770a8e9c4781
patch 8.2.0897: list of functions in patched version is outdated
Bram Moolenaar <Bram@vim.org>
parents:
20643
diff
changeset
|
1140 popup_list() get list of all popup window IDs |
770a8e9c4781
patch 8.2.0897: list of functions in patched version is outdated
Bram Moolenaar <Bram@vim.org>
parents:
20643
diff
changeset
|
1141 popup_locate() get popup window ID from its screen position |
17257
cb0ca75f0c26
patch 8.1.1628: popup window functions not in list of functions
Bram Moolenaar <Bram@vim.org>
parents:
17020
diff
changeset
|
1142 |
9286
64035abb986b
commit https://github.com/vim/vim/commit/c95a302a4c42ec8230473cd4a5e0064d0a143aa8
Christian Brabandt <cb@256bit.org>
parents:
9227
diff
changeset
|
1143 Timers: *timer-functions* |
64035abb986b
commit https://github.com/vim/vim/commit/c95a302a4c42ec8230473cd4a5e0064d0a143aa8
Christian Brabandt <cb@256bit.org>
parents:
9227
diff
changeset
|
1144 timer_start() create a timer |
9858
3e96d9ed2ca1
commit https://github.com/vim/vim/commit/b5ae48e9ffd3b8eb6ca4057de11f1bddcde8ce6f
Christian Brabandt <cb@256bit.org>
parents:
9644
diff
changeset
|
1145 timer_pause() pause or unpause a timer |
9286
64035abb986b
commit https://github.com/vim/vim/commit/c95a302a4c42ec8230473cd4a5e0064d0a143aa8
Christian Brabandt <cb@256bit.org>
parents:
9227
diff
changeset
|
1146 timer_stop() stop a timer |
9858
3e96d9ed2ca1
commit https://github.com/vim/vim/commit/b5ae48e9ffd3b8eb6ca4057de11f1bddcde8ce6f
Christian Brabandt <cb@256bit.org>
parents:
9644
diff
changeset
|
1147 timer_stopall() stop all timers |
3e96d9ed2ca1
commit https://github.com/vim/vim/commit/b5ae48e9ffd3b8eb6ca4057de11f1bddcde8ce6f
Christian Brabandt <cb@256bit.org>
parents:
9644
diff
changeset
|
1148 timer_info() get information about timers |
7790
ca19726d5e83
commit https://github.com/vim/vim/commit/298b440930ecece38d6ea0505a3e582dc817e79b
Christian Brabandt <cb@256bit.org>
parents:
7651
diff
changeset
|
1149 |
15068 | 1150 Tags: *tag-functions* |
1151 taglist() get list of matching tags | |
1152 tagfiles() get a list of tags files | |
1153 gettagstack() get the tag stack of a window | |
1154 settagstack() modify the tag stack of a window | |
1155 | |
1156 Prompt Buffer: *promptbuffer-functions* | |
22077
335365fcbb60
patch 8.2.1588: cannot read back the prompt of a prompt buffer
Bram Moolenaar <Bram@vim.org>
parents:
21991
diff
changeset
|
1157 prompt_getprompt() get the effective prompt text for a buffer |
15068 | 1158 prompt_setcallback() set prompt callback for a buffer |
1159 prompt_setinterrupt() set interrupt callback for a buffer | |
1160 prompt_setprompt() set the prompt text for a buffer | |
1161 | |
20687
770a8e9c4781
patch 8.2.0897: list of functions in patched version is outdated
Bram Moolenaar <Bram@vim.org>
parents:
20643
diff
changeset
|
1162 Text Properties: *text-property-functions* |
770a8e9c4781
patch 8.2.0897: list of functions in patched version is outdated
Bram Moolenaar <Bram@vim.org>
parents:
20643
diff
changeset
|
1163 prop_add() attach a property at a position |
770a8e9c4781
patch 8.2.0897: list of functions in patched version is outdated
Bram Moolenaar <Bram@vim.org>
parents:
20643
diff
changeset
|
1164 prop_clear() remove all properties from a line or lines |
770a8e9c4781
patch 8.2.0897: list of functions in patched version is outdated
Bram Moolenaar <Bram@vim.org>
parents:
20643
diff
changeset
|
1165 prop_find() search for a property |
770a8e9c4781
patch 8.2.0897: list of functions in patched version is outdated
Bram Moolenaar <Bram@vim.org>
parents:
20643
diff
changeset
|
1166 prop_list() return a list of all properties in a line |
770a8e9c4781
patch 8.2.0897: list of functions in patched version is outdated
Bram Moolenaar <Bram@vim.org>
parents:
20643
diff
changeset
|
1167 prop_remove() remove a property from a line |
770a8e9c4781
patch 8.2.0897: list of functions in patched version is outdated
Bram Moolenaar <Bram@vim.org>
parents:
20643
diff
changeset
|
1168 prop_type_add() add/define a property type |
770a8e9c4781
patch 8.2.0897: list of functions in patched version is outdated
Bram Moolenaar <Bram@vim.org>
parents:
20643
diff
changeset
|
1169 prop_type_change() change properties of a type |
770a8e9c4781
patch 8.2.0897: list of functions in patched version is outdated
Bram Moolenaar <Bram@vim.org>
parents:
20643
diff
changeset
|
1170 prop_type_delete() remove a text property type |
770a8e9c4781
patch 8.2.0897: list of functions in patched version is outdated
Bram Moolenaar <Bram@vim.org>
parents:
20643
diff
changeset
|
1171 prop_type_get() return the properties of a type |
770a8e9c4781
patch 8.2.0897: list of functions in patched version is outdated
Bram Moolenaar <Bram@vim.org>
parents:
20643
diff
changeset
|
1172 prop_type_list() return a list of all property types |
770a8e9c4781
patch 8.2.0897: list of functions in patched version is outdated
Bram Moolenaar <Bram@vim.org>
parents:
20643
diff
changeset
|
1173 |
770a8e9c4781
patch 8.2.0897: list of functions in patched version is outdated
Bram Moolenaar <Bram@vim.org>
parents:
20643
diff
changeset
|
1174 Sound: *sound-functions* |
770a8e9c4781
patch 8.2.0897: list of functions in patched version is outdated
Bram Moolenaar <Bram@vim.org>
parents:
20643
diff
changeset
|
1175 sound_clear() stop playing all sounds |
770a8e9c4781
patch 8.2.0897: list of functions in patched version is outdated
Bram Moolenaar <Bram@vim.org>
parents:
20643
diff
changeset
|
1176 sound_playevent() play an event's sound |
770a8e9c4781
patch 8.2.0897: list of functions in patched version is outdated
Bram Moolenaar <Bram@vim.org>
parents:
20643
diff
changeset
|
1177 sound_playfile() play a sound file |
770a8e9c4781
patch 8.2.0897: list of functions in patched version is outdated
Bram Moolenaar <Bram@vim.org>
parents:
20643
diff
changeset
|
1178 sound_stop() stop playing a sound |
770a8e9c4781
patch 8.2.0897: list of functions in patched version is outdated
Bram Moolenaar <Bram@vim.org>
parents:
20643
diff
changeset
|
1179 |
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
|
1180 Various: *various-functions* |
7 | 1181 mode() get current editing mode |
20687
770a8e9c4781
patch 8.2.0897: list of functions in patched version is outdated
Bram Moolenaar <Bram@vim.org>
parents:
20643
diff
changeset
|
1182 state() get current busy state |
7 | 1183 visualmode() last visual mode used |
1184 exists() check if a variable, function, etc. exists | |
1185 has() check if a feature is supported in Vim | |
824 | 1186 changenr() return number of most recent change |
7 | 1187 cscope_connection() check if a cscope connection exists |
1188 did_filetype() check if a FileType autocommand was used | |
1189 eventhandler() check if invoked by an event handler | |
1620 | 1190 getpid() get process ID of Vim |
20687
770a8e9c4781
patch 8.2.0897: list of functions in patched version is outdated
Bram Moolenaar <Bram@vim.org>
parents:
20643
diff
changeset
|
1191 getimstatus() check if IME status is active |
770a8e9c4781
patch 8.2.0897: list of functions in patched version is outdated
Bram Moolenaar <Bram@vim.org>
parents:
20643
diff
changeset
|
1192 interrupt() interrupt script execution |
770a8e9c4781
patch 8.2.0897: list of functions in patched version is outdated
Bram Moolenaar <Bram@vim.org>
parents:
20643
diff
changeset
|
1193 windowsversion() get MS-Windows version |
20836
2616c5a337e0
patch 8.2.0970: terminal properties are not available in Vim script
Bram Moolenaar <Bram@vim.org>
parents:
20766
diff
changeset
|
1194 terminalprops() properties of the terminal |
824 | 1195 |
7 | 1196 libcall() call a function in an external library |
1197 libcallnr() idem, returning a number | |
824 | 1198 |
5618 | 1199 undofile() get the name of the undo file |
1200 undotree() return the state of the undo tree | |
1201 | |
7 | 1202 getreg() get contents of a register |
20743
a672feb8fc4f
patch 8.2.0924: cannot save and restore a register properly
Bram Moolenaar <Bram@vim.org>
parents:
20687
diff
changeset
|
1203 getreginfo() get information about a register |
7 | 1204 getregtype() get type of a register |
1205 setreg() set contents and type of a register | |
14004
e124262d435e
patch 8.1.0020: cannot tell whether a register is executing or recording
Christian Brabandt <cb@256bit.org>
parents:
13963
diff
changeset
|
1206 reg_executing() return the name of the register being executed |
e124262d435e
patch 8.1.0020: cannot tell whether a register is executing or recording
Christian Brabandt <cb@256bit.org>
parents:
13963
diff
changeset
|
1207 reg_recording() return the name of the register being recorded |
824 | 1208 |
5618 | 1209 shiftwidth() effective value of 'shiftwidth' |
1210 | |
9464
be72f4201a1d
commit https://github.com/vim/vim/commit/063b9d15abea041a5bfff3ffc4e219e26fd1d4fa
Christian Brabandt <cb@256bit.org>
parents:
9319
diff
changeset
|
1211 wordcount() get byte/word/char count of buffer |
be72f4201a1d
commit https://github.com/vim/vim/commit/063b9d15abea041a5bfff3ffc4e219e26fd1d4fa
Christian Brabandt <cb@256bit.org>
parents:
9319
diff
changeset
|
1212 |
20687
770a8e9c4781
patch 8.2.0897: list of functions in patched version is outdated
Bram Moolenaar <Bram@vim.org>
parents:
20643
diff
changeset
|
1213 luaeval() evaluate |Lua| expression |
2050
afcf9db31561
updated for version 7.2.336
Bram Moolenaar <bram@zimbu.org>
parents:
1702
diff
changeset
|
1214 mzeval() evaluate |MzScheme| expression |
7651
c7575b07de98
commit https://github.com/vim/vim/commit/e9b892ebcd8596bf813793a1eed5a460a9495a28
Christian Brabandt <cb@256bit.org>
parents:
7480
diff
changeset
|
1215 perleval() evaluate Perl expression (|+perl|) |
5618 | 1216 py3eval() evaluate Python expression (|+python3|) |
1217 pyeval() evaluate Python expression (|+python|) | |
10734 | 1218 pyxeval() evaluate |python_x| expression |
20687
770a8e9c4781
patch 8.2.0897: list of functions in patched version is outdated
Bram Moolenaar <Bram@vim.org>
parents:
20643
diff
changeset
|
1219 rubyeval() evaluate |Ruby| expression |
770a8e9c4781
patch 8.2.0897: list of functions in patched version is outdated
Bram Moolenaar <Bram@vim.org>
parents:
20643
diff
changeset
|
1220 |
15194 | 1221 debugbreak() interrupt a program being debugged |
2050
afcf9db31561
updated for version 7.2.336
Bram Moolenaar <bram@zimbu.org>
parents:
1702
diff
changeset
|
1222 |
7 | 1223 ============================================================================== |
1224 *41.7* Defining a function | |
1225 | |
1226 Vim enables you to define your own functions. The basic function declaration | |
1227 begins as follows: > | |
1228 | |
1229 :function {name}({var1}, {var2}, ...) | |
1230 : {body} | |
1231 :endfunction | |
1232 < | |
1233 Note: | |
1234 Function names must begin with a capital letter. | |
1235 | |
1236 Let's define a short function to return the smaller of two numbers. It starts | |
1237 with this line: > | |
1238 | |
1239 :function Min(num1, num2) | |
1240 | |
1241 This tells Vim that the function is named "Min" and it takes two arguments: | |
1242 "num1" and "num2". | |
1243 The first thing you need to do is to check to see which number is smaller: | |
1244 > | |
1245 : if a:num1 < a:num2 | |
1246 | |
1247 The special prefix "a:" tells Vim that the variable is a function argument. | |
1248 Let's assign the variable "smaller" the value of the smallest number: > | |
1249 | |
1250 : if a:num1 < a:num2 | |
1251 : let smaller = a:num1 | |
1252 : else | |
1253 : let smaller = a:num2 | |
1254 : endif | |
1255 | |
1256 The variable "smaller" is a local variable. Variables used inside a function | |
1257 are local unless prefixed by something like "g:", "a:", or "s:". | |
1258 | |
1259 Note: | |
1260 To access a global variable from inside a function you must prepend | |
1620 | 1261 "g:" to it. Thus "g:today" inside a function is used for the global |
1262 variable "today", and "today" is another variable, local to the | |
7 | 1263 function. |
1264 | |
1265 You now use the ":return" statement to return the smallest number to the user. | |
1266 Finally, you end the function: > | |
1267 | |
1268 : return smaller | |
1269 :endfunction | |
1270 | |
1271 The complete function definition is as follows: > | |
1272 | |
1273 :function Min(num1, num2) | |
1274 : if a:num1 < a:num2 | |
1275 : let smaller = a:num1 | |
1276 : else | |
1277 : let smaller = a:num2 | |
1278 : endif | |
1279 : return smaller | |
1280 :endfunction | |
1281 | |
161 | 1282 For people who like short functions, this does the same thing: > |
1283 | |
1284 :function Min(num1, num2) | |
1285 : if a:num1 < a:num2 | |
1286 : return a:num1 | |
1287 : endif | |
1288 : return a:num2 | |
1289 :endfunction | |
1290 | |
681 | 1291 A user defined function is called in exactly the same way as a built-in |
7 | 1292 function. Only the name is different. The Min function can be used like |
1293 this: > | |
1294 | |
1295 :echo Min(5, 8) | |
1296 | |
1297 Only now will the function be executed and the lines be interpreted by Vim. | |
1298 If there are mistakes, like using an undefined variable or function, you will | |
1299 now get an error message. When defining the function these errors are not | |
1300 detected. | |
1301 | |
1302 When a function reaches ":endfunction" or ":return" is used without an | |
1303 argument, the function returns zero. | |
1304 | |
1305 To redefine a function that already exists, use the ! for the ":function" | |
1306 command: > | |
1307 | |
1308 :function! Min(num1, num2, num3) | |
1309 | |
1310 | |
1311 USING A RANGE | |
1312 | |
1313 The ":call" command can be given a line range. This can have one of two | |
1314 meanings. When a function has been defined with the "range" keyword, it will | |
1315 take care of the line range itself. | |
1316 The function will be passed the variables "a:firstline" and "a:lastline". | |
1317 These will have the line numbers from the range the function was called with. | |
1318 Example: > | |
1319 | |
1320 :function Count_words() range | |
1620 | 1321 : let lnum = a:firstline |
1322 : let n = 0 | |
1323 : while lnum <= a:lastline | |
1324 : let n = n + len(split(getline(lnum))) | |
1325 : let lnum = lnum + 1 | |
7 | 1326 : endwhile |
22171 | 1327 : echo "found " .. n .. " words" |
7 | 1328 :endfunction |
1329 | |
1330 You can call this function with: > | |
1331 | |
1332 :10,30call Count_words() | |
1333 | |
1334 It will be executed once and echo the number of words. | |
1335 The other way to use a line range is by defining a function without the | |
1336 "range" keyword. The function will be called once for every line in the | |
1337 range, with the cursor in that line. Example: > | |
1338 | |
1339 :function Number() | |
22171 | 1340 : echo "line " .. line(".") .. " contains: " .. getline(".") |
7 | 1341 :endfunction |
1342 | |
1343 If you call this function with: > | |
1344 | |
1345 :10,15call Number() | |
1346 | |
1347 The function will be called six times. | |
1348 | |
1349 | |
1350 VARIABLE NUMBER OF ARGUMENTS | |
1351 | |
1352 Vim enables you to define functions that have a variable number of arguments. | |
1353 The following command, for instance, defines a function that must have 1 | |
1354 argument (start) and can have up to 20 additional arguments: > | |
1355 | |
1356 :function Show(start, ...) | |
1357 | |
1358 The variable "a:1" contains the first optional argument, "a:2" the second, and | |
1359 so on. The variable "a:0" contains the number of extra arguments. | |
1360 For example: > | |
1361 | |
1362 :function Show(start, ...) | |
1363 : echohl Title | |
22171 | 1364 : echo "start is " .. a:start |
7 | 1365 : echohl None |
1366 : let index = 1 | |
1367 : while index <= a:0 | |
22171 | 1368 : echo " Arg " .. index .. " is " .. a:{index} |
7 | 1369 : let index = index + 1 |
1370 : endwhile | |
1371 : echo "" | |
1372 :endfunction | |
1373 | |
1374 This uses the ":echohl" command to specify the highlighting used for the | |
1375 following ":echo" command. ":echohl None" stops it again. The ":echon" | |
1376 command works like ":echo", but doesn't output a line break. | |
1377 | |
161 | 1378 You can also use the a:000 variable, it is a List of all the "..." arguments. |
1379 See |a:000|. | |
1380 | |
7 | 1381 |
1382 LISTING FUNCTIONS | |
1383 | |
1384 The ":function" command lists the names and arguments of all user-defined | |
1385 functions: > | |
1386 | |
1387 :function | |
1388 < function Show(start, ...) ~ | |
1389 function GetVimIndent() ~ | |
1390 function SetSyn(name) ~ | |
1391 | |
1392 To see what a function does, use its name as an argument for ":function": > | |
1393 | |
1394 :function SetSyn | |
1395 < 1 if &syntax == '' ~ | |
1396 2 let &syntax = a:name ~ | |
1397 3 endif ~ | |
1398 endfunction ~ | |
1399 | |
1400 | |
1401 DEBUGGING | |
1402 | |
1403 The line number is useful for when you get an error message or when debugging. | |
1404 See |debug-scripts| about debugging mode. | |
1405 You can also set the 'verbose' option to 12 or higher to see all function | |
1406 calls. Set it to 15 or higher to see every executed line. | |
1407 | |
1408 | |
1409 DELETING A FUNCTION | |
1410 | |
1411 To delete the Show() function: > | |
1412 | |
1413 :delfunction Show | |
1414 | |
1415 You get an error when the function doesn't exist. | |
1416 | |
161 | 1417 |
1418 FUNCTION REFERENCES | |
1419 | |
1420 Sometimes it can be useful to have a variable point to one function or | |
1421 another. You can do it with the function() function. It turns the name of a | |
1422 function into a reference: > | |
1423 | |
1424 :let result = 0 " or 1 | |
1425 :function! Right() | |
1426 : return 'Right!' | |
1427 :endfunc | |
1428 :function! Wrong() | |
1429 : return 'Wrong!' | |
1430 :endfunc | |
1431 : | |
1432 :if result == 1 | |
1433 : let Afunc = function('Right') | |
1434 :else | |
1435 : let Afunc = function('Wrong') | |
1436 :endif | |
1437 :echo call(Afunc, []) | |
1438 < Wrong! ~ | |
1439 | |
1440 Note that the name of a variable that holds a function reference must start | |
1441 with a capital. Otherwise it could be confused with the name of a builtin | |
1442 function. | |
1443 The way to invoke a function that a variable refers to is with the call() | |
1444 function. Its first argument is the function reference, the second argument | |
1445 is a List with arguments. | |
1446 | |
1447 Function references are most useful in combination with a Dictionary, as is | |
1448 explained in the next section. | |
1449 | |
7 | 1450 ============================================================================== |
161 | 1451 *41.8* Lists and Dictionaries |
1452 | |
1453 So far we have used the basic types String and Number. Vim also supports two | |
1454 composite types: List and Dictionary. | |
1455 | |
1456 A List is an ordered sequence of things. The things can be any kind of value, | |
1457 thus you can make a List of numbers, a List of Lists and even a List of mixed | |
1458 items. To create a List with three strings: > | |
1459 | |
856 | 1460 :let alist = ['aap', 'mies', 'noot'] |
161 | 1461 |
1462 The List items are enclosed in square brackets and separated by commas. To | |
1463 create an empty List: > | |
1464 | |
856 | 1465 :let alist = [] |
161 | 1466 |
1467 You can add items to a List with the add() function: > | |
1468 | |
856 | 1469 :let alist = [] |
161 | 1470 :call add(alist, 'foo') |
1471 :call add(alist, 'bar') | |
1472 :echo alist | |
1473 < ['foo', 'bar'] ~ | |
1474 | |
1475 List concatenation is done with +: > | |
1476 | |
1477 :echo alist + ['foo', 'bar'] | |
1478 < ['foo', 'bar', 'foo', 'bar'] ~ | |
1479 | |
1480 Or, if you want to extend a List directly: > | |
1481 | |
856 | 1482 :let alist = ['one'] |
161 | 1483 :call extend(alist, ['two', 'three']) |
1484 :echo alist | |
1485 < ['one', 'two', 'three'] ~ | |
1486 | |
1487 Notice that using add() will have a different effect: > | |
1488 | |
856 | 1489 :let alist = ['one'] |
161 | 1490 :call add(alist, ['two', 'three']) |
1491 :echo alist | |
1492 < ['one', ['two', 'three']] ~ | |
1493 | |
1494 The second argument of add() is added as a single item. | |
1495 | |
1496 | |
1497 FOR LOOP | |
1498 | |
1499 One of the nice things you can do with a List is iterate over it: > | |
1500 | |
1501 :let alist = ['one', 'two', 'three'] | |
1502 :for n in alist | |
1503 : echo n | |
1504 :endfor | |
1505 < one ~ | |
1506 two ~ | |
1507 three ~ | |
1508 | |
1509 This will loop over each element in List "alist", assigning the value to | |
1510 variable "n". The generic form of a for loop is: > | |
1511 | |
1512 :for {varname} in {listexpression} | |
1513 : {commands} | |
1514 :endfor | |
1515 | |
1516 To loop a certain number of times you need a List of a specific length. The | |
1517 range() function creates one for you: > | |
1518 | |
1519 :for a in range(3) | |
1520 : echo a | |
1521 :endfor | |
1522 < 0 ~ | |
1523 1 ~ | |
1524 2 ~ | |
1525 | |
1526 Notice that the first item of the List that range() produces is zero, thus the | |
1527 last item is one less than the length of the list. | |
1528 You can also specify the maximum value, the stride and even go backwards: > | |
1529 | |
1530 :for a in range(8, 4, -2) | |
1531 : echo a | |
1532 :endfor | |
1533 < 8 ~ | |
1534 6 ~ | |
1535 4 ~ | |
1536 | |
1537 A more useful example, looping over lines in the buffer: > | |
1538 | |
856 | 1539 :for line in getline(1, 20) |
1540 : if line =~ "Date: " | |
1541 : echo matchstr(line, 'Date: \zs.*') | |
1542 : endif | |
1543 :endfor | |
161 | 1544 |
1545 This looks into lines 1 to 20 (inclusive) and echoes any date found in there. | |
1546 | |
1547 | |
1548 DICTIONARIES | |
1549 | |
1550 A Dictionary stores key-value pairs. You can quickly lookup a value if you | |
1551 know the key. A Dictionary is created with curly braces: > | |
856 | 1552 |
161 | 1553 :let uk2nl = {'one': 'een', 'two': 'twee', 'three': 'drie'} |
1554 | |
164 | 1555 Now you can lookup words by putting the key in square brackets: > |
161 | 1556 |
1557 :echo uk2nl['two'] | |
1558 < twee ~ | |
1559 | |
1560 The generic form for defining a Dictionary is: > | |
1561 | |
1562 {<key> : <value>, ...} | |
1563 | |
1564 An empty Dictionary is one without any keys: > | |
1565 | |
1566 {} | |
1567 | |
1568 The possibilities with Dictionaries are numerous. There are various functions | |
1569 for them as well. For example, you can obtain a list of the keys and loop | |
1570 over them: > | |
1571 | |
1572 :for key in keys(uk2nl) | |
1573 : echo key | |
1574 :endfor | |
1575 < three ~ | |
1576 one ~ | |
1577 two ~ | |
1578 | |
1620 | 1579 You will notice the keys are not ordered. You can sort the list to get a |
161 | 1580 specific order: > |
1581 | |
1582 :for key in sort(keys(uk2nl)) | |
1583 : echo key | |
1584 :endfor | |
1585 < one ~ | |
1586 three ~ | |
1587 two ~ | |
1588 | |
1589 But you can never get back the order in which items are defined. For that you | |
1590 need to use a List, it stores items in an ordered sequence. | |
1591 | |
1592 | |
1593 DICTIONARY FUNCTIONS | |
1594 | |
1595 The items in a Dictionary can normally be obtained with an index in square | |
1596 brackets: > | |
1597 | |
1598 :echo uk2nl['one'] | |
1599 < een ~ | |
1600 | |
1601 A method that does the same, but without so many punctuation characters: > | |
1602 | |
1603 :echo uk2nl.one | |
1604 < een ~ | |
1605 | |
1606 This only works for a key that is made of ASCII letters, digits and the | |
1607 underscore. You can also assign a new value this way: > | |
1608 | |
1609 :let uk2nl.four = 'vier' | |
1610 :echo uk2nl | |
1611 < {'three': 'drie', 'four': 'vier', 'one': 'een', 'two': 'twee'} ~ | |
1612 | |
1613 And now for something special: you can directly define a function and store a | |
1614 reference to it in the dictionary: > | |
1615 | |
1616 :function uk2nl.translate(line) dict | |
1617 : return join(map(split(a:line), 'get(self, v:val, "???")')) | |
1618 :endfunction | |
1619 | |
1620 Let's first try it out: > | |
1621 | |
1622 :echo uk2nl.translate('three two five one') | |
1623 < drie twee ??? een ~ | |
1624 | |
1625 The first special thing you notice is the "dict" at the end of the ":function" | |
1626 line. This marks the function as being used from a Dictionary. The "self" | |
1627 local variable will then refer to that Dictionary. | |
1628 Now let's break up the complicated return command: > | |
1629 | |
1630 split(a:line) | |
1631 | |
2709 | 1632 The split() function takes a string, chops it into whitespace separated words |
161 | 1633 and returns a list with these words. Thus in the example it returns: > |
1634 | |
1635 :echo split('three two five one') | |
1636 < ['three', 'two', 'five', 'one'] ~ | |
1637 | |
1638 This list is the first argument to the map() function. This will go through | |
1639 the list, evaluating its second argument with "v:val" set to the value of each | |
1640 item. This is a shortcut to using a for loop. This command: > | |
1641 | |
1642 :let alist = map(split(a:line), 'get(self, v:val, "???")') | |
1643 | |
1644 Is equivalent to: > | |
1645 | |
1646 :let alist = split(a:line) | |
1647 :for idx in range(len(alist)) | |
1648 : let alist[idx] = get(self, alist[idx], "???") | |
1649 :endfor | |
1650 | |
1651 The get() function checks if a key is present in a Dictionary. If it is, then | |
1652 the value is retrieved. If it isn't, then the default value is returned, in | |
164 | 1653 the example it's '???'. This is a convenient way to handle situations where a |
161 | 1654 key may not be present and you don't want an error message. |
1655 | |
1656 The join() function does the opposite of split(): it joins together a list of | |
1657 words, putting a space in between. | |
1658 This combination of split(), map() and join() is a nice way to filter a line | |
1659 of words in a very compact way. | |
1660 | |
1661 | |
1662 OBJECT ORIENTED PROGRAMMING | |
1663 | |
1664 Now that you can put both values and functions in a Dictionary, you can | |
1665 actually use a Dictionary like an object. | |
1666 Above we used a Dictionary for translating Dutch to English. We might want | |
1667 to do the same for other languages. Let's first make an object (aka | |
1668 Dictionary) that has the translate function, but no words to translate: > | |
1669 | |
1670 :let transdict = {} | |
1671 :function transdict.translate(line) dict | |
1672 : return join(map(split(a:line), 'get(self.words, v:val, "???")')) | |
1673 :endfunction | |
1674 | |
1675 It's slightly different from the function above, using 'self.words' to lookup | |
1676 word translations. But we don't have a self.words. Thus you could call this | |
1677 an abstract class. | |
1678 | |
1679 Now we can instantiate a Dutch translation object: > | |
1680 | |
1681 :let uk2nl = copy(transdict) | |
1682 :let uk2nl.words = {'one': 'een', 'two': 'twee', 'three': 'drie'} | |
1683 :echo uk2nl.translate('three one') | |
1684 < drie een ~ | |
1685 | |
1686 And a German translator: > | |
1687 | |
1688 :let uk2de = copy(transdict) | |
9286
64035abb986b
commit https://github.com/vim/vim/commit/c95a302a4c42ec8230473cd4a5e0064d0a143aa8
Christian Brabandt <cb@256bit.org>
parents:
9227
diff
changeset
|
1689 :let uk2de.words = {'one': 'eins', 'two': 'zwei', 'three': 'drei'} |
161 | 1690 :echo uk2de.translate('three one') |
9286
64035abb986b
commit https://github.com/vim/vim/commit/c95a302a4c42ec8230473cd4a5e0064d0a143aa8
Christian Brabandt <cb@256bit.org>
parents:
9227
diff
changeset
|
1691 < drei eins ~ |
161 | 1692 |
1693 You see that the copy() function is used to make a copy of the "transdict" | |
1694 Dictionary and then the copy is changed to add the words. The original | |
1695 remains the same, of course. | |
1696 | |
1697 Now you can go one step further, and use your preferred translator: > | |
1698 | |
1699 :if $LANG =~ "de" | |
1700 : let trans = uk2de | |
1701 :else | |
1702 : let trans = uk2nl | |
1703 :endif | |
1704 :echo trans.translate('one two three') | |
1705 < een twee drie ~ | |
1706 | |
1707 Here "trans" refers to one of the two objects (Dictionaries). No copy is | |
1708 made. More about List and Dictionary identity can be found at |list-identity| | |
1709 and |dict-identity|. | |
1710 | |
1711 Now you might use a language that isn't supported. You can overrule the | |
1712 translate() function to do nothing: > | |
1713 | |
1714 :let uk2uk = copy(transdict) | |
1715 :function! uk2uk.translate(line) | |
1716 : return a:line | |
1717 :endfunction | |
1718 :echo uk2uk.translate('three one wladiwostok') | |
1719 < three one wladiwostok ~ | |
1720 | |
1721 Notice that a ! was used to overwrite the existing function reference. Now | |
1722 use "uk2uk" when no recognized language is found: > | |
1723 | |
1724 :if $LANG =~ "de" | |
1725 : let trans = uk2de | |
1726 :elseif $LANG =~ "nl" | |
1727 : let trans = uk2nl | |
1728 :else | |
1729 : let trans = uk2uk | |
1730 :endif | |
1731 :echo trans.translate('one two three') | |
1732 < one two three ~ | |
1733 | |
1734 For further reading see |Lists| and |Dictionaries|. | |
1735 | |
1736 ============================================================================== | |
1737 *41.9* Exceptions | |
7 | 1738 |
1739 Let's start with an example: > | |
1740 | |
1741 :try | |
1742 : read ~/templates/pascal.tmpl | |
1743 :catch /E484:/ | |
1744 : echo "Sorry, the Pascal template file cannot be found." | |
1745 :endtry | |
1746 | |
1747 The ":read" command will fail if the file does not exist. Instead of | |
1748 generating an error message, this code catches the error and gives the user a | |
2709 | 1749 nice message. |
7 | 1750 |
1751 For the commands in between ":try" and ":endtry" errors are turned into | |
1752 exceptions. An exception is a string. In the case of an error the string | |
1753 contains the error message. And every error message has a number. In this | |
1754 case, the error we catch contains "E484:". This number is guaranteed to stay | |
1755 the same (the text may change, e.g., it may be translated). | |
1756 | |
1757 When the ":read" command causes another error, the pattern "E484:" will not | |
1758 match in it. Thus this exception will not be caught and result in the usual | |
1759 error message. | |
1760 | |
1761 You might be tempted to do this: > | |
1762 | |
1763 :try | |
1764 : read ~/templates/pascal.tmpl | |
1765 :catch | |
1766 : echo "Sorry, the Pascal template file cannot be found." | |
1767 :endtry | |
1768 | |
1769 This means all errors are caught. But then you will not see errors that are | |
1770 useful, such as "E21: Cannot make changes, 'modifiable' is off". | |
1771 | |
1772 Another useful mechanism is the ":finally" command: > | |
1773 | |
1774 :let tmp = tempname() | |
1775 :try | |
22171 | 1776 : exe ".,$write " .. tmp |
1777 : exe "!filter " .. tmp | |
7 | 1778 : .,$delete |
22171 | 1779 : exe "$read " .. tmp |
7 | 1780 :finally |
1781 : call delete(tmp) | |
1782 :endtry | |
1783 | |
1784 This filters the lines from the cursor until the end of the file through the | |
1785 "filter" command, which takes a file name argument. No matter if the | |
1786 filtering works, something goes wrong in between ":try" and ":finally" or the | |
1787 user cancels the filtering by pressing CTRL-C, the "call delete(tmp)" is | |
1788 always executed. This makes sure you don't leave the temporary file behind. | |
1789 | |
1790 More information about exception handling can be found in the reference | |
1791 manual: |exception-handling|. | |
1792 | |
1793 ============================================================================== | |
161 | 1794 *41.10* Various remarks |
7 | 1795 |
1796 Here is a summary of items that apply to Vim scripts. They are also mentioned | |
1797 elsewhere, but form a nice checklist. | |
1798 | |
1799 The end-of-line character depends on the system. For Unix a single <NL> | |
23305 | 1800 character is used. For MS-Windows and the like, <CR><NL> is used. This is |
18912
ccd16426a1f9
patch 8.2.0017: OS/2 and MS-DOS are still mentioned
Bram Moolenaar <Bram@vim.org>
parents:
18879
diff
changeset
|
1801 important when using mappings that end in a <CR>. See |:source_crnl|. |
7 | 1802 |
1803 | |
1804 WHITE SPACE | |
1805 | |
1806 Blank lines are allowed and ignored. | |
1807 | |
1808 Leading whitespace characters (blanks and TABs) are always ignored. The | |
11062 | 1809 whitespaces between parameters (e.g. between the "set" and the "cpoptions" in |
7 | 1810 the example below) are reduced to one blank character and plays the role of a |
1811 separator, the whitespaces after the last (visible) character may or may not | |
1812 be ignored depending on the situation, see below. | |
1813 | |
1814 For a ":set" command involving the "=" (equal) sign, such as in: > | |
1815 | |
1816 :set cpoptions =aABceFst | |
1817 | |
1818 the whitespace immediately before the "=" sign is ignored. But there can be | |
1819 no whitespace after the "=" sign! | |
1820 | |
1821 To include a whitespace character in the value of an option, it must be | |
1822 escaped by a "\" (backslash) as in the following example: > | |
1823 | |
1824 :set tags=my\ nice\ file | |
1825 | |
2709 | 1826 The same example written as: > |
7 | 1827 |
1828 :set tags=my nice file | |
1829 | |
1830 will issue an error, because it is interpreted as: > | |
1831 | |
1832 :set tags=my | |
1833 :set nice | |
1834 :set file | |
1835 | |
1836 | |
1837 COMMENTS | |
1838 | |
1839 The character " (the double quote mark) starts a comment. Everything after | |
1840 and including this character until the end-of-line is considered a comment and | |
1841 is ignored, except for commands that don't consider comments, as shown in | |
1842 examples below. A comment can start on any character position on the line. | |
1843 | |
1844 There is a little "catch" with comments for some commands. Examples: > | |
1845 | |
1846 :abbrev dev development " shorthand | |
1847 :map <F3> o#include " insert include | |
1848 :execute cmd " do it | |
1849 :!ls *.c " list C files | |
1850 | |
1851 The abbreviation 'dev' will be expanded to 'development " shorthand'. The | |
1852 mapping of <F3> will actually be the whole line after the 'o# ....' including | |
1853 the '" insert include'. The "execute" command will give an error. The "!" | |
1854 command will send everything after it to the shell, causing an error for an | |
1855 unmatched '"' character. | |
1856 There can be no comment after ":map", ":abbreviate", ":execute" and "!" | |
1857 commands (there are a few more commands with this restriction). For the | |
1858 ":map", ":abbreviate" and ":execute" commands there is a trick: > | |
1859 | |
1860 :abbrev dev development|" shorthand | |
1861 :map <F3> o#include|" insert include | |
1862 :execute cmd |" do it | |
1863 | |
1864 With the '|' character the command is separated from the next one. And that | |
1146 | 1865 next command is only a comment. For the last command you need to do two |
1866 things: |:execute| and use '|': > | |
1867 :exe '!ls *.c' |" list C files | |
7 | 1868 |
1869 Notice that there is no white space before the '|' in the abbreviation and | |
1870 mapping. For these commands, any character until the end-of-line or '|' is | |
1871 included. As a consequence of this behavior, you don't always see that | |
1872 trailing whitespace is included: > | |
1873 | |
1874 :map <F4> o#include | |
1875 | |
1146 | 1876 To spot these problems, you can set the 'list' option when editing vimrc |
7 | 1877 files. |
1878 | |
1146 | 1879 For Unix there is one special way to comment a line, that allows making a Vim |
1880 script executable: > | |
1881 #!/usr/bin/env vim -S | |
1882 echo "this is a Vim script" | |
1883 quit | |
1884 | |
1885 The "#" command by itself lists a line with the line number. Adding an | |
1886 exclamation mark changes it into doing nothing, so that you can add the shell | |
1887 command to execute the rest of the file. |:#!| |-S| | |
1888 | |
7 | 1889 |
1890 PITFALLS | |
1891 | |
1892 Even bigger problem arises in the following example: > | |
1893 | |
1894 :map ,ab o#include | |
1895 :unmap ,ab | |
1896 | |
1897 Here the unmap command will not work, because it tries to unmap ",ab ". This | |
1898 does not exist as a mapped sequence. An error will be issued, which is very | |
1899 hard to identify, because the ending whitespace character in ":unmap ,ab " is | |
1900 not visible. | |
1901 | |
1902 And this is the same as what happens when one uses a comment after an 'unmap' | |
1903 command: > | |
1904 | |
1905 :unmap ,ab " comment | |
1906 | |
1907 Here the comment part will be ignored. However, Vim will try to unmap | |
1908 ',ab ', which does not exist. Rewrite it as: > | |
1909 | |
1910 :unmap ,ab| " comment | |
1911 | |
1912 | |
1913 RESTORING THE VIEW | |
1914 | |
3893 | 1915 Sometimes you want to make a change and go back to where the cursor was. |
7 | 1916 Restoring the relative position would also be nice, so that the same line |
1917 appears at the top of the window. | |
1918 This example yanks the current line, puts it above the first line in the | |
1919 file and then restores the view: > | |
1920 | |
1921 map ,p ma"aYHmbgg"aP`bzt`a | |
1922 | |
1923 What this does: > | |
1924 ma"aYHmbgg"aP`bzt`a | |
1925 < ma set mark a at cursor position | |
1926 "aY yank current line into register a | |
1927 Hmb go to top line in window and set mark b there | |
1928 gg go to first line in file | |
1929 "aP put the yanked line above it | |
1930 `b go back to top line in display | |
1931 zt position the text in the window as before | |
1932 `a go back to saved cursor position | |
1933 | |
1934 | |
1935 PACKAGING | |
1936 | |
1937 To avoid your function names to interfere with functions that you get from | |
1938 others, use this scheme: | |
1939 - Prepend a unique string before each function name. I often use an | |
1940 abbreviation. For example, "OW_" is used for the option window functions. | |
1941 - Put the definition of your functions together in a file. Set a global | |
1942 variable to indicate that the functions have been loaded. When sourcing the | |
1943 file again, first unload the functions. | |
1944 Example: > | |
1945 | |
1946 " This is the XXX package | |
1947 | |
1948 if exists("XXX_loaded") | |
1949 delfun XXX_one | |
1950 delfun XXX_two | |
1951 endif | |
1952 | |
1953 function XXX_one(a) | |
1954 ... body of function ... | |
1955 endfun | |
1956 | |
1957 function XXX_two(b) | |
1958 ... body of function ... | |
1959 endfun | |
1960 | |
1961 let XXX_loaded = 1 | |
1962 | |
1963 ============================================================================== | |
161 | 1964 *41.11* Writing a plugin *write-plugin* |
7 | 1965 |
1966 You can write a Vim script in such a way that many people can use it. This is | |
1967 called a plugin. Vim users can drop your script in their plugin directory and | |
1968 use its features right away |add-plugin|. | |
1969 | |
1970 There are actually two types of plugins: | |
1971 | |
1972 global plugins: For all types of files. | |
1973 filetype plugins: Only for files of a specific type. | |
1974 | |
1975 In this section the first type is explained. Most items are also relevant for | |
1976 writing filetype plugins. The specifics for filetype plugins are in the next | |
1977 section |write-filetype-plugin|. | |
1978 | |
1979 | |
1980 NAME | |
1981 | |
1982 First of all you must choose a name for your plugin. The features provided | |
1983 by the plugin should be clear from its name. And it should be unlikely that | |
1984 someone else writes a plugin with the same name but which does something | |
1985 different. And please limit the name to 8 characters, to avoid problems on | |
18912
ccd16426a1f9
patch 8.2.0017: OS/2 and MS-DOS are still mentioned
Bram Moolenaar <Bram@vim.org>
parents:
18879
diff
changeset
|
1986 old MS-Windows systems. |
7 | 1987 |
1988 A script that corrects typing mistakes could be called "typecorr.vim". We | |
1989 will use it here as an example. | |
1990 | |
1991 For the plugin to work for everybody, it should follow a few guidelines. This | |
1992 will be explained step-by-step. The complete example plugin is at the end. | |
1993 | |
1994 | |
1995 BODY | |
1996 | |
1997 Let's start with the body of the plugin, the lines that do the actual work: > | |
1998 | |
1999 14 iabbrev teh the | |
2000 15 iabbrev otehr other | |
2001 16 iabbrev wnat want | |
2002 17 iabbrev synchronisation | |
2003 18 \ synchronization | |
2004 19 let s:count = 4 | |
2005 | |
2006 The actual list should be much longer, of course. | |
2007 | |
2008 The line numbers have only been added to explain a few things, don't put them | |
2009 in your plugin file! | |
2010 | |
2011 | |
2012 HEADER | |
2013 | |
2014 You will probably add new corrections to the plugin and soon have several | |
3830 | 2015 versions lying around. And when distributing this file, people will want to |
7 | 2016 know who wrote this wonderful plugin and where they can send remarks. |
2017 Therefore, put a header at the top of your plugin: > | |
2018 | |
2019 1 " Vim global plugin for correcting typing mistakes | |
2020 2 " Last Change: 2000 Oct 15 | |
2021 3 " Maintainer: Bram Moolenaar <Bram@vim.org> | |
2022 | |
2023 About copyright and licensing: Since plugins are very useful and it's hardly | |
2024 worth restricting their distribution, please consider making your plugin | |
2025 either public domain or use the Vim |license|. A short note about this near | |
2026 the top of the plugin should be sufficient. Example: > | |
2027 | |
2028 4 " License: This file is placed in the public domain. | |
2029 | |
2030 | |
2031 LINE CONTINUATION, AVOIDING SIDE EFFECTS *use-cpo-save* | |
2032 | |
2033 In line 18 above, the line-continuation mechanism is used |line-continuation|. | |
2034 Users with 'compatible' set will run into trouble here, they will get an error | |
2035 message. We can't just reset 'compatible', because that has a lot of side | |
2036 effects. To avoid this, we will set the 'cpoptions' option to its Vim default | |
2037 value and restore it later. That will allow the use of line-continuation and | |
2038 make the script work for most people. It is done like this: > | |
2039 | |
2040 11 let s:save_cpo = &cpo | |
2041 12 set cpo&vim | |
2042 .. | |
2043 42 let &cpo = s:save_cpo | |
3445 | 2044 43 unlet s:save_cpo |
7 | 2045 |
2046 We first store the old value of 'cpoptions' in the s:save_cpo variable. At | |
2047 the end of the plugin this value is restored. | |
2048 | |
2049 Notice that a script-local variable is used |s:var|. A global variable could | |
2050 already be in use for something else. Always use script-local variables for | |
2051 things that are only used in the script. | |
2052 | |
2053 | |
2054 NOT LOADING | |
2055 | |
2056 It's possible that a user doesn't always want to load this plugin. Or the | |
2057 system administrator has dropped it in the system-wide plugin directory, but a | |
2058 user has his own plugin he wants to use. Then the user must have a chance to | |
2059 disable loading this specific plugin. This will make it possible: > | |
2060 | |
2325
f177a6431514
Better implementation of creating the Color Scheme menu. (Juergen Kraemer)
Bram Moolenaar <bram@vim.org>
parents:
2301
diff
changeset
|
2061 6 if exists("g:loaded_typecorr") |
7 | 2062 7 finish |
2063 8 endif | |
2325
f177a6431514
Better implementation of creating the Color Scheme menu. (Juergen Kraemer)
Bram Moolenaar <bram@vim.org>
parents:
2301
diff
changeset
|
2064 9 let g:loaded_typecorr = 1 |
7 | 2065 |
2066 This also avoids that when the script is loaded twice it would cause error | |
2067 messages for redefining functions and cause trouble for autocommands that are | |
2068 added twice. | |
2069 | |
2325
f177a6431514
Better implementation of creating the Color Scheme menu. (Juergen Kraemer)
Bram Moolenaar <bram@vim.org>
parents:
2301
diff
changeset
|
2070 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
|
2071 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
|
2072 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
|
2073 function). |
f177a6431514
Better implementation of creating the Color Scheme menu. (Juergen Kraemer)
Bram Moolenaar <bram@vim.org>
parents:
2301
diff
changeset
|
2074 |
f177a6431514
Better implementation of creating the Color Scheme menu. (Juergen Kraemer)
Bram Moolenaar <bram@vim.org>
parents:
2301
diff
changeset
|
2075 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
|
2076 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
|
2077 |
7 | 2078 |
2079 MAPPING | |
2080 | |
2081 Now let's make the plugin more interesting: We will add a mapping that adds a | |
2082 correction for the word under the cursor. We could just pick a key sequence | |
2083 for this mapping, but the user might already use it for something else. To | |
2084 allow the user to define which keys a mapping in a plugin uses, the <Leader> | |
2085 item can be used: > | |
2086 | |
21825 | 2087 22 map <unique> <Leader>a <Plug>TypecorrAdd; |
2088 | |
2089 The "<Plug>TypecorrAdd;" thing will do the work, more about that further on. | |
7 | 2090 |
2091 The user can set the "mapleader" variable to the key sequence that he wants | |
2092 this mapping to start with. Thus if the user has done: > | |
2093 | |
2094 let mapleader = "_" | |
2095 | |
2096 the mapping will define "_a". If the user didn't do this, the default value | |
2097 will be used, which is a backslash. Then a map for "\a" will be defined. | |
2098 | |
2099 Note that <unique> is used, this will cause an error message if the mapping | |
2100 already happened to exist. |:map-<unique>| | |
2101 | |
2102 But what if the user wants to define his own key sequence? We can allow that | |
2103 with this mechanism: > | |
2104 | |
21825 | 2105 21 if !hasmapto('<Plug>TypecorrAdd;') |
2106 22 map <unique> <Leader>a <Plug>TypecorrAdd; | |
7 | 2107 23 endif |
2108 | |
21991 | 2109 This checks if a mapping to "<Plug>TypecorrAdd;" already exists, and only |
7 | 2110 defines the mapping from "<Leader>a" if it doesn't. The user then has a |
2111 chance of putting this in his vimrc file: > | |
2112 | |
21825 | 2113 map ,c <Plug>TypecorrAdd; |
7 | 2114 |
2115 Then the mapped key sequence will be ",c" instead of "_a" or "\a". | |
2116 | |
2117 | |
2118 PIECES | |
2119 | |
2120 If a script gets longer, you often want to break up the work in pieces. You | |
2121 can use functions or mappings for this. But you don't want these functions | |
2122 and mappings to interfere with the ones from other scripts. For example, you | |
2123 could define a function Add(), but another script could try to define the same | |
2124 function. To avoid this, we define the function local to the script by | |
2125 prepending it with "s:". | |
2126 | |
2127 We will define a function that adds a new typing correction: > | |
2128 | |
2129 30 function s:Add(from, correct) | |
22171 | 2130 31 let to = input("type the correction for " .. a:from .. ": ") |
2131 32 exe ":iabbrev " .. a:from .. " " .. to | |
7 | 2132 .. |
2133 36 endfunction | |
2134 | |
2135 Now we can call the function s:Add() from within this script. If another | |
2136 script also defines s:Add(), it will be local to that script and can only | |
2137 be called from the script it was defined in. There can also be a global Add() | |
2138 function (without the "s:"), which is again another function. | |
2139 | |
2140 <SID> can be used with mappings. It generates a script ID, which identifies | |
2141 the current script. In our typing correction plugin we use it like this: > | |
2142 | |
21825 | 2143 24 noremap <unique> <script> <Plug>TypecorrAdd; <SID>Add |
7 | 2144 .. |
2145 28 noremap <SID>Add :call <SID>Add(expand("<cword>"), 1)<CR> | |
2146 | |
2147 Thus when a user types "\a", this sequence is invoked: > | |
2148 | |
21825 | 2149 \a -> <Plug>TypecorrAdd; -> <SID>Add -> :call <SID>Add() |
2150 | |
2151 If another script also maps <SID>Add, it will get another script ID and | |
7 | 2152 thus define another mapping. |
2153 | |
2154 Note that instead of s:Add() we use <SID>Add() here. That is because the | |
2155 mapping is typed by the user, thus outside of the script. The <SID> is | |
2156 translated to the script ID, so that Vim knows in which script to look for | |
2157 the Add() function. | |
2158 | |
2159 This is a bit complicated, but it's required for the plugin to work together | |
2160 with other plugins. The basic rule is that you use <SID>Add() in mappings and | |
2161 s:Add() in other places (the script itself, autocommands, user commands). | |
2162 | |
2163 We can also add a menu entry to do the same as the mapping: > | |
2164 | |
2165 26 noremenu <script> Plugin.Add\ Correction <SID>Add | |
2166 | |
2167 The "Plugin" menu is recommended for adding menu items for plugins. In this | |
2168 case only one item is used. When adding more items, creating a submenu is | |
2169 recommended. For example, "Plugin.CVS" could be used for a plugin that offers | |
2170 CVS operations "Plugin.CVS.checkin", "Plugin.CVS.checkout", etc. | |
2171 | |
2172 Note that in line 28 ":noremap" is used to avoid that any other mappings cause | |
2173 trouble. Someone may have remapped ":call", for example. In line 24 we also | |
2174 use ":noremap", but we do want "<SID>Add" to be remapped. This is why | |
2175 "<script>" is used here. This only allows mappings which are local to the | |
2176 script. |:map-<script>| The same is done in line 26 for ":noremenu". | |
2177 |:menu-<script>| | |
2178 | |
2179 | |
2180 <SID> AND <Plug> *using-<Plug>* | |
2181 | |
2182 Both <SID> and <Plug> are used to avoid that mappings of typed keys interfere | |
2183 with mappings that are only to be used from other mappings. Note the | |
2184 difference between using <SID> and <Plug>: | |
2185 | |
2186 <Plug> is visible outside of the script. It is used for mappings which the | |
2187 user might want to map a key sequence to. <Plug> is a special code | |
2188 that a typed key will never produce. | |
2189 To make it very unlikely that other plugins use the same sequence of | |
2190 characters, use this structure: <Plug> scriptname mapname | |
2191 In our example the scriptname is "Typecorr" and the mapname is "Add". | |
21825 | 2192 We add a semicolon as the terminator. This results in |
2193 "<Plug>TypecorrAdd;". Only the first character of scriptname and | |
2194 mapname is uppercase, so that we can see where mapname starts. | |
7 | 2195 |
2196 <SID> is the script ID, a unique identifier for a script. | |
2197 Internally Vim translates <SID> to "<SNR>123_", where "123" can be any | |
2198 number. Thus a function "<SID>Add()" will have a name "<SNR>11_Add()" | |
2199 in one script, and "<SNR>22_Add()" in another. You can see this if | |
2200 you use the ":function" command to get a list of functions. The | |
2201 translation of <SID> in mappings is exactly the same, that's how you | |
2202 can call a script-local function from a mapping. | |
2203 | |
2204 | |
2205 USER COMMAND | |
2206 | |
2207 Now let's add a user command to add a correction: > | |
2208 | |
2209 38 if !exists(":Correct") | |
2210 39 command -nargs=1 Correct :call s:Add(<q-args>, 0) | |
2211 40 endif | |
2212 | |
2213 The user command is defined only if no command with the same name already | |
2214 exists. Otherwise we would get an error here. Overriding the existing user | |
2215 command with ":command!" is not a good idea, this would probably make the user | |
2216 wonder why the command he defined himself doesn't work. |:command| | |
2217 | |
2218 | |
2219 SCRIPT VARIABLES | |
2220 | |
2221 When a variable starts with "s:" it is a script variable. It can only be used | |
2222 inside a script. Outside the script it's not visible. This avoids trouble | |
2223 with using the same variable name in different scripts. The variables will be | |
2224 kept as long as Vim is running. And the same variables are used when sourcing | |
2225 the same script again. |s:var| | |
2226 | |
2227 The fun is that these variables can also be used in functions, autocommands | |
2228 and user commands that are defined in the script. In our example we can add | |
2229 a few lines to count the number of corrections: > | |
2230 | |
2231 19 let s:count = 4 | |
2232 .. | |
2233 30 function s:Add(from, correct) | |
2234 .. | |
2235 34 let s:count = s:count + 1 | |
22171 | 2236 35 echo s:count .. " corrections now" |
7 | 2237 36 endfunction |
2238 | |
2239 First s:count is initialized to 4 in the script itself. When later the | |
2240 s:Add() function is called, it increments s:count. It doesn't matter from | |
2241 where the function was called, since it has been defined in the script, it | |
2242 will use the local variables from this script. | |
2243 | |
2244 | |
2245 THE RESULT | |
2246 | |
2247 Here is the resulting complete example: > | |
2248 | |
2249 1 " Vim global plugin for correcting typing mistakes | |
2250 2 " Last Change: 2000 Oct 15 | |
2251 3 " Maintainer: Bram Moolenaar <Bram@vim.org> | |
2252 4 " License: This file is placed in the public domain. | |
2253 5 | |
2325
f177a6431514
Better implementation of creating the Color Scheme menu. (Juergen Kraemer)
Bram Moolenaar <bram@vim.org>
parents:
2301
diff
changeset
|
2254 6 if exists("g:loaded_typecorr") |
7 | 2255 7 finish |
2256 8 endif | |
2325
f177a6431514
Better implementation of creating the Color Scheme menu. (Juergen Kraemer)
Bram Moolenaar <bram@vim.org>
parents:
2301
diff
changeset
|
2257 9 let g:loaded_typecorr = 1 |
7 | 2258 10 |
2259 11 let s:save_cpo = &cpo | |
2260 12 set cpo&vim | |
2261 13 | |
2262 14 iabbrev teh the | |
2263 15 iabbrev otehr other | |
2264 16 iabbrev wnat want | |
2265 17 iabbrev synchronisation | |
2266 18 \ synchronization | |
2267 19 let s:count = 4 | |
2268 20 | |
21825 | 2269 21 if !hasmapto('<Plug>TypecorrAdd;') |
2270 22 map <unique> <Leader>a <Plug>TypecorrAdd; | |
7 | 2271 23 endif |
21825 | 2272 24 noremap <unique> <script> <Plug>TypecorrAdd; <SID>Add |
7 | 2273 25 |
2274 26 noremenu <script> Plugin.Add\ Correction <SID>Add | |
2275 27 | |
2276 28 noremap <SID>Add :call <SID>Add(expand("<cword>"), 1)<CR> | |
2277 29 | |
2278 30 function s:Add(from, correct) | |
22171 | 2279 31 let to = input("type the correction for " .. a:from .. ": ") |
2280 32 exe ":iabbrev " .. a:from .. " " .. to | |
7 | 2281 33 if a:correct | exe "normal viws\<C-R>\" \b\e" | endif |
2282 34 let s:count = s:count + 1 | |
22171 | 2283 35 echo s:count .. " corrections now" |
7 | 2284 36 endfunction |
2285 37 | |
2286 38 if !exists(":Correct") | |
2287 39 command -nargs=1 Correct :call s:Add(<q-args>, 0) | |
2288 40 endif | |
2289 41 | |
2290 42 let &cpo = s:save_cpo | |
3445 | 2291 43 unlet s:save_cpo |
7 | 2292 |
2293 Line 33 wasn't explained yet. It applies the new correction to the word under | |
2294 the cursor. The |:normal| command is used to use the new abbreviation. Note | |
2295 that mappings and abbreviations are expanded here, even though the function | |
2296 was called from a mapping defined with ":noremap". | |
2297 | |
2298 Using "unix" for the 'fileformat' option is recommended. The Vim scripts will | |
2299 then work everywhere. Scripts with 'fileformat' set to "dos" do not work on | |
2300 Unix. Also see |:source_crnl|. To be sure it is set right, do this before | |
2301 writing the file: > | |
2302 | |
2303 :set fileformat=unix | |
2304 | |
2305 | |
2306 DOCUMENTATION *write-local-help* | |
2307 | |
2308 It's a good idea to also write some documentation for your plugin. Especially | |
2309 when its behavior can be changed by the user. See |add-local-help| for how | |
2310 they are installed. | |
2311 | |
2312 Here is a simple example for a plugin help file, called "typecorr.txt": > | |
2313 | |
2314 1 *typecorr.txt* Plugin for correcting typing mistakes | |
2315 2 | |
2316 3 If you make typing mistakes, this plugin will have them corrected | |
2317 4 automatically. | |
2318 5 | |
2319 6 There are currently only a few corrections. Add your own if you like. | |
2320 7 | |
2321 8 Mappings: | |
21825 | 2322 9 <Leader>a or <Plug>TypecorrAdd; |
7 | 2323 10 Add a correction for the word under the cursor. |
2324 11 | |
2325 12 Commands: | |
2326 13 :Correct {word} | |
2327 14 Add a correction for {word}. | |
2328 15 | |
2329 16 *typecorr-settings* | |
2330 17 This plugin doesn't have any settings. | |
2331 | |
2332 The first line is actually the only one for which the format matters. It will | |
2333 be extracted from the help file to be put in the "LOCAL ADDITIONS:" section of | |
2334 help.txt |local-additions|. The first "*" must be in the first column of the | |
2335 first line. After adding your help file do ":help" and check that the entries | |
2336 line up nicely. | |
2337 | |
2338 You can add more tags inside ** in your help file. But be careful not to use | |
2339 existing help tags. You would probably use the name of your plugin in most of | |
2340 them, like "typecorr-settings" in the example. | |
2341 | |
2342 Using references to other parts of the help in || is recommended. This makes | |
2343 it easy for the user to find associated help. | |
2344 | |
2345 | |
2346 FILETYPE DETECTION *plugin-filetype* | |
2347 | |
2348 If your filetype is not already detected by Vim, you should create a filetype | |
2349 detection snippet in a separate file. It is usually in the form of an | |
2350 autocommand that sets the filetype when the file name matches a pattern. | |
2351 Example: > | |
2352 | |
2353 au BufNewFile,BufRead *.foo set filetype=foofoo | |
2354 | |
2355 Write this single-line file as "ftdetect/foofoo.vim" in the first directory | |
2356 that appears in 'runtimepath'. For Unix that would be | |
2357 "~/.vim/ftdetect/foofoo.vim". The convention is to use the name of the | |
2358 filetype for the script name. | |
2359 | |
2360 You can make more complicated checks if you like, for example to inspect the | |
2361 contents of the file to recognize the language. Also see |new-filetype|. | |
2362 | |
2363 | |
2364 SUMMARY *plugin-special* | |
2365 | |
2366 Summary of special things to use in a plugin: | |
2367 | |
2368 s:name Variables local to the script. | |
2369 | |
2370 <SID> Script-ID, used for mappings and functions local to | |
2371 the script. | |
2372 | |
2373 hasmapto() Function to test if the user already defined a mapping | |
2374 for functionality the script offers. | |
2375 | |
2376 <Leader> Value of "mapleader", which the user defines as the | |
2377 keys that plugin mappings start with. | |
2378 | |
2379 :map <unique> Give a warning if a mapping already exists. | |
2380 | |
2381 :noremap <script> Use only mappings local to the script, not global | |
2382 mappings. | |
2383 | |
2384 exists(":Cmd") Check if a user command already exists. | |
2385 | |
2386 ============================================================================== | |
161 | 2387 *41.12* Writing a filetype plugin *write-filetype-plugin* *ftplugin* |
7 | 2388 |
2389 A filetype plugin is like a global plugin, except that it sets options and | |
2390 defines mappings for the current buffer only. See |add-filetype-plugin| for | |
2391 how this type of plugin is used. | |
2392 | |
161 | 2393 First read the section on global plugins above |41.11|. All that is said there |
7 | 2394 also applies to filetype plugins. There are a few extras, which are explained |
2395 here. The essential thing is that a filetype plugin should only have an | |
2396 effect on the current buffer. | |
2397 | |
2398 | |
2399 DISABLING | |
2400 | |
2401 If you are writing a filetype plugin to be used by many people, they need a | |
2402 chance to disable loading it. Put this at the top of the plugin: > | |
2403 | |
2404 " Only do this when not done yet for this buffer | |
2405 if exists("b:did_ftplugin") | |
2406 finish | |
2407 endif | |
2408 let b:did_ftplugin = 1 | |
2409 | |
2410 This also needs to be used to avoid that the same plugin is executed twice for | |
2411 the same buffer (happens when using an ":edit" command without arguments). | |
2412 | |
2413 Now users can disable loading the default plugin completely by making a | |
2414 filetype plugin with only this line: > | |
2415 | |
2416 let b:did_ftplugin = 1 | |
2417 | |
2418 This does require that the filetype plugin directory comes before $VIMRUNTIME | |
2419 in 'runtimepath'! | |
2420 | |
2421 If you do want to use the default plugin, but overrule one of the settings, | |
2422 you can write the different setting in a script: > | |
2423 | |
2424 setlocal textwidth=70 | |
2425 | |
2426 Now write this in the "after" directory, so that it gets sourced after the | |
2427 distributed "vim.vim" ftplugin |after-directory|. For Unix this would be | |
2428 "~/.vim/after/ftplugin/vim.vim". Note that the default plugin will have set | |
2429 "b:did_ftplugin", but it is ignored here. | |
2430 | |
2431 | |
2432 OPTIONS | |
2433 | |
2434 To make sure the filetype plugin only affects the current buffer use the > | |
2435 | |
2436 :setlocal | |
2437 | |
2438 command to set options. And only set options which are local to a buffer (see | |
2439 the help for the option to check that). When using |:setlocal| for global | |
2440 options or options local to a window, the value will change for many buffers, | |
2441 and that is not what a filetype plugin should do. | |
2442 | |
2443 When an option has a value that is a list of flags or items, consider using | |
2444 "+=" and "-=" to keep the existing value. Be aware that the user may have | |
2445 changed an option value already. First resetting to the default value and | |
2698
b6471224d2af
Updated runtime files and translations.
Bram Moolenaar <bram@vim.org>
parents:
2662
diff
changeset
|
2446 then changing it is often a good idea. Example: > |
7 | 2447 |
2448 :setlocal formatoptions& formatoptions+=ro | |
2449 | |
2450 | |
2451 MAPPINGS | |
2452 | |
2453 To make sure mappings will only work in the current buffer use the > | |
2454 | |
2455 :map <buffer> | |
2456 | |
2457 command. This needs to be combined with the two-step mapping explained above. | |
2458 An example of how to define functionality in a filetype plugin: > | |
2459 | |
21825 | 2460 if !hasmapto('<Plug>JavaImport;') |
2461 map <buffer> <unique> <LocalLeader>i <Plug>JavaImport; | |
7 | 2462 endif |
21825 | 2463 noremap <buffer> <unique> <Plug>JavaImport; oimport ""<Left><Esc> |
7 | 2464 |
2465 |hasmapto()| is used to check if the user has already defined a map to | |
21825 | 2466 <Plug>JavaImport;. If not, then the filetype plugin defines the default |
7 | 2467 mapping. This starts with |<LocalLeader>|, which allows the user to select |
2468 the key(s) he wants filetype plugin mappings to start with. The default is a | |
2469 backslash. | |
2470 "<unique>" is used to give an error message if the mapping already exists or | |
2471 overlaps with an existing mapping. | |
2472 |:noremap| is used to avoid that any other mappings that the user has defined | |
2473 interferes. You might want to use ":noremap <script>" to allow remapping | |
2474 mappings defined in this script that start with <SID>. | |
2475 | |
2476 The user must have a chance to disable the mappings in a filetype plugin, | |
2477 without disabling everything. Here is an example of how this is done for a | |
2478 plugin for the mail filetype: > | |
2479 | |
2480 " Add mappings, unless the user didn't want this. | |
2481 if !exists("no_plugin_maps") && !exists("no_mail_maps") | |
2482 " Quote text by inserting "> " | |
21825 | 2483 if !hasmapto('<Plug>MailQuote;') |
2484 vmap <buffer> <LocalLeader>q <Plug>MailQuote; | |
2485 nmap <buffer> <LocalLeader>q <Plug>MailQuote; | |
7 | 2486 endif |
21825 | 2487 vnoremap <buffer> <Plug>MailQuote; :s/^/> /<CR> |
2488 nnoremap <buffer> <Plug>MailQuote; :.,$s/^/> /<CR> | |
7 | 2489 endif |
2490 | |
2491 Two global variables are used: | |
11262 | 2492 |no_plugin_maps| disables mappings for all filetype plugins |
2493 |no_mail_maps| disables mappings for the "mail" filetype | |
7 | 2494 |
2495 | |
2496 USER COMMANDS | |
2497 | |
2498 To add a user command for a specific file type, so that it can only be used in | |
2499 one buffer, use the "-buffer" argument to |:command|. Example: > | |
2500 | |
2501 :command -buffer Make make %:r.s | |
2502 | |
2503 | |
2504 VARIABLES | |
2505 | |
2506 A filetype plugin will be sourced for each buffer of the type it's for. Local | |
2507 script variables |s:var| will be shared between all invocations. Use local | |
2508 buffer variables |b:var| if you want a variable specifically for one buffer. | |
2509 | |
2510 | |
2511 FUNCTIONS | |
2512 | |
2513 When defining a function, this only needs to be done once. But the filetype | |
2514 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
|
2515 This construct makes sure the function is only defined once: > |
7 | 2516 |
2517 :if !exists("*s:Func") | |
2518 : function s:Func(arg) | |
2519 : ... | |
2520 : endfunction | |
2521 :endif | |
2522 < | |
2523 | |
8061
abd64cf67bcf
commit https://github.com/vim/vim/commit/38a55639d603823efcf2d2fdf542dbffdeb60b75
Christian Brabandt <cb@256bit.org>
parents:
7924
diff
changeset
|
2524 UNDO *undo_indent* *undo_ftplugin* |
7 | 2525 |
2526 When the user does ":setfiletype xyz" the effect of the previous filetype | |
2527 should be undone. Set the b:undo_ftplugin variable to the commands that will | |
2528 undo the settings in your filetype plugin. Example: > | |
2529 | |
2530 let b:undo_ftplugin = "setlocal fo< com< tw< commentstring<" | |
22171 | 2531 \ .. "| unlet b:match_ignorecase b:match_words b:match_skip" |
7 | 2532 |
2533 Using ":setlocal" with "<" after the option name resets the option to its | |
2534 global value. That is mostly the best way to reset the option value. | |
2535 | |
2536 This does require removing the "C" flag from 'cpoptions' to allow line | |
2537 continuation, as mentioned above |use-cpo-save|. | |
2538 | |
8061
abd64cf67bcf
commit https://github.com/vim/vim/commit/38a55639d603823efcf2d2fdf542dbffdeb60b75
Christian Brabandt <cb@256bit.org>
parents:
7924
diff
changeset
|
2539 For undoing the effect of an indent script, the b:undo_indent variable should |
abd64cf67bcf
commit https://github.com/vim/vim/commit/38a55639d603823efcf2d2fdf542dbffdeb60b75
Christian Brabandt <cb@256bit.org>
parents:
7924
diff
changeset
|
2540 be set accordingly. |
abd64cf67bcf
commit https://github.com/vim/vim/commit/38a55639d603823efcf2d2fdf542dbffdeb60b75
Christian Brabandt <cb@256bit.org>
parents:
7924
diff
changeset
|
2541 |
7 | 2542 |
2543 FILE NAME | |
2544 | |
2545 The filetype must be included in the file name |ftplugin-name|. Use one of | |
2546 these three forms: | |
2547 | |
2548 .../ftplugin/stuff.vim | |
2549 .../ftplugin/stuff_foo.vim | |
2550 .../ftplugin/stuff/bar.vim | |
2551 | |
2552 "stuff" is the filetype, "foo" and "bar" are arbitrary names. | |
2553 | |
2554 | |
2555 SUMMARY *ftplugin-special* | |
2556 | |
2557 Summary of special things to use in a filetype plugin: | |
2558 | |
2559 <LocalLeader> Value of "maplocalleader", which the user defines as | |
2560 the keys that filetype plugin mappings start with. | |
2561 | |
2562 :map <buffer> Define a mapping local to the buffer. | |
2563 | |
2564 :noremap <script> Only remap mappings defined in this script that start | |
2565 with <SID>. | |
2566 | |
2567 :setlocal Set an option for the current buffer only. | |
2568 | |
2569 :command -buffer Define a user command local to the buffer. | |
2570 | |
2571 exists("*s:Func") Check if a function was already defined. | |
2572 | |
2573 Also see |plugin-special|, the special things used for all plugins. | |
2574 | |
2575 ============================================================================== | |
161 | 2576 *41.13* Writing a compiler plugin *write-compiler-plugin* |
7 | 2577 |
2578 A compiler plugin sets options for use with a specific compiler. The user can | |
2579 load it with the |:compiler| command. The main use is to set the | |
2580 'errorformat' and 'makeprg' options. | |
2581 | |
2582 Easiest is to have a look at examples. This command will edit all the default | |
2583 compiler plugins: > | |
2584 | |
2585 :next $VIMRUNTIME/compiler/*.vim | |
2586 | |
2587 Use |:next| to go to the next plugin file. | |
2588 | |
2589 There are two special items about these files. First is a mechanism to allow | |
2590 a user to overrule or add to the default file. The default files start with: > | |
2591 | |
2592 :if exists("current_compiler") | |
2593 : finish | |
2594 :endif | |
2595 :let current_compiler = "mine" | |
2596 | |
2597 When you write a compiler file and put it in your personal runtime directory | |
2598 (e.g., ~/.vim/compiler for Unix), you set the "current_compiler" variable to | |
2599 make the default file skip the settings. | |
570 | 2600 *:CompilerSet* |
7 | 2601 The second mechanism is to use ":set" for ":compiler!" and ":setlocal" for |
2602 ":compiler". Vim defines the ":CompilerSet" user command for this. However, | |
2603 older Vim versions don't, thus your plugin should define it then. This is an | |
2604 example: > | |
2605 | |
2606 if exists(":CompilerSet") != 2 | |
2607 command -nargs=* CompilerSet setlocal <args> | |
2608 endif | |
2609 CompilerSet errorformat& " use the default 'errorformat' | |
2610 CompilerSet makeprg=nmake | |
2611 | |
2612 When you write a compiler plugin for the Vim distribution or for a system-wide | |
2613 runtime directory, use the mechanism mentioned above. When | |
2614 "current_compiler" was already set by a user plugin nothing will be done. | |
2615 | |
2616 When you write a compiler plugin to overrule settings from a default plugin, | |
2617 don't check "current_compiler". This plugin is supposed to be loaded | |
2618 last, thus it should be in a directory at the end of 'runtimepath'. For Unix | |
2619 that could be ~/.vim/after/compiler. | |
2620 | |
2621 ============================================================================== | |
170 | 2622 *41.14* Writing a plugin that loads quickly *write-plugin-quickload* |
2623 | |
2624 A plugin may grow and become quite long. The startup delay may become | |
1620 | 2625 noticeable, while you hardly ever use the plugin. Then it's time for a |
170 | 2626 quickload plugin. |
2627 | |
2628 The basic idea is that the plugin is loaded twice. The first time user | |
2629 commands and mappings are defined that offer the functionality. The second | |
2630 time the functions that implement the functionality are defined. | |
2631 | |
2632 It may sound surprising that quickload means loading a script twice. What we | |
2633 mean is that it loads quickly the first time, postponing the bulk of the | |
2634 script to the second time, which only happens when you actually use it. When | |
2635 you always use the functionality it actually gets slower! | |
2636 | |
793 | 2637 Note that since Vim 7 there is an alternative: use the |autoload| |
2638 functionality |41.15|. | |
2639 | |
170 | 2640 The following example shows how it's done: > |
2641 | |
2642 " Vim global plugin for demonstrating quick loading | |
2643 " Last Change: 2005 Feb 25 | |
2644 " Maintainer: Bram Moolenaar <Bram@vim.org> | |
2645 " License: This file is placed in the public domain. | |
2646 | |
2647 if !exists("s:did_load") | |
2648 command -nargs=* BNRead call BufNetRead(<f-args>) | |
2649 map <F19> :call BufNetWrite('something')<CR> | |
2650 | |
2651 let s:did_load = 1 | |
22171 | 2652 exe 'au FuncUndefined BufNet* source ' .. expand('<sfile>') |
170 | 2653 finish |
2654 endif | |
2655 | |
2656 function BufNetRead(...) | |
22171 | 2657 echo 'BufNetRead(' .. string(a:000) .. ')' |
170 | 2658 " read functionality here |
2659 endfunction | |
2660 | |
2661 function BufNetWrite(...) | |
22171 | 2662 echo 'BufNetWrite(' .. string(a:000) .. ')' |
170 | 2663 " write functionality here |
2664 endfunction | |
2665 | |
2666 When the script is first loaded "s:did_load" is not set. The commands between | |
2667 the "if" and "endif" will be executed. This ends in a |:finish| command, thus | |
2668 the rest of the script is not executed. | |
2669 | |
2670 The second time the script is loaded "s:did_load" exists and the commands | |
2671 after the "endif" are executed. This defines the (possible long) | |
2672 BufNetRead() and BufNetWrite() functions. | |
2673 | |
2674 If you drop this script in your plugin directory Vim will execute it on | |
2675 startup. This is the sequence of events that happens: | |
2676 | |
2677 1. The "BNRead" command is defined and the <F19> key is mapped when the script | |
2678 is sourced at startup. A |FuncUndefined| autocommand is defined. The | |
2679 ":finish" command causes the script to terminate early. | |
2680 | |
2681 2. The user types the BNRead command or presses the <F19> key. The | |
2682 BufNetRead() or BufNetWrite() function will be called. | |
856 | 2683 |
170 | 2684 3. Vim can't find the function and triggers the |FuncUndefined| autocommand |
2685 event. Since the pattern "BufNet*" matches the invoked function, the | |
2686 command "source fname" will be executed. "fname" will be equal to the name | |
2687 of the script, no matter where it is located, because it comes from | |
2688 expanding "<sfile>" (see |expand()|). | |
2689 | |
2690 4. The script is sourced again, the "s:did_load" variable exists and the | |
2691 functions are defined. | |
2692 | |
2693 Notice that the functions that are loaded afterwards match the pattern in the | |
2694 |FuncUndefined| autocommand. You must make sure that no other plugin defines | |
2695 functions that match this pattern. | |
2696 | |
2697 ============================================================================== | |
2698 *41.15* Writing library scripts *write-library-script* | |
2699 | |
2700 Some functionality will be required in several places. When this becomes more | |
2701 than a few lines you will want to put it in one script and use it from many | |
2702 scripts. We will call that one script a library script. | |
2703 | |
2704 Manually loading a library script is possible, so long as you avoid loading it | |
2705 when it's already done. You can do this with the |exists()| function. | |
2706 Example: > | |
2707 | |
2708 if !exists('*MyLibFunction') | |
2709 runtime library/mylibscript.vim | |
2710 endif | |
2711 call MyLibFunction(arg) | |
2712 | |
2713 Here you need to know that MyLibFunction() is defined in a script | |
2714 "library/mylibscript.vim" in one of the directories in 'runtimepath'. | |
2715 | |
2716 To make this a bit simpler Vim offers the autoload mechanism. Then the | |
2717 example looks like this: > | |
2718 | |
270 | 2719 call mylib#myfunction(arg) |
170 | 2720 |
2721 That's a lot simpler, isn't it? Vim will recognize the function name and when | |
2722 it's not defined search for the script "autoload/mylib.vim" in 'runtimepath'. | |
270 | 2723 That script must define the "mylib#myfunction()" function. |
170 | 2724 |
2725 You can put many other functions in the mylib.vim script, you are free to | |
2726 organize your functions in library scripts. But you must use function names | |
323 | 2727 where the part before the '#' matches the script name. Otherwise Vim would |
2728 not know what script to load. | |
170 | 2729 |
681 | 2730 If you get really enthusiastic and write lots of library scripts, you may |
170 | 2731 want to use subdirectories. Example: > |
2732 | |
270 | 2733 call netlib#ftp#read('somefile') |
170 | 2734 |
2735 For Unix the library script used for this could be: | |
2736 | |
2737 ~/.vim/autoload/netlib/ftp.vim | |
2738 | |
2739 Where the function is defined like this: > | |
2740 | |
270 | 2741 function netlib#ftp#read(fname) |
170 | 2742 " Read the file fname through ftp |
2743 endfunction | |
2744 | |
2745 Notice that the name the function is defined with is exactly the same as the | |
323 | 2746 name used for calling the function. And the part before the last '#' |
170 | 2747 exactly matches the subdirectory and script name. |
2748 | |
2749 You can use the same mechanism for variables: > | |
2750 | |
270 | 2751 let weekdays = dutch#weekdays |
170 | 2752 |
2753 This will load the script "autoload/dutch.vim", which should contain something | |
2754 like: > | |
2755 | |
270 | 2756 let dutch#weekdays = ['zondag', 'maandag', 'dinsdag', 'woensdag', |
170 | 2757 \ 'donderdag', 'vrijdag', 'zaterdag'] |
2758 | |
2759 Further reading: |autoload|. | |
2760 | |
2761 ============================================================================== | |
793 | 2762 *41.16* Distributing Vim scripts *distribute-script* |
2763 | |
2764 Vim users will look for scripts on the Vim website: http://www.vim.org. | |
2765 If you made something that is useful for others, share it! | |
2766 | |
2767 Vim scripts can be used on any system. There might not be a tar or gzip | |
2768 command. If you want to pack files together and/or compress them the "zip" | |
2769 utility is recommended. | |
2770 | |
2771 For utmost portability use Vim itself to pack scripts together. This can be | |
2772 done with the Vimball utility. See |vimball|. | |
2773 | |
799 | 2774 It's good if you add a line to allow automatic updating. See |glvs-plugins|. |
2775 | |
793 | 2776 ============================================================================== |
7 | 2777 |
2778 Next chapter: |usr_42.txt| Add new menus | |
2779 | |
14519 | 2780 Copyright: see |manual-copyright| vim:tw=78:ts=8:noet:ft=help:norl: |