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