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