Mercurial > vim
annotate runtime/doc/repeat.txt @ 22317:f75c88539e94
Added tag v8.2.1707 for changeset d275371fd1e71b874bfdb842778cde4cc6300594
author | Bram Moolenaar <Bram@vim.org> |
---|---|
date | Fri, 18 Sep 2020 22:00:04 +0200 |
parents | 0db0640e16e0 |
children | 17c4178f26ea |
rev | line source |
---|---|
21825 | 1 *repeat.txt* For Vim version 8.2. Last change: 2020 Aug 15 |
7 | 2 |
3 | |
4 VIM REFERENCE MANUAL by Bram Moolenaar | |
5 | |
6 | |
7 Repeating commands, Vim scripts and debugging *repeating* | |
8 | |
9 Chapter 26 of the user manual introduces repeating |usr_26.txt|. | |
10 | |
8748
b1a19a2f73f0
commit https://github.com/vim/vim/commit/4f3f668c8486444e53163c29d2fc79bf47eb3c82
Christian Brabandt <cb@256bit.org>
parents:
8673
diff
changeset
|
11 1. Single repeats |single-repeat| |
b1a19a2f73f0
commit https://github.com/vim/vim/commit/4f3f668c8486444e53163c29d2fc79bf47eb3c82
Christian Brabandt <cb@256bit.org>
parents:
8673
diff
changeset
|
12 2. Multiple repeats |multi-repeat| |
b1a19a2f73f0
commit https://github.com/vim/vim/commit/4f3f668c8486444e53163c29d2fc79bf47eb3c82
Christian Brabandt <cb@256bit.org>
parents:
8673
diff
changeset
|
13 3. Complex repeats |complex-repeat| |
b1a19a2f73f0
commit https://github.com/vim/vim/commit/4f3f668c8486444e53163c29d2fc79bf47eb3c82
Christian Brabandt <cb@256bit.org>
parents:
8673
diff
changeset
|
14 4. Using Vim scripts |using-scripts| |
b1a19a2f73f0
commit https://github.com/vim/vim/commit/4f3f668c8486444e53163c29d2fc79bf47eb3c82
Christian Brabandt <cb@256bit.org>
parents:
8673
diff
changeset
|
15 5. Using Vim packages |packages| |
b1a19a2f73f0
commit https://github.com/vim/vim/commit/4f3f668c8486444e53163c29d2fc79bf47eb3c82
Christian Brabandt <cb@256bit.org>
parents:
8673
diff
changeset
|
16 6. Creating Vim packages |package-create| |
b1a19a2f73f0
commit https://github.com/vim/vim/commit/4f3f668c8486444e53163c29d2fc79bf47eb3c82
Christian Brabandt <cb@256bit.org>
parents:
8673
diff
changeset
|
17 7. Debugging scripts |debug-scripts| |
b1a19a2f73f0
commit https://github.com/vim/vim/commit/4f3f668c8486444e53163c29d2fc79bf47eb3c82
Christian Brabandt <cb@256bit.org>
parents:
8673
diff
changeset
|
18 8. Profiling |profiling| |
7 | 19 |
20 ============================================================================== | |
21 1. Single repeats *single-repeat* | |
22 | |
23 *.* | |
24 . Repeat last change, with count replaced with [count]. | |
25 Also repeat a yank command, when the 'y' flag is | |
22 | 26 included in 'cpoptions'. Does not repeat a |
27 command-line command. | |
7 | 28 |
29 Simple changes can be repeated with the "." command. Without a count, the | |
30 count of the last change is used. If you enter a count, it will replace the | |
5663
1dea14d4c738
Update runtime files. Add support for systemverilog.
Bram Moolenaar <bram@vim.org>
parents:
5294
diff
changeset
|
31 last one. |v:count| and |v:count1| will be set. |
1dea14d4c738
Update runtime files. Add support for systemverilog.
Bram Moolenaar <bram@vim.org>
parents:
5294
diff
changeset
|
32 |
1dea14d4c738
Update runtime files. Add support for systemverilog.
Bram Moolenaar <bram@vim.org>
parents:
5294
diff
changeset
|
33 If the last change included a specification of a numbered register, the |
1dea14d4c738
Update runtime files. Add support for systemverilog.
Bram Moolenaar <bram@vim.org>
parents:
5294
diff
changeset
|
34 register number will be incremented. See |redo-register| for an example how |
1dea14d4c738
Update runtime files. Add support for systemverilog.
Bram Moolenaar <bram@vim.org>
parents:
5294
diff
changeset
|
35 to use this. |
1dea14d4c738
Update runtime files. Add support for systemverilog.
Bram Moolenaar <bram@vim.org>
parents:
5294
diff
changeset
|
36 |
1dea14d4c738
Update runtime files. Add support for systemverilog.
Bram Moolenaar <bram@vim.org>
parents:
5294
diff
changeset
|
37 Note that when repeating a command that used a Visual selection, the same SIZE |
1dea14d4c738
Update runtime files. Add support for systemverilog.
Bram Moolenaar <bram@vim.org>
parents:
5294
diff
changeset
|
38 of area is used, see |visual-repeat|. |
7 | 39 |
40 *@:* | |
41 @: Repeat last command-line [count] times. | |
42 {not available when compiled without the | |
43 |+cmdline_hist| feature} | |
44 | |
45 | |
46 ============================================================================== | |
47 2. Multiple repeats *multi-repeat* | |
48 | |
11494
8e5ec22db3d8
patch 8.0.0630: it is not easy to work on lines without a match
Christian Brabandt <cb@256bit.org>
parents:
10895
diff
changeset
|
49 *:g* *:global* *E148* |
7 | 50 :[range]g[lobal]/{pattern}/[cmd] |
51 Execute the Ex command [cmd] (default ":p") on the | |
52 lines within [range] where {pattern} matches. | |
53 | |
54 :[range]g[lobal]!/{pattern}/[cmd] | |
55 Execute the Ex command [cmd] (default ":p") on the | |
56 lines within [range] where {pattern} does NOT match. | |
57 | |
58 *:v* *:vglobal* | |
59 :[range]v[global]/{pattern}/[cmd] | |
60 Same as :g!. | |
61 | |
1125 | 62 Instead of the '/' which surrounds the {pattern}, you can use any other |
5239 | 63 single byte character, but not an alphabetic character, '\', '"' or '|'. |
1125 | 64 This is useful if you want to include a '/' in the search pattern or |
65 replacement string. | |
66 | |
67 For the definition of a pattern, see |pattern|. | |
68 | |
6336 | 69 NOTE [cmd] may contain a range; see |collapse| and |edit-paragraph-join| for |
70 examples. | |
71 | |
7 | 72 The global commands work by first scanning through the [range] lines and |
73 marking each line where a match occurs (for a multi-line pattern, only the | |
74 start of the match matters). | |
8876
47f17f66da3d
commit https://github.com/vim/vim/commit/03413f44167c4b5cd0012def9bb331e2518c83cf
Christian Brabandt <cb@256bit.org>
parents:
8795
diff
changeset
|
75 In a second scan the [cmd] is executed for each marked line, as if the cursor |
47f17f66da3d
commit https://github.com/vim/vim/commit/03413f44167c4b5cd0012def9bb331e2518c83cf
Christian Brabandt <cb@256bit.org>
parents:
8795
diff
changeset
|
76 was in that line. For ":v" and ":g!" the command is executed for each not |
7 | 77 marked line. If a line is deleted its mark disappears. |
78 The default for [range] is the whole buffer (1,$). Use "CTRL-C" to interrupt | |
79 the command. If an error message is given for a line, the command for that | |
80 line is aborted and the global command continues with the next marked or | |
81 unmarked line. | |
18831 | 82 *E147* |
11494
8e5ec22db3d8
patch 8.0.0630: it is not easy to work on lines without a match
Christian Brabandt <cb@256bit.org>
parents:
10895
diff
changeset
|
83 When the command is used recursively, it only works on one line. Giving a |
8e5ec22db3d8
patch 8.0.0630: it is not easy to work on lines without a match
Christian Brabandt <cb@256bit.org>
parents:
10895
diff
changeset
|
84 range is then not allowed. This is useful to find all lines that match a |
8e5ec22db3d8
patch 8.0.0630: it is not easy to work on lines without a match
Christian Brabandt <cb@256bit.org>
parents:
10895
diff
changeset
|
85 pattern and do not match another pattern: > |
8e5ec22db3d8
patch 8.0.0630: it is not easy to work on lines without a match
Christian Brabandt <cb@256bit.org>
parents:
10895
diff
changeset
|
86 :g/found/v/notfound/{cmd} |
8e5ec22db3d8
patch 8.0.0630: it is not easy to work on lines without a match
Christian Brabandt <cb@256bit.org>
parents:
10895
diff
changeset
|
87 This first finds all lines containing "found", but only executes {cmd} when |
8e5ec22db3d8
patch 8.0.0630: it is not easy to work on lines without a match
Christian Brabandt <cb@256bit.org>
parents:
10895
diff
changeset
|
88 there is no match for "notfound". |
7 | 89 |
11494
8e5ec22db3d8
patch 8.0.0630: it is not easy to work on lines without a match
Christian Brabandt <cb@256bit.org>
parents:
10895
diff
changeset
|
90 To execute a non-Ex command, you can use the `:normal` command: > |
7 | 91 :g/pat/normal {commands} |
92 Make sure that {commands} ends with a whole command, otherwise Vim will wait | |
93 for you to type the rest of the command for each match. The screen will not | |
94 have been updated, so you don't know what you are doing. See |:normal|. | |
95 | |
96 The undo/redo command will undo/redo the whole global command at once. | |
97 The previous context mark will only be set once (with "''" you go back to | |
98 where the cursor was before the global command). | |
99 | |
100 The global command sets both the last used search pattern and the last used | |
101 substitute pattern (this is vi compatible). This makes it easy to globally | |
102 replace a string: | |
103 :g/pat/s//PAT/g | |
104 This replaces all occurrences of "pat" with "PAT". The same can be done with: | |
105 :%s/pat/PAT/g | |
106 Which is two characters shorter! | |
107 | |
1623 | 108 When using "global" in Ex mode, a special case is using ":visual" as a |
109 command. This will move to a matching line, go to Normal mode to let you | |
110 execute commands there until you use |Q| to return to Ex mode. This will be | |
111 repeated for each matching line. While doing this you cannot use ":global". | |
112 To abort this type CTRL-C twice. | |
168 | 113 |
7 | 114 ============================================================================== |
115 3. Complex repeats *complex-repeat* | |
116 | |
117 *q* *recording* | |
118 q{0-9a-zA-Z"} Record typed characters into register {0-9a-zA-Z"} | |
119 (uppercase to append). The 'q' command is disabled | |
120 while executing a register, and it doesn't work inside | |
7233
9487ea110214
commit https://github.com/vim/vim/commit/a0ed84a26897c994512873a895b9fc54e90c6845
Christian Brabandt <cb@256bit.org>
parents:
6757
diff
changeset
|
121 a mapping and |:normal|. |
9487ea110214
commit https://github.com/vim/vim/commit/a0ed84a26897c994512873a895b9fc54e90c6845
Christian Brabandt <cb@256bit.org>
parents:
6757
diff
changeset
|
122 |
9487ea110214
commit https://github.com/vim/vim/commit/a0ed84a26897c994512873a895b9fc54e90c6845
Christian Brabandt <cb@256bit.org>
parents:
6757
diff
changeset
|
123 Note: If the register being used for recording is also |
9487ea110214
commit https://github.com/vim/vim/commit/a0ed84a26897c994512873a895b9fc54e90c6845
Christian Brabandt <cb@256bit.org>
parents:
6757
diff
changeset
|
124 used for |y| and |p| the result is most likely not |
9487ea110214
commit https://github.com/vim/vim/commit/a0ed84a26897c994512873a895b9fc54e90c6845
Christian Brabandt <cb@256bit.org>
parents:
6757
diff
changeset
|
125 what is expected, because the put will paste the |
9487ea110214
commit https://github.com/vim/vim/commit/a0ed84a26897c994512873a895b9fc54e90c6845
Christian Brabandt <cb@256bit.org>
parents:
6757
diff
changeset
|
126 recorded macro and the yank will overwrite the |
16610 | 127 recorded macro. |
7 | 128 |
20552 | 129 Note: The recording happens while you type, replaying |
130 the register happens as if the keys come from a | |
131 mapping. This matters, for example, for undo, which | |
132 only syncs when commands were typed. | |
133 | |
7 | 134 q Stops recording. (Implementation note: The 'q' that |
135 stops recording is not stored in the register, unless | |
16610 | 136 it was the result of a mapping) |
7 | 137 |
138 *@* | |
3445 | 139 @{0-9a-z".=*+} Execute the contents of register {0-9a-z".=*+} [count] |
7 | 140 times. Note that register '%' (name of the current |
141 file) and '#' (name of the alternate file) cannot be | |
2681 | 142 used. |
143 The register is executed like a mapping, that means | |
144 that the difference between 'wildchar' and 'wildcharm' | |
20552 | 145 applies, and undo might not be synced in the same way. |
2681 | 146 For "@=" you are prompted to enter an expression. The |
147 result of the expression is then executed. | |
16610 | 148 See also |@:|. |
7 | 149 |
168 | 150 *@@* *E748* |
7 | 151 @@ Repeat the previous @{0-9a-z":*} [count] times. |
152 | |
3445 | 153 :[addr]*{0-9a-z".=+} *:@* *:star* |
154 :[addr]@{0-9a-z".=*+} Execute the contents of register {0-9a-z".=*+} as an Ex | |
7 | 155 command. First set cursor at line [addr] (default is |
156 current line). When the last line in the register does | |
157 not have a <CR> it will be added automatically when | |
158 the 'e' flag is present in 'cpoptions'. | |
159 Note that the ":*" command is only recognized when the | |
160 '*' flag is present in 'cpoptions'. This is NOT the | |
161 default when 'nocompatible' is used. | |
162 For ":@=" the last used expression is used. The | |
163 result of evaluating the expression is executed as an | |
164 Ex command. | |
165 Mappings are not recognized in these commands. | |
20891
4bdc07beeadb
patch 8.2.0997: cannot execute a register containing line continuation
Bram Moolenaar <Bram@vim.org>
parents:
20552
diff
changeset
|
166 When the |line-continuation| character (\) is present |
4bdc07beeadb
patch 8.2.0997: cannot execute a register containing line continuation
Bram Moolenaar <Bram@vim.org>
parents:
20552
diff
changeset
|
167 at the beginning of a line in a linewise register, |
4bdc07beeadb
patch 8.2.0997: cannot execute a register containing line continuation
Bram Moolenaar <Bram@vim.org>
parents:
20552
diff
changeset
|
168 then it is combined with the previous line. This is |
4bdc07beeadb
patch 8.2.0997: cannot execute a register containing line continuation
Bram Moolenaar <Bram@vim.org>
parents:
20552
diff
changeset
|
169 useful for yanking and executing parts of a Vim |
4bdc07beeadb
patch 8.2.0997: cannot execute a register containing line continuation
Bram Moolenaar <Bram@vim.org>
parents:
20552
diff
changeset
|
170 script. |
16610 | 171 Future: Will execute the register for each line in the |
172 address range. | |
7 | 173 |
174 *:@:* | |
175 :[addr]@: Repeat last command-line. First set cursor at line | |
16553
0e473e9e70c2
patch 8.1.1280: remarks about functionality not in Vi clutters the help
Bram Moolenaar <Bram@vim.org>
parents:
16267
diff
changeset
|
176 [addr] (default is current line). |
7 | 177 |
10186
a5ef9968638c
commit https://github.com/vim/vim/commit/7e1479b86c590a66b63a274c079b7f18907d45a4
Christian Brabandt <cb@256bit.org>
parents:
9644
diff
changeset
|
178 :[addr]@ *:@@* |
20241 | 179 :[addr]@@ Repeat the previous :@{register}. First set cursor at |
16553
0e473e9e70c2
patch 8.1.1280: remarks about functionality not in Vi clutters the help
Bram Moolenaar <Bram@vim.org>
parents:
16267
diff
changeset
|
180 line [addr] (default is current line). |
7 | 181 |
182 ============================================================================== | |
183 4. Using Vim scripts *using-scripts* | |
184 | |
185 For writing a Vim script, see chapter 41 of the user manual |usr_41.txt|. | |
186 | |
187 *:so* *:source* *load-vim-script* | |
188 :so[urce] {file} Read Ex commands from {file}. These are commands that | |
189 start with a ":". | |
716 | 190 Triggers the |SourcePre| autocommand. |
16808 | 191 *:source!* |
7 | 192 :so[urce]! {file} Read Vim commands from {file}. These are commands |
193 that are executed from Normal mode, like you type | |
194 them. | |
195 When used after |:global|, |:argdo|, |:windo|, | |
196 |:bufdo|, in a loop or when another command follows | |
197 the display won't be updated while executing the | |
198 commands. | |
16808 | 199 Cannot be used in the |sandbox|. |
7 | 200 |
201 *:ru* *:runtime* | |
8526
981cc3bef9f3
commit https://github.com/vim/vim/commit/8dcf259d904cfb965d31841dc74a5cfaf5a351d9
Christian Brabandt <cb@256bit.org>
parents:
8475
diff
changeset
|
202 :ru[ntime][!] [where] {file} .. |
7 | 203 Read Ex commands from {file} in each directory given |
8526
981cc3bef9f3
commit https://github.com/vim/vim/commit/8dcf259d904cfb965d31841dc74a5cfaf5a351d9
Christian Brabandt <cb@256bit.org>
parents:
8475
diff
changeset
|
204 by 'runtimepath' and/or 'packpath'. There is no error |
981cc3bef9f3
commit https://github.com/vim/vim/commit/8dcf259d904cfb965d31841dc74a5cfaf5a351d9
Christian Brabandt <cb@256bit.org>
parents:
8475
diff
changeset
|
205 for non-existing files. |
18831 | 206 |
8526
981cc3bef9f3
commit https://github.com/vim/vim/commit/8dcf259d904cfb965d31841dc74a5cfaf5a351d9
Christian Brabandt <cb@256bit.org>
parents:
8475
diff
changeset
|
207 Example: > |
7 | 208 :runtime syntax/c.vim |
209 | |
210 < There can be multiple {file} arguments, separated by | |
211 spaces. Each {file} is searched for in the first | |
212 directory from 'runtimepath', then in the second | |
213 directory, etc. Use a backslash to include a space | |
214 inside {file} (although it's better not to use spaces | |
215 in file names, it causes trouble). | |
216 | |
217 When [!] is included, all found files are sourced. | |
218 When it is not included only the first found file is | |
219 sourced. | |
220 | |
8526
981cc3bef9f3
commit https://github.com/vim/vim/commit/8dcf259d904cfb965d31841dc74a5cfaf5a351d9
Christian Brabandt <cb@256bit.org>
parents:
8475
diff
changeset
|
221 When [where] is omitted only 'runtimepath' is used. |
981cc3bef9f3
commit https://github.com/vim/vim/commit/8dcf259d904cfb965d31841dc74a5cfaf5a351d9
Christian Brabandt <cb@256bit.org>
parents:
8475
diff
changeset
|
222 Other values: |
981cc3bef9f3
commit https://github.com/vim/vim/commit/8dcf259d904cfb965d31841dc74a5cfaf5a351d9
Christian Brabandt <cb@256bit.org>
parents:
8475
diff
changeset
|
223 START search under "start" in 'packpath' |
981cc3bef9f3
commit https://github.com/vim/vim/commit/8dcf259d904cfb965d31841dc74a5cfaf5a351d9
Christian Brabandt <cb@256bit.org>
parents:
8475
diff
changeset
|
224 OPT search under "opt" in 'packpath' |
981cc3bef9f3
commit https://github.com/vim/vim/commit/8dcf259d904cfb965d31841dc74a5cfaf5a351d9
Christian Brabandt <cb@256bit.org>
parents:
8475
diff
changeset
|
225 PACK search under "start" and "opt" in |
981cc3bef9f3
commit https://github.com/vim/vim/commit/8dcf259d904cfb965d31841dc74a5cfaf5a351d9
Christian Brabandt <cb@256bit.org>
parents:
8475
diff
changeset
|
226 'packpath' |
981cc3bef9f3
commit https://github.com/vim/vim/commit/8dcf259d904cfb965d31841dc74a5cfaf5a351d9
Christian Brabandt <cb@256bit.org>
parents:
8475
diff
changeset
|
227 ALL first use 'runtimepath', then search |
981cc3bef9f3
commit https://github.com/vim/vim/commit/8dcf259d904cfb965d31841dc74a5cfaf5a351d9
Christian Brabandt <cb@256bit.org>
parents:
8475
diff
changeset
|
228 under "start" and "opt" in 'packpath' |
981cc3bef9f3
commit https://github.com/vim/vim/commit/8dcf259d904cfb965d31841dc74a5cfaf5a351d9
Christian Brabandt <cb@256bit.org>
parents:
8475
diff
changeset
|
229 |
7 | 230 When {file} contains wildcards it is expanded to all |
231 matching files. Example: > | |
18130 | 232 :runtime! plugin/**/*.vim |
7 | 233 < This is what Vim uses to load the plugin files when |
237 | 234 starting up. This similar command: > |
18130 | 235 :runtime plugin/**/*.vim |
7 | 236 < would source the first file only. |
237 | |
238 When 'verbose' is one or higher, there is a message | |
239 when no file could be found. | |
240 When 'verbose' is two or higher, there is a message | |
241 about each searched file. | |
242 | |
8416
1a6527cce675
commit https://github.com/vim/vim/commit/be82c254862e475a582c0717455e1db6bf96b0d0
Christian Brabandt <cb@256bit.org>
parents:
8392
diff
changeset
|
243 *:pa* *:packadd* *E919* |
8392
1bf1b88968a2
commit https://github.com/vim/vim/commit/328da0dcb7be34b594725eef6dc98d3ea6516d69
Christian Brabandt <cb@256bit.org>
parents:
8388
diff
changeset
|
244 :pa[ckadd][!] {name} Search for an optional plugin directory in 'packpath' |
1bf1b88968a2
commit https://github.com/vim/vim/commit/328da0dcb7be34b594725eef6dc98d3ea6516d69
Christian Brabandt <cb@256bit.org>
parents:
8388
diff
changeset
|
245 and source any plugin files found. The directory must |
1bf1b88968a2
commit https://github.com/vim/vim/commit/328da0dcb7be34b594725eef6dc98d3ea6516d69
Christian Brabandt <cb@256bit.org>
parents:
8388
diff
changeset
|
246 match: |
1bf1b88968a2
commit https://github.com/vim/vim/commit/328da0dcb7be34b594725eef6dc98d3ea6516d69
Christian Brabandt <cb@256bit.org>
parents:
8388
diff
changeset
|
247 pack/*/opt/{name} ~ |
1bf1b88968a2
commit https://github.com/vim/vim/commit/328da0dcb7be34b594725eef6dc98d3ea6516d69
Christian Brabandt <cb@256bit.org>
parents:
8388
diff
changeset
|
248 The directory is added to 'runtimepath' if it wasn't |
1bf1b88968a2
commit https://github.com/vim/vim/commit/328da0dcb7be34b594725eef6dc98d3ea6516d69
Christian Brabandt <cb@256bit.org>
parents:
8388
diff
changeset
|
249 there yet. |
9116
bc38030aec7d
commit https://github.com/vim/vim/commit/26852128a2b713ef49341a0c18daba928444e7eb
Christian Brabandt <cb@256bit.org>
parents:
8876
diff
changeset
|
250 If the directory pack/*/opt/{name}/after exists it is |
bc38030aec7d
commit https://github.com/vim/vim/commit/26852128a2b713ef49341a0c18daba928444e7eb
Christian Brabandt <cb@256bit.org>
parents:
8876
diff
changeset
|
251 added at the end of 'runtimepath'. |
8303
88207f4b861a
commit https://github.com/vim/vim/commit/dae8d21dd291df6a6679a00be64e18bca0156576
Christian Brabandt <cb@256bit.org>
parents:
8246
diff
changeset
|
252 |
13051 | 253 If loading packages from "pack/*/start" was skipped, |
254 then this directory is searched first: | |
255 pack/*/start/{name} ~ | |
256 | |
8182
95d59081580f
commit https://github.com/vim/vim/commit/f6fee0e2d4341c0c2f5339c1268e5877fafd07cf
Christian Brabandt <cb@256bit.org>
parents:
8061
diff
changeset
|
257 Note that {name} is the directory name, not the name |
8876
47f17f66da3d
commit https://github.com/vim/vim/commit/03413f44167c4b5cd0012def9bb331e2518c83cf
Christian Brabandt <cb@256bit.org>
parents:
8795
diff
changeset
|
258 of the .vim file. All the files matching the pattern |
47f17f66da3d
commit https://github.com/vim/vim/commit/03413f44167c4b5cd0012def9bb331e2518c83cf
Christian Brabandt <cb@256bit.org>
parents:
8795
diff
changeset
|
259 pack/*/opt/{name}/plugin/**/*.vim ~ |
47f17f66da3d
commit https://github.com/vim/vim/commit/03413f44167c4b5cd0012def9bb331e2518c83cf
Christian Brabandt <cb@256bit.org>
parents:
8795
diff
changeset
|
260 will be sourced. This allows for using subdirectories |
47f17f66da3d
commit https://github.com/vim/vim/commit/03413f44167c4b5cd0012def9bb331e2518c83cf
Christian Brabandt <cb@256bit.org>
parents:
8795
diff
changeset
|
261 below "plugin", just like with plugins in |
47f17f66da3d
commit https://github.com/vim/vim/commit/03413f44167c4b5cd0012def9bb331e2518c83cf
Christian Brabandt <cb@256bit.org>
parents:
8795
diff
changeset
|
262 'runtimepath'. |
8182
95d59081580f
commit https://github.com/vim/vim/commit/f6fee0e2d4341c0c2f5339c1268e5877fafd07cf
Christian Brabandt <cb@256bit.org>
parents:
8061
diff
changeset
|
263 |
8392
1bf1b88968a2
commit https://github.com/vim/vim/commit/328da0dcb7be34b594725eef6dc98d3ea6516d69
Christian Brabandt <cb@256bit.org>
parents:
8388
diff
changeset
|
264 If the filetype detection was not enabled yet (this |
1bf1b88968a2
commit https://github.com/vim/vim/commit/328da0dcb7be34b594725eef6dc98d3ea6516d69
Christian Brabandt <cb@256bit.org>
parents:
8388
diff
changeset
|
265 is usually done with a "syntax enable" or "filetype |
1bf1b88968a2
commit https://github.com/vim/vim/commit/328da0dcb7be34b594725eef6dc98d3ea6516d69
Christian Brabandt <cb@256bit.org>
parents:
8388
diff
changeset
|
266 on" command in your .vimrc file), this will also look |
1bf1b88968a2
commit https://github.com/vim/vim/commit/328da0dcb7be34b594725eef6dc98d3ea6516d69
Christian Brabandt <cb@256bit.org>
parents:
8388
diff
changeset
|
267 for "{name}/ftdetect/*.vim" files. |
1bf1b88968a2
commit https://github.com/vim/vim/commit/328da0dcb7be34b594725eef6dc98d3ea6516d69
Christian Brabandt <cb@256bit.org>
parents:
8388
diff
changeset
|
268 |
1bf1b88968a2
commit https://github.com/vim/vim/commit/328da0dcb7be34b594725eef6dc98d3ea6516d69
Christian Brabandt <cb@256bit.org>
parents:
8388
diff
changeset
|
269 When the optional ! is added no plugin files or |
1bf1b88968a2
commit https://github.com/vim/vim/commit/328da0dcb7be34b594725eef6dc98d3ea6516d69
Christian Brabandt <cb@256bit.org>
parents:
8388
diff
changeset
|
270 ftdetect scripts are loaded, only the matching |
1bf1b88968a2
commit https://github.com/vim/vim/commit/328da0dcb7be34b594725eef6dc98d3ea6516d69
Christian Brabandt <cb@256bit.org>
parents:
8388
diff
changeset
|
271 directories are added to 'runtimepath'. This is |
1bf1b88968a2
commit https://github.com/vim/vim/commit/328da0dcb7be34b594725eef6dc98d3ea6516d69
Christian Brabandt <cb@256bit.org>
parents:
8388
diff
changeset
|
272 useful in your .vimrc. The plugins will then be |
1bf1b88968a2
commit https://github.com/vim/vim/commit/328da0dcb7be34b594725eef6dc98d3ea6516d69
Christian Brabandt <cb@256bit.org>
parents:
8388
diff
changeset
|
273 loaded during initialization, see |load-plugins|. |
1bf1b88968a2
commit https://github.com/vim/vim/commit/328da0dcb7be34b594725eef6dc98d3ea6516d69
Christian Brabandt <cb@256bit.org>
parents:
8388
diff
changeset
|
274 |
1bf1b88968a2
commit https://github.com/vim/vim/commit/328da0dcb7be34b594725eef6dc98d3ea6516d69
Christian Brabandt <cb@256bit.org>
parents:
8388
diff
changeset
|
275 Also see |pack-add|. |
14249
4543777545a3
Updated runtime and language files.
Christian Brabandt <cb@256bit.org>
parents:
13963
diff
changeset
|
276 {only available when compiled with |+eval|} |
8392
1bf1b88968a2
commit https://github.com/vim/vim/commit/328da0dcb7be34b594725eef6dc98d3ea6516d69
Christian Brabandt <cb@256bit.org>
parents:
8388
diff
changeset
|
277 |
8673
ed7251c3e2d3
commit https://github.com/vim/vim/commit/e18c0b39815c5a746887a509c2cd9f11fadaba07
Christian Brabandt <cb@256bit.org>
parents:
8526
diff
changeset
|
278 *:packl* *:packloadall* |
8876
47f17f66da3d
commit https://github.com/vim/vim/commit/03413f44167c4b5cd0012def9bb331e2518c83cf
Christian Brabandt <cb@256bit.org>
parents:
8795
diff
changeset
|
279 :packl[oadall][!] Load all packages in the "start" directory under each |
47f17f66da3d
commit https://github.com/vim/vim/commit/03413f44167c4b5cd0012def9bb331e2518c83cf
Christian Brabandt <cb@256bit.org>
parents:
8795
diff
changeset
|
280 entry in 'packpath'. |
18831 | 281 |
8876
47f17f66da3d
commit https://github.com/vim/vim/commit/03413f44167c4b5cd0012def9bb331e2518c83cf
Christian Brabandt <cb@256bit.org>
parents:
8795
diff
changeset
|
282 First all the directories found are added to |
47f17f66da3d
commit https://github.com/vim/vim/commit/03413f44167c4b5cd0012def9bb331e2518c83cf
Christian Brabandt <cb@256bit.org>
parents:
8795
diff
changeset
|
283 'runtimepath', then the plugins found in the |
47f17f66da3d
commit https://github.com/vim/vim/commit/03413f44167c4b5cd0012def9bb331e2518c83cf
Christian Brabandt <cb@256bit.org>
parents:
8795
diff
changeset
|
284 directories are sourced. This allows for a plugin to |
47f17f66da3d
commit https://github.com/vim/vim/commit/03413f44167c4b5cd0012def9bb331e2518c83cf
Christian Brabandt <cb@256bit.org>
parents:
8795
diff
changeset
|
285 depend on something of another plugin, e.g. an |
47f17f66da3d
commit https://github.com/vim/vim/commit/03413f44167c4b5cd0012def9bb331e2518c83cf
Christian Brabandt <cb@256bit.org>
parents:
8795
diff
changeset
|
286 "autoload" directory. See |packload-two-steps| for |
47f17f66da3d
commit https://github.com/vim/vim/commit/03413f44167c4b5cd0012def9bb331e2518c83cf
Christian Brabandt <cb@256bit.org>
parents:
8795
diff
changeset
|
287 how this can be useful. |
47f17f66da3d
commit https://github.com/vim/vim/commit/03413f44167c4b5cd0012def9bb331e2518c83cf
Christian Brabandt <cb@256bit.org>
parents:
8795
diff
changeset
|
288 |
8673
ed7251c3e2d3
commit https://github.com/vim/vim/commit/e18c0b39815c5a746887a509c2cd9f11fadaba07
Christian Brabandt <cb@256bit.org>
parents:
8526
diff
changeset
|
289 This is normally done automatically during startup, |
ed7251c3e2d3
commit https://github.com/vim/vim/commit/e18c0b39815c5a746887a509c2cd9f11fadaba07
Christian Brabandt <cb@256bit.org>
parents:
8526
diff
changeset
|
290 after loading your .vimrc file. With this command it |
ed7251c3e2d3
commit https://github.com/vim/vim/commit/e18c0b39815c5a746887a509c2cd9f11fadaba07
Christian Brabandt <cb@256bit.org>
parents:
8526
diff
changeset
|
291 can be done earlier. |
8876
47f17f66da3d
commit https://github.com/vim/vim/commit/03413f44167c4b5cd0012def9bb331e2518c83cf
Christian Brabandt <cb@256bit.org>
parents:
8795
diff
changeset
|
292 |
17161 | 293 Packages will be loaded only once. Using |
294 `:packloadall` a second time will have no effect. | |
295 When the optional ! is added this command will load | |
296 packages even when done before. | |
297 | |
298 Note that when using `:packloadall` in the |vimrc| | |
299 file, the 'runtimepath' option is updated, and later | |
300 all plugins in 'runtimepath' will be loaded, which | |
301 means they are loaded again. Plugins are expected to | |
302 handle that. | |
8876
47f17f66da3d
commit https://github.com/vim/vim/commit/03413f44167c4b5cd0012def9bb331e2518c83cf
Christian Brabandt <cb@256bit.org>
parents:
8795
diff
changeset
|
303 |
8795
aba2d0a01290
commit https://github.com/vim/vim/commit/7db8f6f4f85e5d0526d23107b2a5e2334dc23354
Christian Brabandt <cb@256bit.org>
parents:
8748
diff
changeset
|
304 An error only causes sourcing the script where it |
8673
ed7251c3e2d3
commit https://github.com/vim/vim/commit/e18c0b39815c5a746887a509c2cd9f11fadaba07
Christian Brabandt <cb@256bit.org>
parents:
8526
diff
changeset
|
305 happens to be aborted, further plugins will be loaded. |
8526
981cc3bef9f3
commit https://github.com/vim/vim/commit/8dcf259d904cfb965d31841dc74a5cfaf5a351d9
Christian Brabandt <cb@256bit.org>
parents:
8475
diff
changeset
|
306 See |packages|. |
14249
4543777545a3
Updated runtime and language files.
Christian Brabandt <cb@256bit.org>
parents:
13963
diff
changeset
|
307 {only available when compiled with |+eval|} |
8182
95d59081580f
commit https://github.com/vim/vim/commit/f6fee0e2d4341c0c2f5339c1268e5877fafd07cf
Christian Brabandt <cb@256bit.org>
parents:
8061
diff
changeset
|
308 |
7 | 309 :scripte[ncoding] [encoding] *:scripte* *:scriptencoding* *E167* |
310 Specify the character encoding used in the script. | |
311 The following lines will be converted from [encoding] | |
312 to the value of the 'encoding' option, if they are | |
313 different. Examples: > | |
314 scriptencoding iso-8859-5 | |
315 scriptencoding cp932 | |
316 < | |
317 When [encoding] is empty, no conversion is done. This | |
318 can be used to restrict conversion to a sequence of | |
319 lines: > | |
320 scriptencoding euc-jp | |
321 ... lines to be converted ... | |
322 scriptencoding | |
323 ... not converted ... | |
324 | |
325 < When conversion isn't supported by the system, there | |
9644
9f7bcc2c3b97
commit https://github.com/vim/vim/commit/6f1d9a096bf22d50c727dca73abbfb8e3ff55176
Christian Brabandt <cb@256bit.org>
parents:
9286
diff
changeset
|
326 is no error message and no conversion is done. When a |
9f7bcc2c3b97
commit https://github.com/vim/vim/commit/6f1d9a096bf22d50c727dca73abbfb8e3ff55176
Christian Brabandt <cb@256bit.org>
parents:
9286
diff
changeset
|
327 line can't be converted there is no error and the |
9f7bcc2c3b97
commit https://github.com/vim/vim/commit/6f1d9a096bf22d50c727dca73abbfb8e3ff55176
Christian Brabandt <cb@256bit.org>
parents:
9286
diff
changeset
|
328 original line is kept. |
7 | 329 |
330 Don't use "ucs-2" or "ucs-4", scripts cannot be in | |
331 these encodings (they would contain NUL bytes). | |
332 When a sourced script starts with a BOM (Byte Order | |
2207
b17bbfa96fa0
Add the settabvar() and gettabvar() functions.
Bram Moolenaar <bram@vim.org>
parents:
2154
diff
changeset
|
333 Mark) in utf-8 format Vim will recognize it, no need |
7 | 334 to use ":scriptencoding utf-8" then. |
335 | |
10895
c391bfbdb452
Updated runtime files.
Christian Brabandt <cb@256bit.org>
parents:
10198
diff
changeset
|
336 If you set the 'encoding' option in your |.vimrc|, |
c391bfbdb452
Updated runtime files.
Christian Brabandt <cb@256bit.org>
parents:
10198
diff
changeset
|
337 `:scriptencoding` must be placed after that. E.g.: > |
c391bfbdb452
Updated runtime files.
Christian Brabandt <cb@256bit.org>
parents:
10198
diff
changeset
|
338 set encoding=utf-8 |
c391bfbdb452
Updated runtime files.
Christian Brabandt <cb@256bit.org>
parents:
10198
diff
changeset
|
339 scriptencoding utf-8 |
c391bfbdb452
Updated runtime files.
Christian Brabandt <cb@256bit.org>
parents:
10198
diff
changeset
|
340 < |
7 | 341 |
16223
abb67309c1ca
patch 8.1.1116: cannot enforce a Vim script style
Bram Moolenaar <Bram@vim.org>
parents:
15878
diff
changeset
|
342 :scriptv[ersion] {version} *:scriptv* *:scriptversion* |
abb67309c1ca
patch 8.1.1116: cannot enforce a Vim script style
Bram Moolenaar <Bram@vim.org>
parents:
15878
diff
changeset
|
343 *E999* *E984* |
16267 | 344 Specify the version of Vim for the lines that follow |
345 in the same file. Only applies at the toplevel of | |
346 sourced scripts, not inside functions. | |
16223
abb67309c1ca
patch 8.1.1116: cannot enforce a Vim script style
Bram Moolenaar <Bram@vim.org>
parents:
15878
diff
changeset
|
347 |
abb67309c1ca
patch 8.1.1116: cannot enforce a Vim script style
Bram Moolenaar <Bram@vim.org>
parents:
15878
diff
changeset
|
348 If {version} is higher than what the current Vim |
abb67309c1ca
patch 8.1.1116: cannot enforce a Vim script style
Bram Moolenaar <Bram@vim.org>
parents:
15878
diff
changeset
|
349 version supports E999 will be given. You either need |
abb67309c1ca
patch 8.1.1116: cannot enforce a Vim script style
Bram Moolenaar <Bram@vim.org>
parents:
15878
diff
changeset
|
350 to rewrite the script to make it work with an older |
abb67309c1ca
patch 8.1.1116: cannot enforce a Vim script style
Bram Moolenaar <Bram@vim.org>
parents:
15878
diff
changeset
|
351 Vim version, or update Vim to a newer version. See |
abb67309c1ca
patch 8.1.1116: cannot enforce a Vim script style
Bram Moolenaar <Bram@vim.org>
parents:
15878
diff
changeset
|
352 |vimscript-version| for what changed between versions. |
abb67309c1ca
patch 8.1.1116: cannot enforce a Vim script style
Bram Moolenaar <Bram@vim.org>
parents:
15878
diff
changeset
|
353 |
6476 | 354 *:scr* *:scriptnames* |
355 :scr[iptnames] List all sourced script names, in the order they were | |
7 | 356 first sourced. The number is used for the script ID |
357 |<SID>|. | |
16553
0e473e9e70c2
patch 8.1.1280: remarks about functionality not in Vi clutters the help
Bram Moolenaar <Bram@vim.org>
parents:
16267
diff
changeset
|
358 {not available when compiled without the |+eval| |
0e473e9e70c2
patch 8.1.1280: remarks about functionality not in Vi clutters the help
Bram Moolenaar <Bram@vim.org>
parents:
16267
diff
changeset
|
359 feature} |
7 | 360 |
15085
1783c0b6bc2e
patch 8.1.0553: it is not easy to edit a script that was sourced
Bram Moolenaar <Bram@vim.org>
parents:
14864
diff
changeset
|
361 :scr[iptnames][!] {scriptId} *:script* |
15194 | 362 Edit script {scriptId}. Although ":scriptnames name" |
363 works, using ":script name" is recommended. | |
364 When the current buffer can't be |abandon|ed and the ! | |
365 is not present, the command fails. | |
15085
1783c0b6bc2e
patch 8.1.0553: it is not easy to edit a script that was sourced
Bram Moolenaar <Bram@vim.org>
parents:
14864
diff
changeset
|
366 |
7 | 367 *:fini* *:finish* *E168* |
368 :fini[sh] Stop sourcing a script. Can only be used in a Vim | |
369 script file. This is a quick way to skip the rest of | |
370 the file. If it is used after a |:try| but before the | |
371 matching |:finally| (if present), the commands | |
372 following the ":finally" up to the matching |:endtry| | |
373 are executed first. This process applies to all | |
374 nested ":try"s in the script. The outermost ":endtry" | |
16553
0e473e9e70c2
patch 8.1.1280: remarks about functionality not in Vi clutters the help
Bram Moolenaar <Bram@vim.org>
parents:
16267
diff
changeset
|
375 then stops sourcing the script. |
7 | 376 |
377 All commands and command sequences can be repeated by putting them in a named | |
378 register and then executing it. There are two ways to get the commands in the | |
379 register: | |
380 - Use the record command "q". You type the commands once, and while they are | |
381 being executed they are stored in a register. Easy, because you can see | |
382 what you are doing. If you make a mistake, "p"ut the register into the | |
383 file, edit the command sequence, and then delete it into the register | |
384 again. You can continue recording by appending to the register (use an | |
385 uppercase letter). | |
386 - Delete or yank the command sequence into the register. | |
387 | |
388 Often used command sequences can be put under a function key with the ':map' | |
389 command. | |
390 | |
391 An alternative is to put the commands in a file, and execute them with the | |
392 ':source!' command. Useful for long command sequences. Can be combined with | |
393 the ':map' command to put complicated commands under a function key. | |
394 | |
395 The ':source' command reads Ex commands from a file line by line. You will | |
396 have to type any needed keyboard input. The ':source!' command reads from a | |
397 script file character by character, interpreting each character as if you | |
398 typed it. | |
399 | |
400 Example: When you give the ":!ls" command you get the |hit-enter| prompt. If | |
401 you ':source' a file with the line "!ls" in it, you will have to type the | |
402 <Enter> yourself. But if you ':source!' a file with the line ":!ls" in it, | |
403 the next characters from that file are read until a <CR> is found. You will | |
404 not have to type <CR> yourself, unless ":!ls" was the last line in the file. | |
405 | |
406 It is possible to put ':source[!]' commands in the script file, so you can | |
407 make a top-down hierarchy of script files. The ':source' command can be | |
408 nested as deep as the number of files that can be opened at one time (about | |
409 15). The ':source!' command can be nested up to 15 levels deep. | |
410 | |
411 You can use the "<sfile>" string (literally, this is not a special key) inside | |
412 of the sourced file, in places where a file name is expected. It will be | |
413 replaced by the file name of the sourced file. For example, if you have a | |
414 "other.vimrc" file in the same directory as your ".vimrc" file, you can source | |
415 it from your ".vimrc" file with this command: > | |
416 :source <sfile>:h/other.vimrc | |
417 | |
418 In script files terminal-dependent key codes are represented by | |
419 terminal-independent two character codes. This means that they can be used | |
420 in the same way on different kinds of terminals. The first character of a | |
421 key code is 0x80 or 128, shown on the screen as "~@". The second one can be | |
422 found in the list |key-notation|. Any of these codes can also be entered | |
423 with CTRL-V followed by the three digit decimal code. This does NOT work for | |
424 the <t_xx> termcap codes, these can only be used in mappings. | |
425 | |
426 *:source_crnl* *W15* | |
18912
ccd16426a1f9
patch 8.2.0017: OS/2 and MS-DOS are still mentioned
Bram Moolenaar <Bram@vim.org>
parents:
18879
diff
changeset
|
427 Win32: Files that are read with ":source" normally have <CR><NL> <EOL>s. |
ccd16426a1f9
patch 8.2.0017: OS/2 and MS-DOS are still mentioned
Bram Moolenaar <Bram@vim.org>
parents:
18879
diff
changeset
|
428 These always work. If you are using a file with <NL> <EOL>s (for example, a |
ccd16426a1f9
patch 8.2.0017: OS/2 and MS-DOS are still mentioned
Bram Moolenaar <Bram@vim.org>
parents:
18879
diff
changeset
|
429 file made on Unix), this will be recognized if 'fileformats' is not empty and |
ccd16426a1f9
patch 8.2.0017: OS/2 and MS-DOS are still mentioned
Bram Moolenaar <Bram@vim.org>
parents:
18879
diff
changeset
|
430 the first line does not end in a <CR>. This fails if the first line has |
ccd16426a1f9
patch 8.2.0017: OS/2 and MS-DOS are still mentioned
Bram Moolenaar <Bram@vim.org>
parents:
18879
diff
changeset
|
431 something like ":map <F1> :help^M", where "^M" is a <CR>. If the first line |
ccd16426a1f9
patch 8.2.0017: OS/2 and MS-DOS are still mentioned
Bram Moolenaar <Bram@vim.org>
parents:
18879
diff
changeset
|
432 ends in a <CR>, but following ones don't, you will get an error message, |
ccd16426a1f9
patch 8.2.0017: OS/2 and MS-DOS are still mentioned
Bram Moolenaar <Bram@vim.org>
parents:
18879
diff
changeset
|
433 because the <CR> from the first lines will be lost. |
7 | 434 |
333 | 435 Mac Classic: Files that are read with ":source" normally have <CR> <EOL>s. |
7 | 436 These always work. If you are using a file with <NL> <EOL>s (for example, a |
437 file made on Unix), this will be recognized if 'fileformats' is not empty and | |
438 the first line does not end in a <CR>. Be careful not to use a file with <NL> | |
439 linebreaks which has a <CR> in first line. | |
440 | |
441 On other systems, Vim expects ":source"ed files to end in a <NL>. These | |
442 always work. If you are using a file with <CR><NL> <EOL>s (for example, a | |
18972 | 443 file made on MS-Windows), all lines will have a trailing <CR>. This may cause |
7 | 444 problems for some commands (e.g., mappings). There is no automatic <EOL> |
445 detection, because it's common to start with a line that defines a mapping | |
446 that ends in a <CR>, which will confuse the automaton. | |
447 | |
448 *line-continuation* | |
449 Long lines in a ":source"d Ex command script file can be split by inserting | |
450 a line continuation symbol "\" (backslash) at the start of the next line. | |
451 There can be white space before the backslash, which is ignored. | |
452 | |
453 Example: the lines > | |
454 :set comments=sr:/*,mb:*,el:*/, | |
455 \://, | |
456 \b:#, | |
457 \:%, | |
458 \n:>, | |
459 \fb:- | |
460 are interpreted as if they were given in one line: | |
461 :set comments=sr:/*,mb:*,el:*/,://,b:#,:%,n:>,fb:- | |
462 | |
463 All leading whitespace characters in the line before a backslash are ignored. | |
464 Note however that trailing whitespace in the line before it cannot be | |
465 inserted freely; it depends on the position where a command is split up | |
466 whether additional whitespace is allowed or not. | |
467 | |
2033
de5a43c5eedc
Update documentation files.
Bram Moolenaar <bram@zimbu.org>
parents:
1702
diff
changeset
|
468 When a space is required it's best to put it right after the backslash. A |
de5a43c5eedc
Update documentation files.
Bram Moolenaar <bram@zimbu.org>
parents:
1702
diff
changeset
|
469 space at the end of a line is hard to see and may be accidentally deleted. > |
de5a43c5eedc
Update documentation files.
Bram Moolenaar <bram@zimbu.org>
parents:
1702
diff
changeset
|
470 :syn match Comment |
de5a43c5eedc
Update documentation files.
Bram Moolenaar <bram@zimbu.org>
parents:
1702
diff
changeset
|
471 \ "very long regexp" |
de5a43c5eedc
Update documentation files.
Bram Moolenaar <bram@zimbu.org>
parents:
1702
diff
changeset
|
472 \ keepend |
de5a43c5eedc
Update documentation files.
Bram Moolenaar <bram@zimbu.org>
parents:
1702
diff
changeset
|
473 |
7 | 474 There is a problem with the ":append" and ":insert" commands: > |
475 :1append | |
476 \asdf | |
477 . | |
478 The backslash is seen as a line-continuation symbol, thus this results in the | |
479 command: > | |
480 :1appendasdf | |
481 . | |
482 To avoid this, add the 'C' flag to the 'cpoptions' option: > | |
483 :set cpo+=C | |
484 :1append | |
485 \asdf | |
486 . | |
487 :set cpo-=C | |
488 | |
489 Note that when the commands are inside a function, you need to add the 'C' | |
490 flag when defining the function, it is not relevant when executing it. > | |
491 :set cpo+=C | |
492 :function Foo() | |
493 :1append | |
494 \asdf | |
495 . | |
496 :endfunction | |
497 :set cpo-=C | |
14714
bdbb049c2aa8
patch 8.1.0369: continuation lines cannot contain comments
Christian Brabandt <cb@256bit.org>
parents:
14421
diff
changeset
|
498 < |
bdbb049c2aa8
patch 8.1.0369: continuation lines cannot contain comments
Christian Brabandt <cb@256bit.org>
parents:
14421
diff
changeset
|
499 *line-continuation-comment* |
14864 | 500 To add a comment in between the lines start with '"\ '. Notice the space |
501 after the backslash. Example: > | |
14714
bdbb049c2aa8
patch 8.1.0369: continuation lines cannot contain comments
Christian Brabandt <cb@256bit.org>
parents:
14421
diff
changeset
|
502 let array = [ |
bdbb049c2aa8
patch 8.1.0369: continuation lines cannot contain comments
Christian Brabandt <cb@256bit.org>
parents:
14421
diff
changeset
|
503 "\ first entry comment |
bdbb049c2aa8
patch 8.1.0369: continuation lines cannot contain comments
Christian Brabandt <cb@256bit.org>
parents:
14421
diff
changeset
|
504 \ 'first', |
bdbb049c2aa8
patch 8.1.0369: continuation lines cannot contain comments
Christian Brabandt <cb@256bit.org>
parents:
14421
diff
changeset
|
505 "\ second entry comment |
bdbb049c2aa8
patch 8.1.0369: continuation lines cannot contain comments
Christian Brabandt <cb@256bit.org>
parents:
14421
diff
changeset
|
506 \ 'second', |
bdbb049c2aa8
patch 8.1.0369: continuation lines cannot contain comments
Christian Brabandt <cb@256bit.org>
parents:
14421
diff
changeset
|
507 \ ] |
7 | 508 |
509 Rationale: | |
510 Most programs work with a trailing backslash to indicate line | |
511 continuation. Using this in Vim would cause incompatibility with Vi. | |
512 For example for this Vi mapping: > | |
513 :map xx asdf\ | |
514 < Therefore the unusual leading backslash is used. | |
515 | |
14714
bdbb049c2aa8
patch 8.1.0369: continuation lines cannot contain comments
Christian Brabandt <cb@256bit.org>
parents:
14421
diff
changeset
|
516 Starting a comment in a continuation line results in all following |
bdbb049c2aa8
patch 8.1.0369: continuation lines cannot contain comments
Christian Brabandt <cb@256bit.org>
parents:
14421
diff
changeset
|
517 continuation lines to be part of the comment. Since it was like this |
bdbb049c2aa8
patch 8.1.0369: continuation lines cannot contain comments
Christian Brabandt <cb@256bit.org>
parents:
14421
diff
changeset
|
518 for a long time, when making it possible to add a comment halfway a |
bdbb049c2aa8
patch 8.1.0369: continuation lines cannot contain comments
Christian Brabandt <cb@256bit.org>
parents:
14421
diff
changeset
|
519 sequence of continuation lines, it was not possible to use \", since |
bdbb049c2aa8
patch 8.1.0369: continuation lines cannot contain comments
Christian Brabandt <cb@256bit.org>
parents:
14421
diff
changeset
|
520 that was a valid continuation line. Using '"\ ' comes closest, even |
bdbb049c2aa8
patch 8.1.0369: continuation lines cannot contain comments
Christian Brabandt <cb@256bit.org>
parents:
14421
diff
changeset
|
521 though it may look a bit weird. Requiring the space after the |
bdbb049c2aa8
patch 8.1.0369: continuation lines cannot contain comments
Christian Brabandt <cb@256bit.org>
parents:
14421
diff
changeset
|
522 backslash is to make it very unlikely this is a normal comment line. |
bdbb049c2aa8
patch 8.1.0369: continuation lines cannot contain comments
Christian Brabandt <cb@256bit.org>
parents:
14421
diff
changeset
|
523 |
7 | 524 ============================================================================== |
8182
95d59081580f
commit https://github.com/vim/vim/commit/f6fee0e2d4341c0c2f5339c1268e5877fafd07cf
Christian Brabandt <cb@256bit.org>
parents:
8061
diff
changeset
|
525 5. Using Vim packages *packages* |
95d59081580f
commit https://github.com/vim/vim/commit/f6fee0e2d4341c0c2f5339c1268e5877fafd07cf
Christian Brabandt <cb@256bit.org>
parents:
8061
diff
changeset
|
526 |
95d59081580f
commit https://github.com/vim/vim/commit/f6fee0e2d4341c0c2f5339c1268e5877fafd07cf
Christian Brabandt <cb@256bit.org>
parents:
8061
diff
changeset
|
527 A Vim package is a directory that contains one or more plugins. The |
95d59081580f
commit https://github.com/vim/vim/commit/f6fee0e2d4341c0c2f5339c1268e5877fafd07cf
Christian Brabandt <cb@256bit.org>
parents:
8061
diff
changeset
|
528 advantages over normal plugins: |
95d59081580f
commit https://github.com/vim/vim/commit/f6fee0e2d4341c0c2f5339c1268e5877fafd07cf
Christian Brabandt <cb@256bit.org>
parents:
8061
diff
changeset
|
529 - A package can be downloaded as an archive and unpacked in its own directory. |
8440
4c6ad81d41fe
commit https://github.com/vim/vim/commit/5f148ec0b5a6cedd9129b3abac351034b83cc4f7
Christian Brabandt <cb@256bit.org>
parents:
8416
diff
changeset
|
530 Thus the files are not mixed with files of other plugins. That makes it |
4c6ad81d41fe
commit https://github.com/vim/vim/commit/5f148ec0b5a6cedd9129b3abac351034b83cc4f7
Christian Brabandt <cb@256bit.org>
parents:
8416
diff
changeset
|
531 easy to update and remove. |
8376
e448f2a5d45b
commit https://github.com/vim/vim/commit/91715873d19a1859c08eeded7848113596e2f2bd
Christian Brabandt <cb@256bit.org>
parents:
8303
diff
changeset
|
532 - A package can be a git, mercurial, etc. repository. That makes it really |
8182
95d59081580f
commit https://github.com/vim/vim/commit/f6fee0e2d4341c0c2f5339c1268e5877fafd07cf
Christian Brabandt <cb@256bit.org>
parents:
8061
diff
changeset
|
533 easy to update. |
95d59081580f
commit https://github.com/vim/vim/commit/f6fee0e2d4341c0c2f5339c1268e5877fafd07cf
Christian Brabandt <cb@256bit.org>
parents:
8061
diff
changeset
|
534 - A package can contain multiple plugins that depend on each other. |
95d59081580f
commit https://github.com/vim/vim/commit/f6fee0e2d4341c0c2f5339c1268e5877fafd07cf
Christian Brabandt <cb@256bit.org>
parents:
8061
diff
changeset
|
535 - A package can contain plugins that are automatically loaded on startup and |
8440
4c6ad81d41fe
commit https://github.com/vim/vim/commit/5f148ec0b5a6cedd9129b3abac351034b83cc4f7
Christian Brabandt <cb@256bit.org>
parents:
8416
diff
changeset
|
536 ones that are only loaded when needed with `:packadd`. |
4c6ad81d41fe
commit https://github.com/vim/vim/commit/5f148ec0b5a6cedd9129b3abac351034b83cc4f7
Christian Brabandt <cb@256bit.org>
parents:
8416
diff
changeset
|
537 |
4c6ad81d41fe
commit https://github.com/vim/vim/commit/5f148ec0b5a6cedd9129b3abac351034b83cc4f7
Christian Brabandt <cb@256bit.org>
parents:
8416
diff
changeset
|
538 |
4c6ad81d41fe
commit https://github.com/vim/vim/commit/5f148ec0b5a6cedd9129b3abac351034b83cc4f7
Christian Brabandt <cb@256bit.org>
parents:
8416
diff
changeset
|
539 Using a package and loading automatically ~ |
8182
95d59081580f
commit https://github.com/vim/vim/commit/f6fee0e2d4341c0c2f5339c1268e5877fafd07cf
Christian Brabandt <cb@256bit.org>
parents:
8061
diff
changeset
|
540 |
95d59081580f
commit https://github.com/vim/vim/commit/f6fee0e2d4341c0c2f5339c1268e5877fafd07cf
Christian Brabandt <cb@256bit.org>
parents:
8061
diff
changeset
|
541 Let's assume your Vim files are in the "~/.vim" directory and you want to add a |
8440
4c6ad81d41fe
commit https://github.com/vim/vim/commit/5f148ec0b5a6cedd9129b3abac351034b83cc4f7
Christian Brabandt <cb@256bit.org>
parents:
8416
diff
changeset
|
542 package from a zip archive "/tmp/foopack.zip": |
4c6ad81d41fe
commit https://github.com/vim/vim/commit/5f148ec0b5a6cedd9129b3abac351034b83cc4f7
Christian Brabandt <cb@256bit.org>
parents:
8416
diff
changeset
|
543 % mkdir -p ~/.vim/pack/foo |
4c6ad81d41fe
commit https://github.com/vim/vim/commit/5f148ec0b5a6cedd9129b3abac351034b83cc4f7
Christian Brabandt <cb@256bit.org>
parents:
8416
diff
changeset
|
544 % cd ~/.vim/pack/foo |
4c6ad81d41fe
commit https://github.com/vim/vim/commit/5f148ec0b5a6cedd9129b3abac351034b83cc4f7
Christian Brabandt <cb@256bit.org>
parents:
8416
diff
changeset
|
545 % unzip /tmp/foopack.zip |
8182
95d59081580f
commit https://github.com/vim/vim/commit/f6fee0e2d4341c0c2f5339c1268e5877fafd07cf
Christian Brabandt <cb@256bit.org>
parents:
8061
diff
changeset
|
546 |
8440
4c6ad81d41fe
commit https://github.com/vim/vim/commit/5f148ec0b5a6cedd9129b3abac351034b83cc4f7
Christian Brabandt <cb@256bit.org>
parents:
8416
diff
changeset
|
547 The directory name "foo" is arbitrary, you can pick anything you like. |
8182
95d59081580f
commit https://github.com/vim/vim/commit/f6fee0e2d4341c0c2f5339c1268e5877fafd07cf
Christian Brabandt <cb@256bit.org>
parents:
8061
diff
changeset
|
548 |
95d59081580f
commit https://github.com/vim/vim/commit/f6fee0e2d4341c0c2f5339c1268e5877fafd07cf
Christian Brabandt <cb@256bit.org>
parents:
8061
diff
changeset
|
549 You would now have these files under ~/.vim: |
8440
4c6ad81d41fe
commit https://github.com/vim/vim/commit/5f148ec0b5a6cedd9129b3abac351034b83cc4f7
Christian Brabandt <cb@256bit.org>
parents:
8416
diff
changeset
|
550 pack/foo/README.txt |
8475
aec051e61547
commit https://github.com/vim/vim/commit/af1a0e371e739f8dff337fd31da0ff8ffb347b43
Christian Brabandt <cb@256bit.org>
parents:
8440
diff
changeset
|
551 pack/foo/start/foobar/plugin/foo.vim |
aec051e61547
commit https://github.com/vim/vim/commit/af1a0e371e739f8dff337fd31da0ff8ffb347b43
Christian Brabandt <cb@256bit.org>
parents:
8440
diff
changeset
|
552 pack/foo/start/foobar/syntax/some.vim |
8440
4c6ad81d41fe
commit https://github.com/vim/vim/commit/5f148ec0b5a6cedd9129b3abac351034b83cc4f7
Christian Brabandt <cb@256bit.org>
parents:
8416
diff
changeset
|
553 pack/foo/opt/foodebug/plugin/debugger.vim |
4c6ad81d41fe
commit https://github.com/vim/vim/commit/5f148ec0b5a6cedd9129b3abac351034b83cc4f7
Christian Brabandt <cb@256bit.org>
parents:
8416
diff
changeset
|
554 |
4c6ad81d41fe
commit https://github.com/vim/vim/commit/5f148ec0b5a6cedd9129b3abac351034b83cc4f7
Christian Brabandt <cb@256bit.org>
parents:
8416
diff
changeset
|
555 When Vim starts up, after processing your .vimrc, it scans all directories in |
8876
47f17f66da3d
commit https://github.com/vim/vim/commit/03413f44167c4b5cd0012def9bb331e2518c83cf
Christian Brabandt <cb@256bit.org>
parents:
8795
diff
changeset
|
556 'packpath' for plugins under the "pack/*/start" directory. First all those |
47f17f66da3d
commit https://github.com/vim/vim/commit/03413f44167c4b5cd0012def9bb331e2518c83cf
Christian Brabandt <cb@256bit.org>
parents:
8795
diff
changeset
|
557 directories are added to 'runtimepath'. Then all the plugins are loaded. |
47f17f66da3d
commit https://github.com/vim/vim/commit/03413f44167c4b5cd0012def9bb331e2518c83cf
Christian Brabandt <cb@256bit.org>
parents:
8795
diff
changeset
|
558 See |packload-two-steps| for how these two steps can be useful. |
8440
4c6ad81d41fe
commit https://github.com/vim/vim/commit/5f148ec0b5a6cedd9129b3abac351034b83cc4f7
Christian Brabandt <cb@256bit.org>
parents:
8416
diff
changeset
|
559 |
18831 | 560 In the example Vim will find "pack/foo/start/foobar/plugin/foo.vim" and adds |
8475
aec051e61547
commit https://github.com/vim/vim/commit/af1a0e371e739f8dff337fd31da0ff8ffb347b43
Christian Brabandt <cb@256bit.org>
parents:
8440
diff
changeset
|
561 "~/.vim/pack/foo/start/foobar" to 'runtimepath'. |
8440
4c6ad81d41fe
commit https://github.com/vim/vim/commit/5f148ec0b5a6cedd9129b3abac351034b83cc4f7
Christian Brabandt <cb@256bit.org>
parents:
8416
diff
changeset
|
562 |
4c6ad81d41fe
commit https://github.com/vim/vim/commit/5f148ec0b5a6cedd9129b3abac351034b83cc4f7
Christian Brabandt <cb@256bit.org>
parents:
8416
diff
changeset
|
563 If the "foobar" plugin kicks in and sets the 'filetype' to "some", Vim will |
4c6ad81d41fe
commit https://github.com/vim/vim/commit/5f148ec0b5a6cedd9129b3abac351034b83cc4f7
Christian Brabandt <cb@256bit.org>
parents:
8416
diff
changeset
|
564 find the syntax/some.vim file, because its directory is in 'runtimepath'. |
4c6ad81d41fe
commit https://github.com/vim/vim/commit/5f148ec0b5a6cedd9129b3abac351034b83cc4f7
Christian Brabandt <cb@256bit.org>
parents:
8416
diff
changeset
|
565 |
4c6ad81d41fe
commit https://github.com/vim/vim/commit/5f148ec0b5a6cedd9129b3abac351034b83cc4f7
Christian Brabandt <cb@256bit.org>
parents:
8416
diff
changeset
|
566 Vim will also load ftdetect files, if there are any. |
4c6ad81d41fe
commit https://github.com/vim/vim/commit/5f148ec0b5a6cedd9129b3abac351034b83cc4f7
Christian Brabandt <cb@256bit.org>
parents:
8416
diff
changeset
|
567 |
8748
b1a19a2f73f0
commit https://github.com/vim/vim/commit/4f3f668c8486444e53163c29d2fc79bf47eb3c82
Christian Brabandt <cb@256bit.org>
parents:
8673
diff
changeset
|
568 Note that the files under "pack/foo/opt" are not loaded automatically, only the |
8475
aec051e61547
commit https://github.com/vim/vim/commit/af1a0e371e739f8dff337fd31da0ff8ffb347b43
Christian Brabandt <cb@256bit.org>
parents:
8440
diff
changeset
|
569 ones under "pack/foo/start". See |pack-add| below for how the "opt" directory |
8440
4c6ad81d41fe
commit https://github.com/vim/vim/commit/5f148ec0b5a6cedd9129b3abac351034b83cc4f7
Christian Brabandt <cb@256bit.org>
parents:
8416
diff
changeset
|
570 is used. |
4c6ad81d41fe
commit https://github.com/vim/vim/commit/5f148ec0b5a6cedd9129b3abac351034b83cc4f7
Christian Brabandt <cb@256bit.org>
parents:
8416
diff
changeset
|
571 |
8526
981cc3bef9f3
commit https://github.com/vim/vim/commit/8dcf259d904cfb965d31841dc74a5cfaf5a351d9
Christian Brabandt <cb@256bit.org>
parents:
8475
diff
changeset
|
572 Loading packages automatically will not happen if loading plugins is disabled, |
981cc3bef9f3
commit https://github.com/vim/vim/commit/8dcf259d904cfb965d31841dc74a5cfaf5a351d9
Christian Brabandt <cb@256bit.org>
parents:
8475
diff
changeset
|
573 see |load-plugins|. |
981cc3bef9f3
commit https://github.com/vim/vim/commit/8dcf259d904cfb965d31841dc74a5cfaf5a351d9
Christian Brabandt <cb@256bit.org>
parents:
8475
diff
changeset
|
574 |
981cc3bef9f3
commit https://github.com/vim/vim/commit/8dcf259d904cfb965d31841dc74a5cfaf5a351d9
Christian Brabandt <cb@256bit.org>
parents:
8475
diff
changeset
|
575 To load packages earlier, so that 'runtimepath' gets updated: > |
981cc3bef9f3
commit https://github.com/vim/vim/commit/8dcf259d904cfb965d31841dc74a5cfaf5a351d9
Christian Brabandt <cb@256bit.org>
parents:
8475
diff
changeset
|
576 :packloadall |
981cc3bef9f3
commit https://github.com/vim/vim/commit/8dcf259d904cfb965d31841dc74a5cfaf5a351d9
Christian Brabandt <cb@256bit.org>
parents:
8475
diff
changeset
|
577 This also works when loading plugins is disabled. The automatic loading will |
981cc3bef9f3
commit https://github.com/vim/vim/commit/8dcf259d904cfb965d31841dc74a5cfaf5a351d9
Christian Brabandt <cb@256bit.org>
parents:
8475
diff
changeset
|
578 only happen once. |
8440
4c6ad81d41fe
commit https://github.com/vim/vim/commit/5f148ec0b5a6cedd9129b3abac351034b83cc4f7
Christian Brabandt <cb@256bit.org>
parents:
8416
diff
changeset
|
579 |
9116
bc38030aec7d
commit https://github.com/vim/vim/commit/26852128a2b713ef49341a0c18daba928444e7eb
Christian Brabandt <cb@256bit.org>
parents:
8876
diff
changeset
|
580 If the package has an "after" directory, that directory is added to the end of |
bc38030aec7d
commit https://github.com/vim/vim/commit/26852128a2b713ef49341a0c18daba928444e7eb
Christian Brabandt <cb@256bit.org>
parents:
8876
diff
changeset
|
581 'runtimepath', so that anything there will be loaded later. |
bc38030aec7d
commit https://github.com/vim/vim/commit/26852128a2b713ef49341a0c18daba928444e7eb
Christian Brabandt <cb@256bit.org>
parents:
8876
diff
changeset
|
582 |
8440
4c6ad81d41fe
commit https://github.com/vim/vim/commit/5f148ec0b5a6cedd9129b3abac351034b83cc4f7
Christian Brabandt <cb@256bit.org>
parents:
8416
diff
changeset
|
583 |
4c6ad81d41fe
commit https://github.com/vim/vim/commit/5f148ec0b5a6cedd9129b3abac351034b83cc4f7
Christian Brabandt <cb@256bit.org>
parents:
8416
diff
changeset
|
584 Using a single plugin and loading it automatically ~ |
8182
95d59081580f
commit https://github.com/vim/vim/commit/f6fee0e2d4341c0c2f5339c1268e5877fafd07cf
Christian Brabandt <cb@256bit.org>
parents:
8061
diff
changeset
|
585 |
8388
f5972de59001
commit https://github.com/vim/vim/commit/f3654827368e6204608036353a0360e9e7c21e02
Christian Brabandt <cb@256bit.org>
parents:
8376
diff
changeset
|
586 If you don't have a package but a single plugin, you need to create the extra |
f5972de59001
commit https://github.com/vim/vim/commit/f3654827368e6204608036353a0360e9e7c21e02
Christian Brabandt <cb@256bit.org>
parents:
8376
diff
changeset
|
587 directory level: |
8475
aec051e61547
commit https://github.com/vim/vim/commit/af1a0e371e739f8dff337fd31da0ff8ffb347b43
Christian Brabandt <cb@256bit.org>
parents:
8440
diff
changeset
|
588 % mkdir -p ~/.vim/pack/foo/start/foobar |
aec051e61547
commit https://github.com/vim/vim/commit/af1a0e371e739f8dff337fd31da0ff8ffb347b43
Christian Brabandt <cb@256bit.org>
parents:
8440
diff
changeset
|
589 % cd ~/.vim/pack/foo/start/foobar |
8440
4c6ad81d41fe
commit https://github.com/vim/vim/commit/5f148ec0b5a6cedd9129b3abac351034b83cc4f7
Christian Brabandt <cb@256bit.org>
parents:
8416
diff
changeset
|
590 % unzip /tmp/someplugin.zip |
8182
95d59081580f
commit https://github.com/vim/vim/commit/f6fee0e2d4341c0c2f5339c1268e5877fafd07cf
Christian Brabandt <cb@256bit.org>
parents:
8061
diff
changeset
|
591 |
8440
4c6ad81d41fe
commit https://github.com/vim/vim/commit/5f148ec0b5a6cedd9129b3abac351034b83cc4f7
Christian Brabandt <cb@256bit.org>
parents:
8416
diff
changeset
|
592 You would now have these files: |
8475
aec051e61547
commit https://github.com/vim/vim/commit/af1a0e371e739f8dff337fd31da0ff8ffb347b43
Christian Brabandt <cb@256bit.org>
parents:
8440
diff
changeset
|
593 pack/foo/start/foobar/plugin/foo.vim |
aec051e61547
commit https://github.com/vim/vim/commit/af1a0e371e739f8dff337fd31da0ff8ffb347b43
Christian Brabandt <cb@256bit.org>
parents:
8440
diff
changeset
|
594 pack/foo/start/foobar/syntax/some.vim |
8182
95d59081580f
commit https://github.com/vim/vim/commit/f6fee0e2d4341c0c2f5339c1268e5877fafd07cf
Christian Brabandt <cb@256bit.org>
parents:
8061
diff
changeset
|
595 |
8440
4c6ad81d41fe
commit https://github.com/vim/vim/commit/5f148ec0b5a6cedd9129b3abac351034b83cc4f7
Christian Brabandt <cb@256bit.org>
parents:
8416
diff
changeset
|
596 From here it works like above. |
8182
95d59081580f
commit https://github.com/vim/vim/commit/f6fee0e2d4341c0c2f5339c1268e5877fafd07cf
Christian Brabandt <cb@256bit.org>
parents:
8061
diff
changeset
|
597 |
8376
e448f2a5d45b
commit https://github.com/vim/vim/commit/91715873d19a1859c08eeded7848113596e2f2bd
Christian Brabandt <cb@256bit.org>
parents:
8303
diff
changeset
|
598 |
8440
4c6ad81d41fe
commit https://github.com/vim/vim/commit/5f148ec0b5a6cedd9129b3abac351034b83cc4f7
Christian Brabandt <cb@256bit.org>
parents:
8416
diff
changeset
|
599 Optional plugins ~ |
8388
f5972de59001
commit https://github.com/vim/vim/commit/f3654827368e6204608036353a0360e9e7c21e02
Christian Brabandt <cb@256bit.org>
parents:
8376
diff
changeset
|
600 *pack-add* |
f5972de59001
commit https://github.com/vim/vim/commit/f3654827368e6204608036353a0360e9e7c21e02
Christian Brabandt <cb@256bit.org>
parents:
8376
diff
changeset
|
601 To load an optional plugin from a pack use the `:packadd` command: > |
8440
4c6ad81d41fe
commit https://github.com/vim/vim/commit/5f148ec0b5a6cedd9129b3abac351034b83cc4f7
Christian Brabandt <cb@256bit.org>
parents:
8416
diff
changeset
|
602 :packadd foodebug |
4c6ad81d41fe
commit https://github.com/vim/vim/commit/5f148ec0b5a6cedd9129b3abac351034b83cc4f7
Christian Brabandt <cb@256bit.org>
parents:
8416
diff
changeset
|
603 This searches for "pack/*/opt/foodebug" in 'packpath' and will find |
4c6ad81d41fe
commit https://github.com/vim/vim/commit/5f148ec0b5a6cedd9129b3abac351034b83cc4f7
Christian Brabandt <cb@256bit.org>
parents:
8416
diff
changeset
|
604 ~/.vim/pack/foo/opt/foodebug/plugin/debugger.vim and source it. |
4c6ad81d41fe
commit https://github.com/vim/vim/commit/5f148ec0b5a6cedd9129b3abac351034b83cc4f7
Christian Brabandt <cb@256bit.org>
parents:
8416
diff
changeset
|
605 |
8748
b1a19a2f73f0
commit https://github.com/vim/vim/commit/4f3f668c8486444e53163c29d2fc79bf47eb3c82
Christian Brabandt <cb@256bit.org>
parents:
8673
diff
changeset
|
606 This could be done if some conditions are met. For example, depending on |
b1a19a2f73f0
commit https://github.com/vim/vim/commit/4f3f668c8486444e53163c29d2fc79bf47eb3c82
Christian Brabandt <cb@256bit.org>
parents:
8673
diff
changeset
|
607 whether Vim supports a feature or a dependency is missing. |
b1a19a2f73f0
commit https://github.com/vim/vim/commit/4f3f668c8486444e53163c29d2fc79bf47eb3c82
Christian Brabandt <cb@256bit.org>
parents:
8673
diff
changeset
|
608 |
b1a19a2f73f0
commit https://github.com/vim/vim/commit/4f3f668c8486444e53163c29d2fc79bf47eb3c82
Christian Brabandt <cb@256bit.org>
parents:
8673
diff
changeset
|
609 You can also load an optional plugin at startup, by putting this command in |
b1a19a2f73f0
commit https://github.com/vim/vim/commit/4f3f668c8486444e53163c29d2fc79bf47eb3c82
Christian Brabandt <cb@256bit.org>
parents:
8673
diff
changeset
|
610 your |.vimrc|: > |
b1a19a2f73f0
commit https://github.com/vim/vim/commit/4f3f668c8486444e53163c29d2fc79bf47eb3c82
Christian Brabandt <cb@256bit.org>
parents:
8673
diff
changeset
|
611 :packadd! foodebug |
9286
64035abb986b
commit https://github.com/vim/vim/commit/c95a302a4c42ec8230473cd4a5e0064d0a143aa8
Christian Brabandt <cb@256bit.org>
parents:
9116
diff
changeset
|
612 The extra "!" is so that the plugin isn't loaded if Vim was started with |
8748
b1a19a2f73f0
commit https://github.com/vim/vim/commit/4f3f668c8486444e53163c29d2fc79bf47eb3c82
Christian Brabandt <cb@256bit.org>
parents:
8673
diff
changeset
|
613 |--noplugin|. |
8182
95d59081580f
commit https://github.com/vim/vim/commit/f6fee0e2d4341c0c2f5339c1268e5877fafd07cf
Christian Brabandt <cb@256bit.org>
parents:
8061
diff
changeset
|
614 |
95d59081580f
commit https://github.com/vim/vim/commit/f6fee0e2d4341c0c2f5339c1268e5877fafd07cf
Christian Brabandt <cb@256bit.org>
parents:
8061
diff
changeset
|
615 It is perfectly normal for a package to only have files in the "opt" |
95d59081580f
commit https://github.com/vim/vim/commit/f6fee0e2d4341c0c2f5339c1268e5877fafd07cf
Christian Brabandt <cb@256bit.org>
parents:
8061
diff
changeset
|
616 directory. You then need to load each plugin when you want to use it. |
95d59081580f
commit https://github.com/vim/vim/commit/f6fee0e2d4341c0c2f5339c1268e5877fafd07cf
Christian Brabandt <cb@256bit.org>
parents:
8061
diff
changeset
|
617 |
8748
b1a19a2f73f0
commit https://github.com/vim/vim/commit/4f3f668c8486444e53163c29d2fc79bf47eb3c82
Christian Brabandt <cb@256bit.org>
parents:
8673
diff
changeset
|
618 |
b1a19a2f73f0
commit https://github.com/vim/vim/commit/4f3f668c8486444e53163c29d2fc79bf47eb3c82
Christian Brabandt <cb@256bit.org>
parents:
8673
diff
changeset
|
619 Where to put what ~ |
b1a19a2f73f0
commit https://github.com/vim/vim/commit/4f3f668c8486444e53163c29d2fc79bf47eb3c82
Christian Brabandt <cb@256bit.org>
parents:
8673
diff
changeset
|
620 |
b1a19a2f73f0
commit https://github.com/vim/vim/commit/4f3f668c8486444e53163c29d2fc79bf47eb3c82
Christian Brabandt <cb@256bit.org>
parents:
8673
diff
changeset
|
621 Since color schemes, loaded with `:colorscheme`, are found below |
b1a19a2f73f0
commit https://github.com/vim/vim/commit/4f3f668c8486444e53163c29d2fc79bf47eb3c82
Christian Brabandt <cb@256bit.org>
parents:
8673
diff
changeset
|
622 "pack/*/start" and "pack/*/opt", you could put them anywhere. We recommend |
b1a19a2f73f0
commit https://github.com/vim/vim/commit/4f3f668c8486444e53163c29d2fc79bf47eb3c82
Christian Brabandt <cb@256bit.org>
parents:
8673
diff
changeset
|
623 you put them below "pack/*/opt", for example |
b1a19a2f73f0
commit https://github.com/vim/vim/commit/4f3f668c8486444e53163c29d2fc79bf47eb3c82
Christian Brabandt <cb@256bit.org>
parents:
8673
diff
changeset
|
624 ".vim/pack/mycolors/opt/dark/colors/very_dark.vim". |
b1a19a2f73f0
commit https://github.com/vim/vim/commit/4f3f668c8486444e53163c29d2fc79bf47eb3c82
Christian Brabandt <cb@256bit.org>
parents:
8673
diff
changeset
|
625 |
b1a19a2f73f0
commit https://github.com/vim/vim/commit/4f3f668c8486444e53163c29d2fc79bf47eb3c82
Christian Brabandt <cb@256bit.org>
parents:
8673
diff
changeset
|
626 Filetype plugins should go under "pack/*/start", so that they are always |
b1a19a2f73f0
commit https://github.com/vim/vim/commit/4f3f668c8486444e53163c29d2fc79bf47eb3c82
Christian Brabandt <cb@256bit.org>
parents:
8673
diff
changeset
|
627 found. Unless you have more than one plugin for a file type and want to |
b1a19a2f73f0
commit https://github.com/vim/vim/commit/4f3f668c8486444e53163c29d2fc79bf47eb3c82
Christian Brabandt <cb@256bit.org>
parents:
8673
diff
changeset
|
628 select which one to load with `:packadd`. E.g. depending on the compiler |
b1a19a2f73f0
commit https://github.com/vim/vim/commit/4f3f668c8486444e53163c29d2fc79bf47eb3c82
Christian Brabandt <cb@256bit.org>
parents:
8673
diff
changeset
|
629 version: > |
b1a19a2f73f0
commit https://github.com/vim/vim/commit/4f3f668c8486444e53163c29d2fc79bf47eb3c82
Christian Brabandt <cb@256bit.org>
parents:
8673
diff
changeset
|
630 if foo_compiler_version > 34 |
b1a19a2f73f0
commit https://github.com/vim/vim/commit/4f3f668c8486444e53163c29d2fc79bf47eb3c82
Christian Brabandt <cb@256bit.org>
parents:
8673
diff
changeset
|
631 packadd foo_new |
b1a19a2f73f0
commit https://github.com/vim/vim/commit/4f3f668c8486444e53163c29d2fc79bf47eb3c82
Christian Brabandt <cb@256bit.org>
parents:
8673
diff
changeset
|
632 else |
b1a19a2f73f0
commit https://github.com/vim/vim/commit/4f3f668c8486444e53163c29d2fc79bf47eb3c82
Christian Brabandt <cb@256bit.org>
parents:
8673
diff
changeset
|
633 packadd foo_old |
b1a19a2f73f0
commit https://github.com/vim/vim/commit/4f3f668c8486444e53163c29d2fc79bf47eb3c82
Christian Brabandt <cb@256bit.org>
parents:
8673
diff
changeset
|
634 endif |
b1a19a2f73f0
commit https://github.com/vim/vim/commit/4f3f668c8486444e53163c29d2fc79bf47eb3c82
Christian Brabandt <cb@256bit.org>
parents:
8673
diff
changeset
|
635 |
b1a19a2f73f0
commit https://github.com/vim/vim/commit/4f3f668c8486444e53163c29d2fc79bf47eb3c82
Christian Brabandt <cb@256bit.org>
parents:
8673
diff
changeset
|
636 The "after" directory is most likely not useful in a package. It's not |
b1a19a2f73f0
commit https://github.com/vim/vim/commit/4f3f668c8486444e53163c29d2fc79bf47eb3c82
Christian Brabandt <cb@256bit.org>
parents:
8673
diff
changeset
|
637 disallowed though. |
b1a19a2f73f0
commit https://github.com/vim/vim/commit/4f3f668c8486444e53163c29d2fc79bf47eb3c82
Christian Brabandt <cb@256bit.org>
parents:
8673
diff
changeset
|
638 |
8182
95d59081580f
commit https://github.com/vim/vim/commit/f6fee0e2d4341c0c2f5339c1268e5877fafd07cf
Christian Brabandt <cb@256bit.org>
parents:
8061
diff
changeset
|
639 ============================================================================== |
8748
b1a19a2f73f0
commit https://github.com/vim/vim/commit/4f3f668c8486444e53163c29d2fc79bf47eb3c82
Christian Brabandt <cb@256bit.org>
parents:
8673
diff
changeset
|
640 6. Creating Vim packages *package-create* |
b1a19a2f73f0
commit https://github.com/vim/vim/commit/4f3f668c8486444e53163c29d2fc79bf47eb3c82
Christian Brabandt <cb@256bit.org>
parents:
8673
diff
changeset
|
641 |
b1a19a2f73f0
commit https://github.com/vim/vim/commit/4f3f668c8486444e53163c29d2fc79bf47eb3c82
Christian Brabandt <cb@256bit.org>
parents:
8673
diff
changeset
|
642 This assumes you write one or more plugins that you distribute as a package. |
b1a19a2f73f0
commit https://github.com/vim/vim/commit/4f3f668c8486444e53163c29d2fc79bf47eb3c82
Christian Brabandt <cb@256bit.org>
parents:
8673
diff
changeset
|
643 |
b1a19a2f73f0
commit https://github.com/vim/vim/commit/4f3f668c8486444e53163c29d2fc79bf47eb3c82
Christian Brabandt <cb@256bit.org>
parents:
8673
diff
changeset
|
644 If you have two unrelated plugins you would use two packages, so that Vim |
21499 | 645 users can choose what they include or not. Or you can decide to use one |
21825 | 646 package with optional plugins, and tell the user to add the preferred ones with |
8748
b1a19a2f73f0
commit https://github.com/vim/vim/commit/4f3f668c8486444e53163c29d2fc79bf47eb3c82
Christian Brabandt <cb@256bit.org>
parents:
8673
diff
changeset
|
647 `:packadd`. |
b1a19a2f73f0
commit https://github.com/vim/vim/commit/4f3f668c8486444e53163c29d2fc79bf47eb3c82
Christian Brabandt <cb@256bit.org>
parents:
8673
diff
changeset
|
648 |
b1a19a2f73f0
commit https://github.com/vim/vim/commit/4f3f668c8486444e53163c29d2fc79bf47eb3c82
Christian Brabandt <cb@256bit.org>
parents:
8673
diff
changeset
|
649 Decide how you want to distribute the package. You can create an archive or |
b1a19a2f73f0
commit https://github.com/vim/vim/commit/4f3f668c8486444e53163c29d2fc79bf47eb3c82
Christian Brabandt <cb@256bit.org>
parents:
8673
diff
changeset
|
650 you could use a repository. An archive can be used by more users, but is a |
b1a19a2f73f0
commit https://github.com/vim/vim/commit/4f3f668c8486444e53163c29d2fc79bf47eb3c82
Christian Brabandt <cb@256bit.org>
parents:
8673
diff
changeset
|
651 bit harder to update to a new version. A repository can usually be kept |
b1a19a2f73f0
commit https://github.com/vim/vim/commit/4f3f668c8486444e53163c29d2fc79bf47eb3c82
Christian Brabandt <cb@256bit.org>
parents:
8673
diff
changeset
|
652 up-to-date easily, but it requires a program like "git" to be available. |
b1a19a2f73f0
commit https://github.com/vim/vim/commit/4f3f668c8486444e53163c29d2fc79bf47eb3c82
Christian Brabandt <cb@256bit.org>
parents:
8673
diff
changeset
|
653 You can do both, github can automatically create an archive for a release. |
b1a19a2f73f0
commit https://github.com/vim/vim/commit/4f3f668c8486444e53163c29d2fc79bf47eb3c82
Christian Brabandt <cb@256bit.org>
parents:
8673
diff
changeset
|
654 |
b1a19a2f73f0
commit https://github.com/vim/vim/commit/4f3f668c8486444e53163c29d2fc79bf47eb3c82
Christian Brabandt <cb@256bit.org>
parents:
8673
diff
changeset
|
655 Your directory layout would be like this: |
b1a19a2f73f0
commit https://github.com/vim/vim/commit/4f3f668c8486444e53163c29d2fc79bf47eb3c82
Christian Brabandt <cb@256bit.org>
parents:
8673
diff
changeset
|
656 start/foobar/plugin/foo.vim " always loaded, defines commands |
b1a19a2f73f0
commit https://github.com/vim/vim/commit/4f3f668c8486444e53163c29d2fc79bf47eb3c82
Christian Brabandt <cb@256bit.org>
parents:
8673
diff
changeset
|
657 start/foobar/plugin/bar.vim " always loaded, defines commands |
b1a19a2f73f0
commit https://github.com/vim/vim/commit/4f3f668c8486444e53163c29d2fc79bf47eb3c82
Christian Brabandt <cb@256bit.org>
parents:
8673
diff
changeset
|
658 start/foobar/autoload/foo.vim " loaded when foo command used |
b1a19a2f73f0
commit https://github.com/vim/vim/commit/4f3f668c8486444e53163c29d2fc79bf47eb3c82
Christian Brabandt <cb@256bit.org>
parents:
8673
diff
changeset
|
659 start/foobar/doc/foo.txt " help for foo.vim |
b1a19a2f73f0
commit https://github.com/vim/vim/commit/4f3f668c8486444e53163c29d2fc79bf47eb3c82
Christian Brabandt <cb@256bit.org>
parents:
8673
diff
changeset
|
660 start/foobar/doc/tags " help tags |
b1a19a2f73f0
commit https://github.com/vim/vim/commit/4f3f668c8486444e53163c29d2fc79bf47eb3c82
Christian Brabandt <cb@256bit.org>
parents:
8673
diff
changeset
|
661 opt/fooextra/plugin/extra.vim " optional plugin, defines commands |
b1a19a2f73f0
commit https://github.com/vim/vim/commit/4f3f668c8486444e53163c29d2fc79bf47eb3c82
Christian Brabandt <cb@256bit.org>
parents:
8673
diff
changeset
|
662 opt/fooextra/autoload/extra.vim " loaded when extra command used |
b1a19a2f73f0
commit https://github.com/vim/vim/commit/4f3f668c8486444e53163c29d2fc79bf47eb3c82
Christian Brabandt <cb@256bit.org>
parents:
8673
diff
changeset
|
663 opt/fooextra/doc/extra.txt " help for extra.vim |
b1a19a2f73f0
commit https://github.com/vim/vim/commit/4f3f668c8486444e53163c29d2fc79bf47eb3c82
Christian Brabandt <cb@256bit.org>
parents:
8673
diff
changeset
|
664 opt/fooextra/doc/tags " help tags |
b1a19a2f73f0
commit https://github.com/vim/vim/commit/4f3f668c8486444e53163c29d2fc79bf47eb3c82
Christian Brabandt <cb@256bit.org>
parents:
8673
diff
changeset
|
665 |
b1a19a2f73f0
commit https://github.com/vim/vim/commit/4f3f668c8486444e53163c29d2fc79bf47eb3c82
Christian Brabandt <cb@256bit.org>
parents:
8673
diff
changeset
|
666 This allows for the user to do: > |
b1a19a2f73f0
commit https://github.com/vim/vim/commit/4f3f668c8486444e53163c29d2fc79bf47eb3c82
Christian Brabandt <cb@256bit.org>
parents:
8673
diff
changeset
|
667 mkdir ~/.vim/pack/myfoobar |
b1a19a2f73f0
commit https://github.com/vim/vim/commit/4f3f668c8486444e53163c29d2fc79bf47eb3c82
Christian Brabandt <cb@256bit.org>
parents:
8673
diff
changeset
|
668 cd ~/.vim/pack/myfoobar |
b1a19a2f73f0
commit https://github.com/vim/vim/commit/4f3f668c8486444e53163c29d2fc79bf47eb3c82
Christian Brabandt <cb@256bit.org>
parents:
8673
diff
changeset
|
669 git clone https://github.com/you/foobar.git |
b1a19a2f73f0
commit https://github.com/vim/vim/commit/4f3f668c8486444e53163c29d2fc79bf47eb3c82
Christian Brabandt <cb@256bit.org>
parents:
8673
diff
changeset
|
670 |
b1a19a2f73f0
commit https://github.com/vim/vim/commit/4f3f668c8486444e53163c29d2fc79bf47eb3c82
Christian Brabandt <cb@256bit.org>
parents:
8673
diff
changeset
|
671 Here "myfoobar" is a name that the user can choose, the only condition is that |
b1a19a2f73f0
commit https://github.com/vim/vim/commit/4f3f668c8486444e53163c29d2fc79bf47eb3c82
Christian Brabandt <cb@256bit.org>
parents:
8673
diff
changeset
|
672 it differs from other packages. |
b1a19a2f73f0
commit https://github.com/vim/vim/commit/4f3f668c8486444e53163c29d2fc79bf47eb3c82
Christian Brabandt <cb@256bit.org>
parents:
8673
diff
changeset
|
673 |
b1a19a2f73f0
commit https://github.com/vim/vim/commit/4f3f668c8486444e53163c29d2fc79bf47eb3c82
Christian Brabandt <cb@256bit.org>
parents:
8673
diff
changeset
|
674 In your documentation you explain what the plugins do, and tell the user how |
b1a19a2f73f0
commit https://github.com/vim/vim/commit/4f3f668c8486444e53163c29d2fc79bf47eb3c82
Christian Brabandt <cb@256bit.org>
parents:
8673
diff
changeset
|
675 to load the optional plugin: > |
b1a19a2f73f0
commit https://github.com/vim/vim/commit/4f3f668c8486444e53163c29d2fc79bf47eb3c82
Christian Brabandt <cb@256bit.org>
parents:
8673
diff
changeset
|
676 :packadd! fooextra |
b1a19a2f73f0
commit https://github.com/vim/vim/commit/4f3f668c8486444e53163c29d2fc79bf47eb3c82
Christian Brabandt <cb@256bit.org>
parents:
8673
diff
changeset
|
677 |
b1a19a2f73f0
commit https://github.com/vim/vim/commit/4f3f668c8486444e53163c29d2fc79bf47eb3c82
Christian Brabandt <cb@256bit.org>
parents:
8673
diff
changeset
|
678 You could add this packadd command in one of your plugins, to be executed when |
b1a19a2f73f0
commit https://github.com/vim/vim/commit/4f3f668c8486444e53163c29d2fc79bf47eb3c82
Christian Brabandt <cb@256bit.org>
parents:
8673
diff
changeset
|
679 the optional plugin is needed. |
b1a19a2f73f0
commit https://github.com/vim/vim/commit/4f3f668c8486444e53163c29d2fc79bf47eb3c82
Christian Brabandt <cb@256bit.org>
parents:
8673
diff
changeset
|
680 |
b1a19a2f73f0
commit https://github.com/vim/vim/commit/4f3f668c8486444e53163c29d2fc79bf47eb3c82
Christian Brabandt <cb@256bit.org>
parents:
8673
diff
changeset
|
681 Run the `:helptags` command to generate the doc/tags file. Including this |
21825 | 682 generated file in the package means that the user can drop the package in the |
8748
b1a19a2f73f0
commit https://github.com/vim/vim/commit/4f3f668c8486444e53163c29d2fc79bf47eb3c82
Christian Brabandt <cb@256bit.org>
parents:
8673
diff
changeset
|
683 pack directory and the help command works right away. Don't forget to re-run |
b1a19a2f73f0
commit https://github.com/vim/vim/commit/4f3f668c8486444e53163c29d2fc79bf47eb3c82
Christian Brabandt <cb@256bit.org>
parents:
8673
diff
changeset
|
684 the command after changing the plugin help: > |
b1a19a2f73f0
commit https://github.com/vim/vim/commit/4f3f668c8486444e53163c29d2fc79bf47eb3c82
Christian Brabandt <cb@256bit.org>
parents:
8673
diff
changeset
|
685 :helptags path/start/foobar/doc |
b1a19a2f73f0
commit https://github.com/vim/vim/commit/4f3f668c8486444e53163c29d2fc79bf47eb3c82
Christian Brabandt <cb@256bit.org>
parents:
8673
diff
changeset
|
686 :helptags path/opt/fooextra/doc |
b1a19a2f73f0
commit https://github.com/vim/vim/commit/4f3f668c8486444e53163c29d2fc79bf47eb3c82
Christian Brabandt <cb@256bit.org>
parents:
8673
diff
changeset
|
687 |
8876
47f17f66da3d
commit https://github.com/vim/vim/commit/03413f44167c4b5cd0012def9bb331e2518c83cf
Christian Brabandt <cb@256bit.org>
parents:
8795
diff
changeset
|
688 |
47f17f66da3d
commit https://github.com/vim/vim/commit/03413f44167c4b5cd0012def9bb331e2518c83cf
Christian Brabandt <cb@256bit.org>
parents:
8795
diff
changeset
|
689 Dependencies between plugins ~ |
47f17f66da3d
commit https://github.com/vim/vim/commit/03413f44167c4b5cd0012def9bb331e2518c83cf
Christian Brabandt <cb@256bit.org>
parents:
8795
diff
changeset
|
690 *packload-two-steps* |
9286
64035abb986b
commit https://github.com/vim/vim/commit/c95a302a4c42ec8230473cd4a5e0064d0a143aa8
Christian Brabandt <cb@256bit.org>
parents:
9116
diff
changeset
|
691 Suppose you have two plugins that depend on the same functionality. You can |
8876
47f17f66da3d
commit https://github.com/vim/vim/commit/03413f44167c4b5cd0012def9bb331e2518c83cf
Christian Brabandt <cb@256bit.org>
parents:
8795
diff
changeset
|
692 put the common functionality in an autoload directory, so that it will be |
47f17f66da3d
commit https://github.com/vim/vim/commit/03413f44167c4b5cd0012def9bb331e2518c83cf
Christian Brabandt <cb@256bit.org>
parents:
8795
diff
changeset
|
693 found automatically. Your package would have these files: |
47f17f66da3d
commit https://github.com/vim/vim/commit/03413f44167c4b5cd0012def9bb331e2518c83cf
Christian Brabandt <cb@256bit.org>
parents:
8795
diff
changeset
|
694 |
47f17f66da3d
commit https://github.com/vim/vim/commit/03413f44167c4b5cd0012def9bb331e2518c83cf
Christian Brabandt <cb@256bit.org>
parents:
8795
diff
changeset
|
695 pack/foo/start/one/plugin/one.vim > |
47f17f66da3d
commit https://github.com/vim/vim/commit/03413f44167c4b5cd0012def9bb331e2518c83cf
Christian Brabandt <cb@256bit.org>
parents:
8795
diff
changeset
|
696 call foolib#getit() |
47f17f66da3d
commit https://github.com/vim/vim/commit/03413f44167c4b5cd0012def9bb331e2518c83cf
Christian Brabandt <cb@256bit.org>
parents:
8795
diff
changeset
|
697 < pack/foo/start/two/plugin/two.vim > |
47f17f66da3d
commit https://github.com/vim/vim/commit/03413f44167c4b5cd0012def9bb331e2518c83cf
Christian Brabandt <cb@256bit.org>
parents:
8795
diff
changeset
|
698 call foolib#getit() |
47f17f66da3d
commit https://github.com/vim/vim/commit/03413f44167c4b5cd0012def9bb331e2518c83cf
Christian Brabandt <cb@256bit.org>
parents:
8795
diff
changeset
|
699 < pack/foo/start/lib/autoload/foolib.vim > |
47f17f66da3d
commit https://github.com/vim/vim/commit/03413f44167c4b5cd0012def9bb331e2518c83cf
Christian Brabandt <cb@256bit.org>
parents:
8795
diff
changeset
|
700 func foolib#getit() |
47f17f66da3d
commit https://github.com/vim/vim/commit/03413f44167c4b5cd0012def9bb331e2518c83cf
Christian Brabandt <cb@256bit.org>
parents:
8795
diff
changeset
|
701 |
47f17f66da3d
commit https://github.com/vim/vim/commit/03413f44167c4b5cd0012def9bb331e2518c83cf
Christian Brabandt <cb@256bit.org>
parents:
8795
diff
changeset
|
702 This works, because loading packages will first add all found directories to |
47f17f66da3d
commit https://github.com/vim/vim/commit/03413f44167c4b5cd0012def9bb331e2518c83cf
Christian Brabandt <cb@256bit.org>
parents:
8795
diff
changeset
|
703 'runtimepath' before sourcing the plugins. |
47f17f66da3d
commit https://github.com/vim/vim/commit/03413f44167c4b5cd0012def9bb331e2518c83cf
Christian Brabandt <cb@256bit.org>
parents:
8795
diff
changeset
|
704 |
8748
b1a19a2f73f0
commit https://github.com/vim/vim/commit/4f3f668c8486444e53163c29d2fc79bf47eb3c82
Christian Brabandt <cb@256bit.org>
parents:
8673
diff
changeset
|
705 ============================================================================== |
b1a19a2f73f0
commit https://github.com/vim/vim/commit/4f3f668c8486444e53163c29d2fc79bf47eb3c82
Christian Brabandt <cb@256bit.org>
parents:
8673
diff
changeset
|
706 7. Debugging scripts *debug-scripts* |
7 | 707 |
708 Besides the obvious messages that you can add to your scripts to find out what | |
709 they are doing, Vim offers a debug mode. This allows you to step through a | |
710 sourced file or user function and set breakpoints. | |
711 | |
712 NOTE: The debugging mode is far from perfect. Debugging will have side | |
713 effects on how Vim works. You cannot use it to debug everything. For | |
714 example, the display is messed up by the debugging messages. | |
715 | |
716 An alternative to debug mode is setting the 'verbose' option. With a bigger | |
717 number it will give more verbose messages about what Vim is doing. | |
718 | |
719 | |
720 STARTING DEBUG MODE *debug-mode* | |
721 | |
722 To enter debugging mode use one of these methods: | |
723 1. Start Vim with the |-D| argument: > | |
724 vim -D file.txt | |
725 < Debugging will start as soon as the first vimrc file is sourced. This is | |
726 useful to find out what is happening when Vim is starting up. A side | |
727 effect is that Vim will switch the terminal mode before initialisations | |
728 have finished, with unpredictable results. | |
729 For a GUI-only version (Windows, Macintosh) the debugging will start as | |
730 soon as the GUI window has been opened. To make this happen early, add a | |
731 ":gui" command in the vimrc file. | |
732 *:debug* | |
733 2. Run a command with ":debug" prepended. Debugging will only be done while | |
734 this command executes. Useful for debugging a specific script or user | |
735 function. And for scripts and functions used by autocommands. Example: > | |
736 :debug edit test.txt.gz | |
737 | |
738 3. Set a breakpoint in a sourced file or user function. You could do this in | |
739 the command line: > | |
740 vim -c "breakadd file */explorer.vim" . | |
741 < This will run Vim and stop in the first line of the "explorer.vim" script. | |
742 Breakpoints can also be set while in debugging mode. | |
743 | |
744 In debugging mode every executed command is displayed before it is executed. | |
745 Comment lines, empty lines and lines that are not executed are skipped. When | |
746 a line contains two commands, separated by "|", each command will be displayed | |
747 separately. | |
748 | |
749 | |
750 DEBUG MODE | |
751 | |
752 Once in debugging mode, the usual Ex commands can be used. For example, to | |
753 inspect the value of a variable: > | |
754 echo idx | |
755 When inside a user function, this will print the value of the local variable | |
756 "idx". Prepend "g:" to get the value of a global variable: > | |
757 echo g:idx | |
758 All commands are executed in the context of the current function or script. | |
759 You can also set options, for example setting or resetting 'verbose' will show | |
760 what happens, but you might want to set it just before executing the lines you | |
761 are interested in: > | |
762 :set verbose=20 | |
763 | |
764 Commands that require updating the screen should be avoided, because their | |
765 effect won't be noticed until after leaving debug mode. For example: > | |
766 :help | |
767 won't be very helpful. | |
768 | |
769 There is a separate command-line history for debug mode. | |
770 | |
771 The line number for a function line is relative to the start of the function. | |
772 If you have trouble figuring out where you are, edit the file that defines | |
773 the function in another Vim, search for the start of the function and do | |
774 "99j". Replace "99" with the line number. | |
775 | |
776 Additionally, these commands can be used: | |
777 *>cont* | |
778 cont Continue execution until the next breakpoint is hit. | |
779 *>quit* | |
780 quit Abort execution. This is like using CTRL-C, some | |
781 things might still be executed, doesn't abort | |
782 everything. Still stops at the next breakpoint. | |
783 *>next* | |
784 next Execute the command and come back to debug mode when | |
785 it's finished. This steps over user function calls | |
786 and sourced files. | |
787 *>step* | |
788 step Execute the command and come back to debug mode for | |
789 the next command. This steps into called user | |
790 functions and sourced files. | |
791 *>interrupt* | |
792 interrupt This is like using CTRL-C, but unlike ">quit" comes | |
793 back to debug mode for the next command that is | |
794 executed. Useful for testing |:finally| and |:catch| | |
795 on interrupt exceptions. | |
796 *>finish* | |
797 finish Finish the current script or user function and come | |
798 back to debug mode for the command after the one that | |
799 sourced or called it. | |
7605
8fc60af6dbf5
commit https://github.com/vim/vim/commit/f1f60f859cdbb2638b3662ccf7b1d179865fe7dc
Christian Brabandt <cb@256bit.org>
parents:
7233
diff
changeset
|
800 *>bt* |
8fc60af6dbf5
commit https://github.com/vim/vim/commit/f1f60f859cdbb2638b3662ccf7b1d179865fe7dc
Christian Brabandt <cb@256bit.org>
parents:
7233
diff
changeset
|
801 *>backtrace* |
8fc60af6dbf5
commit https://github.com/vim/vim/commit/f1f60f859cdbb2638b3662ccf7b1d179865fe7dc
Christian Brabandt <cb@256bit.org>
parents:
7233
diff
changeset
|
802 *>where* |
8fc60af6dbf5
commit https://github.com/vim/vim/commit/f1f60f859cdbb2638b3662ccf7b1d179865fe7dc
Christian Brabandt <cb@256bit.org>
parents:
7233
diff
changeset
|
803 backtrace Show the call stacktrace for current debugging session. |
8fc60af6dbf5
commit https://github.com/vim/vim/commit/f1f60f859cdbb2638b3662ccf7b1d179865fe7dc
Christian Brabandt <cb@256bit.org>
parents:
7233
diff
changeset
|
804 bt |
8fc60af6dbf5
commit https://github.com/vim/vim/commit/f1f60f859cdbb2638b3662ccf7b1d179865fe7dc
Christian Brabandt <cb@256bit.org>
parents:
7233
diff
changeset
|
805 where |
8fc60af6dbf5
commit https://github.com/vim/vim/commit/f1f60f859cdbb2638b3662ccf7b1d179865fe7dc
Christian Brabandt <cb@256bit.org>
parents:
7233
diff
changeset
|
806 *>frame* |
8061
abd64cf67bcf
commit https://github.com/vim/vim/commit/38a55639d603823efcf2d2fdf542dbffdeb60b75
Christian Brabandt <cb@256bit.org>
parents:
7605
diff
changeset
|
807 frame N Goes to N backtrace level. + and - signs make movement |
7605
8fc60af6dbf5
commit https://github.com/vim/vim/commit/f1f60f859cdbb2638b3662ccf7b1d179865fe7dc
Christian Brabandt <cb@256bit.org>
parents:
7233
diff
changeset
|
808 relative. E.g., ":frame +3" goes three frames up. |
8fc60af6dbf5
commit https://github.com/vim/vim/commit/f1f60f859cdbb2638b3662ccf7b1d179865fe7dc
Christian Brabandt <cb@256bit.org>
parents:
7233
diff
changeset
|
809 *>up* |
8fc60af6dbf5
commit https://github.com/vim/vim/commit/f1f60f859cdbb2638b3662ccf7b1d179865fe7dc
Christian Brabandt <cb@256bit.org>
parents:
7233
diff
changeset
|
810 up Goes one level up from call stacktrace. |
8fc60af6dbf5
commit https://github.com/vim/vim/commit/f1f60f859cdbb2638b3662ccf7b1d179865fe7dc
Christian Brabandt <cb@256bit.org>
parents:
7233
diff
changeset
|
811 *>down* |
8fc60af6dbf5
commit https://github.com/vim/vim/commit/f1f60f859cdbb2638b3662ccf7b1d179865fe7dc
Christian Brabandt <cb@256bit.org>
parents:
7233
diff
changeset
|
812 down Goes one level down from call stacktrace. |
7 | 813 |
814 About the additional commands in debug mode: | |
815 - There is no command-line completion for them, you get the completion for the | |
816 normal Ex commands only. | |
8303
88207f4b861a
commit https://github.com/vim/vim/commit/dae8d21dd291df6a6679a00be64e18bca0156576
Christian Brabandt <cb@256bit.org>
parents:
8246
diff
changeset
|
817 - You can shorten them, up to a single character, unless more than one command |
7605
8fc60af6dbf5
commit https://github.com/vim/vim/commit/f1f60f859cdbb2638b3662ccf7b1d179865fe7dc
Christian Brabandt <cb@256bit.org>
parents:
7233
diff
changeset
|
818 starts with the same letter. "f" stands for "finish", use "fr" for "frame". |
7 | 819 - Hitting <CR> will repeat the previous one. When doing another command, this |
820 is reset (because it's not clear what you want to repeat). | |
821 - When you want to use the Ex command with the same name, prepend a colon: | |
822 ":cont", ":next", ":finish" (or shorter). | |
823 | |
7605
8fc60af6dbf5
commit https://github.com/vim/vim/commit/f1f60f859cdbb2638b3662ccf7b1d179865fe7dc
Christian Brabandt <cb@256bit.org>
parents:
7233
diff
changeset
|
824 The backtrace shows the hierarchy of function calls, e.g.: |
8fc60af6dbf5
commit https://github.com/vim/vim/commit/f1f60f859cdbb2638b3662ccf7b1d179865fe7dc
Christian Brabandt <cb@256bit.org>
parents:
7233
diff
changeset
|
825 >bt ~ |
8fc60af6dbf5
commit https://github.com/vim/vim/commit/f1f60f859cdbb2638b3662ccf7b1d179865fe7dc
Christian Brabandt <cb@256bit.org>
parents:
7233
diff
changeset
|
826 3 function One[3] ~ |
8fc60af6dbf5
commit https://github.com/vim/vim/commit/f1f60f859cdbb2638b3662ccf7b1d179865fe7dc
Christian Brabandt <cb@256bit.org>
parents:
7233
diff
changeset
|
827 2 Two[3] ~ |
8fc60af6dbf5
commit https://github.com/vim/vim/commit/f1f60f859cdbb2638b3662ccf7b1d179865fe7dc
Christian Brabandt <cb@256bit.org>
parents:
7233
diff
changeset
|
828 ->1 Three[3] ~ |
8fc60af6dbf5
commit https://github.com/vim/vim/commit/f1f60f859cdbb2638b3662ccf7b1d179865fe7dc
Christian Brabandt <cb@256bit.org>
parents:
7233
diff
changeset
|
829 0 Four ~ |
8fc60af6dbf5
commit https://github.com/vim/vim/commit/f1f60f859cdbb2638b3662ccf7b1d179865fe7dc
Christian Brabandt <cb@256bit.org>
parents:
7233
diff
changeset
|
830 line 1: let four = 4 ~ |
8fc60af6dbf5
commit https://github.com/vim/vim/commit/f1f60f859cdbb2638b3662ccf7b1d179865fe7dc
Christian Brabandt <cb@256bit.org>
parents:
7233
diff
changeset
|
831 |
8fc60af6dbf5
commit https://github.com/vim/vim/commit/f1f60f859cdbb2638b3662ccf7b1d179865fe7dc
Christian Brabandt <cb@256bit.org>
parents:
7233
diff
changeset
|
832 The "->" points to the current frame. Use "up", "down" and "frame N" to |
8fc60af6dbf5
commit https://github.com/vim/vim/commit/f1f60f859cdbb2638b3662ccf7b1d179865fe7dc
Christian Brabandt <cb@256bit.org>
parents:
7233
diff
changeset
|
833 select another frame. |
8fc60af6dbf5
commit https://github.com/vim/vim/commit/f1f60f859cdbb2638b3662ccf7b1d179865fe7dc
Christian Brabandt <cb@256bit.org>
parents:
7233
diff
changeset
|
834 |
8fc60af6dbf5
commit https://github.com/vim/vim/commit/f1f60f859cdbb2638b3662ccf7b1d179865fe7dc
Christian Brabandt <cb@256bit.org>
parents:
7233
diff
changeset
|
835 In the current frame you can evaluate the local function variables. There is |
8fc60af6dbf5
commit https://github.com/vim/vim/commit/f1f60f859cdbb2638b3662ccf7b1d179865fe7dc
Christian Brabandt <cb@256bit.org>
parents:
7233
diff
changeset
|
836 no way to see the command at the current line yet. |
8fc60af6dbf5
commit https://github.com/vim/vim/commit/f1f60f859cdbb2638b3662ccf7b1d179865fe7dc
Christian Brabandt <cb@256bit.org>
parents:
7233
diff
changeset
|
837 |
7 | 838 |
839 DEFINING BREAKPOINTS | |
840 *:breaka* *:breakadd* | |
841 :breaka[dd] func [lnum] {name} | |
842 Set a breakpoint in a function. Example: > | |
843 :breakadd func Explore | |
844 < Doesn't check for a valid function name, thus the breakpoint | |
845 can be set before the function is defined. | |
846 | |
847 :breaka[dd] file [lnum] {name} | |
848 Set a breakpoint in a sourced file. Example: > | |
849 :breakadd file 43 .vimrc | |
850 | |
10 | 851 :breaka[dd] here |
852 Set a breakpoint in the current line of the current file. | |
853 Like doing: > | |
854 :breakadd file <cursor-line> <current-file> | |
855 < Note that this only works for commands that are executed when | |
856 sourcing the file, not for a function defined in that file. | |
857 | |
13262
69278c25429d
patch 8.0.1505: debugger can't break on a condition
Christian Brabandt <cb@256bit.org>
parents:
13051
diff
changeset
|
858 :breaka[dd] expr {expression} |
69278c25429d
patch 8.0.1505: debugger can't break on a condition
Christian Brabandt <cb@256bit.org>
parents:
13051
diff
changeset
|
859 Sets a breakpoint, that will break whenever the {expression} |
69278c25429d
patch 8.0.1505: debugger can't break on a condition
Christian Brabandt <cb@256bit.org>
parents:
13051
diff
changeset
|
860 evaluates to a different value. Example: > |
69278c25429d
patch 8.0.1505: debugger can't break on a condition
Christian Brabandt <cb@256bit.org>
parents:
13051
diff
changeset
|
861 :breakadd expr g:lnum |
69278c25429d
patch 8.0.1505: debugger can't break on a condition
Christian Brabandt <cb@256bit.org>
parents:
13051
diff
changeset
|
862 |
69278c25429d
patch 8.0.1505: debugger can't break on a condition
Christian Brabandt <cb@256bit.org>
parents:
13051
diff
changeset
|
863 < Will break, whenever the global variable lnum changes. |
69278c25429d
patch 8.0.1505: debugger can't break on a condition
Christian Brabandt <cb@256bit.org>
parents:
13051
diff
changeset
|
864 Note if you watch a |script-variable| this will break |
69278c25429d
patch 8.0.1505: debugger can't break on a condition
Christian Brabandt <cb@256bit.org>
parents:
13051
diff
changeset
|
865 when switching scripts, since the script variable is only |
69278c25429d
patch 8.0.1505: debugger can't break on a condition
Christian Brabandt <cb@256bit.org>
parents:
13051
diff
changeset
|
866 valid in the script where it has been defined and if that |
69278c25429d
patch 8.0.1505: debugger can't break on a condition
Christian Brabandt <cb@256bit.org>
parents:
13051
diff
changeset
|
867 script is called from several other scripts, this will stop |
69278c25429d
patch 8.0.1505: debugger can't break on a condition
Christian Brabandt <cb@256bit.org>
parents:
13051
diff
changeset
|
868 whenever that particular variable will become visible or |
69278c25429d
patch 8.0.1505: debugger can't break on a condition
Christian Brabandt <cb@256bit.org>
parents:
13051
diff
changeset
|
869 unaccessible again. |
69278c25429d
patch 8.0.1505: debugger can't break on a condition
Christian Brabandt <cb@256bit.org>
parents:
13051
diff
changeset
|
870 |
7 | 871 The [lnum] is the line number of the breakpoint. Vim will stop at or after |
872 this line. When omitted line 1 is used. | |
873 | |
170 | 874 *:debug-name* |
7 | 875 {name} is a pattern that is matched with the file or function name. The |
876 pattern is like what is used for autocommands. There must be a full match (as | |
877 if the pattern starts with "^" and ends in "$"). A "*" matches any sequence | |
878 of characters. 'ignorecase' is not used, but "\c" can be used in the pattern | |
879 to ignore case |/\c|. Don't include the () for the function name! | |
880 | |
11 | 881 The match for sourced scripts is done against the full file name. If no path |
882 is specified the current directory is used. Examples: > | |
883 breakadd file explorer.vim | |
884 matches "explorer.vim" in the current directory. > | |
7 | 885 breakadd file *explorer.vim |
11 | 886 matches ".../plugin/explorer.vim", ".../plugin/iexplorer.vim", etc. > |
7 | 887 breakadd file */explorer.vim |
11 | 888 matches ".../plugin/explorer.vim" and "explorer.vim" in any other directory. |
7 | 889 |
890 The match for functions is done against the name as it's shown in the output | |
891 of ":function". For local functions this means that something like "<SNR>99_" | |
892 is prepended. | |
893 | |
148 | 894 Note that functions are first loaded and later executed. When they are loaded |
895 the "file" breakpoints are checked, when they are executed the "func" | |
896 breakpoints. | |
897 | |
7 | 898 |
899 DELETING BREAKPOINTS | |
900 *:breakd* *:breakdel* *E161* | |
901 :breakd[el] {nr} | |
902 Delete breakpoint {nr}. Use |:breaklist| to see the number of | |
903 each breakpoint. | |
904 | |
359 | 905 :breakd[el] * |
906 Delete all breakpoints. | |
907 | |
7 | 908 :breakd[el] func [lnum] {name} |
909 Delete a breakpoint in a function. | |
910 | |
911 :breakd[el] file [lnum] {name} | |
912 Delete a breakpoint in a sourced file. | |
913 | |
10 | 914 :breakd[el] here |
915 Delete a breakpoint at the current line of the current file. | |
916 | |
7 | 917 When [lnum] is omitted, the first breakpoint in the function or file is |
918 deleted. | |
919 The {name} must be exactly the same as what was typed for the ":breakadd" | |
920 command. "explorer", "*explorer.vim" and "*explorer*" are different. | |
921 | |
922 | |
923 LISTING BREAKPOINTS | |
924 *:breakl* *:breaklist* | |
925 :breakl[ist] | |
926 List all breakpoints. | |
927 | |
928 | |
929 OBSCURE | |
930 | |
931 *:debugg* *:debuggreedy* | |
932 :debugg[reedy] | |
933 Read debug mode commands from the normal input stream, instead | |
934 of getting them directly from the user. Only useful for test | |
935 scripts. Example: > | |
936 echo 'q^Mq' | vim -e -s -c debuggreedy -c 'breakadd file script.vim' -S script.vim | |
937 | |
938 :0debugg[reedy] | |
939 Undo ":debuggreedy": get debug mode commands directly from the | |
940 user, don't use typeahead for debug commands. | |
941 | |
170 | 942 ============================================================================== |
8748
b1a19a2f73f0
commit https://github.com/vim/vim/commit/4f3f668c8486444e53163c29d2fc79bf47eb3c82
Christian Brabandt <cb@256bit.org>
parents:
8673
diff
changeset
|
943 8. Profiling *profile* *profiling* |
170 | 944 |
2283
7e1bd501306d
Mainly documentation updates.
Bram Moolenaar <bram@vim.org>
parents:
2207
diff
changeset
|
945 Profiling means that Vim measures the time that is spent on executing |
170 | 946 functions and/or scripts. The |+profile| feature is required for this. |
947 It is only included when Vim was compiled with "huge" features. | |
948 | |
794 | 949 You can also use the |reltime()| function to measure time. This only requires |
950 the |+reltime| feature, which is present more often. | |
951 | |
5244 | 952 For profiling syntax highlighting see |:syntime|. |
953 | |
5763 | 954 For example, to profile the one_script.vim script file: > |
955 :profile start /tmp/one_script_profile | |
956 :profile file one_script.vim | |
957 :source one_script.vim | |
958 :exit | |
959 | |
5244 | 960 |
170 | 961 :prof[ile] start {fname} *:prof* *:profile* *E750* |
962 Start profiling, write the output in {fname} upon exit. | |
6757 | 963 "~/" and environment variables in {fname} will be expanded. |
790 | 964 If {fname} already exists it will be silently overwritten. |
170 | 965 The variable |v:profiling| is set to one. |
966 | |
790 | 967 :prof[ile] pause |
968 Don't profile until the following ":profile continue". Can be | |
969 used when doing something that should not be counted (e.g., an | |
970 external command). Does not nest. | |
971 | |
972 :prof[ile] continue | |
973 Continue profiling after ":profile pause". | |
974 | |
170 | 975 :prof[ile] func {pattern} |
976 Profile function that matches the pattern {pattern}. | |
977 See |:debug-name| for how {pattern} is used. | |
978 | |
979 :prof[ile][!] file {pattern} | |
980 Profile script file that matches the pattern {pattern}. | |
981 See |:debug-name| for how {pattern} is used. | |
982 This only profiles the script itself, not the functions | |
983 defined in it. | |
984 When the [!] is added then all functions defined in the script | |
5763 | 985 will also be profiled. |
986 Note that profiling only starts when the script is loaded | |
987 after this command. A :profile command in the script itself | |
988 won't work. | |
170 | 989 |
990 | |
364 | 991 :profd[el] ... *:profd* *:profdel* |
992 Stop profiling for the arguments specified. See |:breakdel| | |
993 for the arguments. | |
994 | |
995 | |
170 | 996 You must always start with a ":profile start fname" command. The resulting |
997 file is written when Vim exits. Here is an example of the output, with line | |
998 numbers prepended for the explanation: | |
999 | |
1000 1 FUNCTION Test2() ~ | |
1001 2 Called 1 time ~ | |
1002 3 Total time: 0.155251 ~ | |
1003 4 Self time: 0.002006 ~ | |
1004 5 ~ | |
1005 6 count total (s) self (s) ~ | |
856 | 1006 7 9 0.000096 for i in range(8) ~ |
1007 8 8 0.153655 0.000410 call Test3() ~ | |
1008 9 8 0.000070 endfor ~ | |
1009 10 " Ask a question ~ | |
1010 11 1 0.001341 echo input("give me an answer: ") ~ | |
170 | 1011 |
1012 The header (lines 1-4) gives the time for the whole function. The "Total" | |
1013 time is the time passed while the function was executing. The "Self" time is | |
1014 the "Total" time reduced by time spent in: | |
1015 - other user defined functions | |
1016 - sourced scripts | |
1017 - executed autocommands | |
1018 - external (shell) commands | |
1019 | |
1020 Lines 7-11 show the time spent in each executed line. Lines that are not | |
1021 executed do not count. Thus a comment line is never counted. | |
1022 | |
1023 The Count column shows how many times a line was executed. Note that the | |
1024 "for" command in line 7 is executed one more time as the following lines. | |
1025 That is because the line is also executed to detect the end of the loop. | |
1026 | |
1027 The time Vim spends waiting for user input isn't counted at all. Thus how | |
1028 long you take to respond to the input() prompt is irrelevant. | |
1029 | |
1030 Profiling should give a good indication of where time is spent, but keep in | |
1031 mind there are various things that may clobber the results: | |
1032 | |
1033 - The accuracy of the time measured depends on the gettimeofday() system | |
1034 function. It may only be as accurate as 1/100 second, even though the times | |
1035 are displayed in micro seconds. | |
1036 | |
1037 - Real elapsed time is measured, if other processes are busy they may cause | |
1038 delays at unpredictable moments. You may want to run the profiling several | |
1039 times and use the lowest results. | |
1040 | |
1041 - If you have several commands in one line you only get one time. Split the | |
1042 line to see the time for the individual commands. | |
1043 | |
1044 - The time of the lines added up is mostly less than the time of the whole | |
1045 function. There is some overhead in between. | |
1046 | |
1047 - Functions that are deleted before Vim exits will not produce profiling | |
1048 information. You can check the |v:profiling| variable if needed: > | |
856 | 1049 :if !v:profiling |
170 | 1050 : delfunc MyFunc |
1051 :endif | |
1052 < | |
177 | 1053 - Profiling may give weird results on multi-processor systems, when sleep |
1054 mode kicks in or the processor frequency is reduced to save power. | |
170 | 1055 |
1125 | 1056 - The "self" time is wrong when a function is used recursively. |
1057 | |
1058 | |
14421 | 1059 vim:tw=78:ts=8:noet:ft=help:norl: |