Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP
Newer
Older
100644 432 lines (364 sloc) 19.459 kB
379f642 @ZyX-I Fixed first tag in new file
ZyX-I authored
1 *vim-addon-manager-getting-started.txt* Declarative package manager for Vim
ca3b3c9 @MarcWeber improve docs:
authored
2 ==============================================================================
b614015 @MarcWeber remove duplicate tags
authored
3 CONTENTS *VAM-contents-getting-started*
ca3b3c9 @MarcWeber improve docs:
authored
4
5 0. GETTING STARTED & LOOKING FOR HELP <<
6
7 1. Intro |VAM-intro|
6d27796 @ZyX-I Section tags work fine no matter where these tags are located.
ZyX-I authored
8 2. Installation & installing plugins |VAM-installation|
ca3b3c9 @MarcWeber improve docs:
authored
9 2.2 Names of addons and addon soucres |VAM-addon-names|
10 2.3 Example: configurable setup |VAM-complex-setup-sample|
11 2.4 unattended installation |VAM-unattended-installation|
6d27796 @ZyX-I Section tags work fine no matter where these tags are located.
ZyX-I authored
12 In |vim-addon-manager-additional-documentation.txt|:
13 3. Functionality provided |VAM-functionality|
14 3.1. Commands |VAM-commands|
15 3.2. Functions |VAM-functions|
16 4. Options |VAM-options|
17 6. Uninstalling plugins |VAM-uninstall-plugins|
18 7. Addon-info file |VAM-addon-info|
19 8. Author, credits, some notes |VAM-related|
20 9. Testing this plugin |VAM-testing|
21 10. Some notes for windows users |VAM-windows|
22 11. Some notes for Gentoo users |VAM-gentoo|
23 12. Troubleshooting and known bugs |VAM-trouble-shooting|
24 13. TODO notes |VAM-TODO|
25 14. VAM vs ... |VAM-comparison|
26 15. Tracking down errors |VAM-tracking-down-erros|
27 16. Making plugins work with VAM |VAM-adjusting-plugins|
ca3b3c9 @MarcWeber improve docs:
authored
28
29 ==============================================================================
30
31 0. GETTING STARTED & LOOKING FOR HELP - something doesn't work
32
33 Getting started fast: ~
34 Read: |VAM-installation| and |VAM-addon-names|
35
36
37 NEED HELP: ~
38 Join irc.freenode.net, /join #vim. Ask there. VAM has many users
39 MarcWeber is hanging around often so ping him or create a github ticket [1] and
40 people will try to help you. You should skim the docs before asking for
41 help though. Also see |VAM-author|
42 [1] https://github.com/MarcWeber/vim-addon-manager/issues
43
44 WHY VAM?: ~
45 - two maintainers (ZyX and Marc Weber)
46 - friendly to users (install addons by name)
ec13839 @Inkane Fixed minor typo
Inkane authored
47 - propagates collaborative coding by providing simple dependency managament
ca3b3c9 @MarcWeber improve docs:
authored
48 improving code sharing
d5aaf71 @ZyX-I Added notes about darcs to documentation
ZyX-I authored
49 - supports many sources (git, hg, bzr, svn, darcs, www.vim.org)
ca3b3c9 @MarcWeber improve docs:
authored
50 - provides a way to deprecate plugins which are superseded by others
51 - most plugins can also be loaded at runtime (some problems may [BUG 10])
52 - some Windows support
53 - is not too shy telling you that alternatives exist (and which one)
54 - copes with "subdirectories contain vim runtimepath" cases
55
56 ==============================================================================
57 1. Intro *VAM-intro*
58
59 VAM is a shortcut for vim-addon-manager. Its vision is: Make it easiest to
9219df8 @ZyX-I Improved documentation
ZyX-I authored
60 install plugin somewhat following the “20% of efforts yields 80% of value”
61 rule.
ca3b3c9 @MarcWeber improve docs:
authored
62 >
9219df8 @ZyX-I Improved documentation
ZyX-I authored
63 :h plugin
64 tells you about the old manual way of installing plugins. VAM helps keeping
65 ~/.vim clean by separating plugins from each other.
ca3b3c9 @MarcWeber improve docs:
authored
66
67 Features:
68 - Separate directories for each plugins
69 - Dependency resolution
70 - Popular VCS support: plugin supports fetching from Git, Mercurial,
d5aaf71 @ZyX-I Added notes about darcs to documentation
ZyX-I authored
71 Subversion, Bazaar and Darcs repositories
ca3b3c9 @MarcWeber improve docs:
authored
72 - maintained pool of addons (vim-addon-manager-known-repositories)
73 which warns you if you try to install an outdated plugin
d649c1f @MarcWeber now we can browse the pool online
authored
74 (have a look at it online : http://mawercer.de/~marc/vam/index.php)
ca3b3c9 @MarcWeber improve docs:
authored
75 - replicate your Vim setup by copying your .vimrc (See SetupVAM)
76 - load plugins lazily when Vim is already running. Some plugins require
77 additional tweaks for this to work
78
79 Dependencies:
80 - Curl, wget or other program that can output URL contents to stdout (in
81 order to get http protocol support)
d5aaf71 @ZyX-I Added notes about darcs to documentation
ZyX-I authored
82 - Git, Mercurial, Subversion, Bazaar and Darcs (if you want to install
83 plugins from appropriate repositories)
ca3b3c9 @MarcWeber improve docs:
authored
84 - Either tar, gzip and zip or 7-zip (required for unpacking some addons)
85
86 What does "Declarative package manager" mean? The final behaviour of Vim
87 should be declared once. Your ~/.vimrc and |:UpdateAddons| should be enough
88 to cause same Vim behaviour everywhere.
89
9219df8 @ZyX-I Improved documentation
ZyX-I authored
90 Note: “Addon” here is a synonym for “plugin”: “a related collection of files
91 enhancing vim functionality”. “Plugin” may also mean “a .vim file inside
92 a plugin directory” hence using “addon”.
ca3b3c9 @MarcWeber improve docs:
authored
93
94 ==============================================================================
95 2. Installation *VAM-installation*
96
97 Windows users: skim |VAM-windows|.
96f3202 @ZyX-I Modified “Installation” section:
ZyX-I authored
98 Gentoo users : skim |VAM-gentoo| which explains how to install VAM system-wide
99 from the layman overlay.
a1e2590 @MarcWeber add some more documentation about what the gentoo way is so that peop…
authored
100
96f3202 @ZyX-I Modified “Installation” section:
ZyX-I authored
101 Rest (linux and everything able to run POSIX shell) users should keep reading
102 here.
ca3b3c9 @MarcWeber improve docs:
authored
103
96f3202 @ZyX-I Modified “Installation” section:
ZyX-I authored
104 Minimal setup ~
ca3b3c9 @MarcWeber improve docs:
authored
105 This is the minimal setup which makes VAM work.
96f3202 @ZyX-I Modified “Installation” section:
ZyX-I authored
106 However you may want to use the longer commented version below because it
107 also fetches VAM so that copying your .vimrc is enough to replicate your
108 setup.
ca3b3c9 @MarcWeber improve docs:
authored
109
110 Add to your .vimrc >
96f3202 @ZyX-I Modified “Installation” section:
ZyX-I authored
111 set runtimepath+=PATH-TO-VAM
112 call vam#ActivateAddons([.. list of plugin names ..], {'auto_install' : 0})
ca3b3c9 @MarcWeber improve docs:
authored
113
114 recommended setup ~
96f3202 @ZyX-I Modified “Installation” section:
ZyX-I authored
115 1) Paste the following to your .vimrc.
116 2) Read the comments carefully. They help you getting started. Then you can
117 remove them.
118 3) Add addon names to the ActivateAddons call, start Vim. That’s all.
119 >
56a2cd3 @MarcWeber forgott to add argument to EnsureVamIsOnDisk function
authored
120 fun! EnsureVamIsOnDisk(vam_install_path)
96f3202 @ZyX-I Modified “Installation” section:
ZyX-I authored
121 " windows users may want to use http://mawercer.de/~marc/vam/index.php
ca3b3c9 @MarcWeber improve docs:
authored
122 " to fetch VAM, VAM-known-repositories and the listed plugins
96f3202 @ZyX-I Modified “Installation” section:
ZyX-I authored
123 " without having to install curl, 7-zip and git tools first
ca3b3c9 @MarcWeber improve docs:
authored
124 " -> BUG [4] (git-less installation)
919a9da @MarcWeber fix issue 75, by v0n
authored
125 let is_installed_c = "isdirectory(a:vam_install_path.'/vim-addon-manager/autoload')"
126 if eval(is_installed_c)
127 return 1
128 else
129 if 1 == confirm("Clone VAM into ".a:vam_install_path."?","&Y\n&N")
130 " I'm sorry having to add this reminder. Eventually it'll pay off.
131 call confirm("Remind yourself that most plugins ship with ".
132 \"documentation (README*, doc/*.txt). It is your ".
133 \"first source of knowledge. If you can't find ".
134 \"the info you're looking for in reasonable ".
135 \"time ask maintainers to improve documentation")
136 call mkdir(a:vam_install_path, 'p')
137 execute '!git clone --depth=1 git://github.com/MarcWeber/vim-addon-manager '.shellescape(a:vam_install_path, 1).'/vim-addon-manager'
138 " VAM runs helptags automatically when you install or update
139 " plugins
140 exec 'helptags '.fnameescape(a:vam_install_path.'/vim-addon-manager/doc')
141 endif
142 return eval(is_installed_c)
ca3b3c9 @MarcWeber improve docs:
authored
143 endif
144 endf
145
146 fun! SetupVAM()
147 " Set advanced options like this:
148 " let g:vim_addon_manager = {}
149 " let g:vim_addon_manager['key'] = value
96e3ab2 @MarcWeber fix: show addon info data for sources which are defined by dependenci…
authored
150 " Pipe all output into a buffer which gets written to disk
151 " let g:vim_addon_manager['log_to_buf'] =1
ca3b3c9 @MarcWeber improve docs:
authored
152
153 " Example: drop git sources unless git is in PATH. Same plugins can
154 " be installed from www.vim.org. Lookup MergeSources to get more control
155 " let g:vim_addon_manager['drop_git_sources'] = !executable('git')
236c85d @MarcWeber adding debug_activation option
authored
156 " let g:vim_addon_manager.debug_activation = 1
ca3b3c9 @MarcWeber improve docs:
authored
157
158 " VAM install location:
159 let vam_install_path = expand('$HOME') . '/.vim/vim-addons'
04ac1cd @ZyX-I Don’t use :echoe ever.
ZyX-I authored
160 if !EnsureVamIsOnDisk(vam_install_path)
5fee544 @ZyX-I Guess it was really meant not to break execution, thus no :throw
ZyX-I authored
161 echohl ErrorMsg
162 echomsg "No VAM found!"
163 echohl NONE
164 return
04ac1cd @ZyX-I Don’t use :echoe ever.
ZyX-I authored
165 endif
ca3b3c9 @MarcWeber improve docs:
authored
166 exec 'set runtimepath+='.vam_install_path.'/vim-addon-manager'
167
168 " Tell VAM which plugins to fetch & load:
169 call vam#ActivateAddons([], {'auto_install' : 0})
170 " sample: call vam#ActivateAddons(['pluginA','pluginB', ...], {'auto_install' : 0})
171
172 " Addons are put into vam_install_path/plugin-name directory
173 " unless those directories exist. Then they are activated.
174 " Activating means adding addon dirs to rtp and do some additional
175 " magic
176
177 " How to find addon names?
178 " - look up source from pool
179 " - (<c-x><c-p> complete plugin names):
180 " You can use name rewritings to point to sources:
181 " ..ActivateAddons(["github:foo", .. => github://foo/vim-addon-foo
182 " ..ActivateAddons(["github:user/repo", .. => github://user/repo
183 " Also see section "2.2. names of addons and addon sources" in VAM's documentation
184 endfun
185 call SetupVAM()
186 " experimental [E1]: load plugins lazily depending on filetype, See
187 " NOTES
188 " experimental [E2]: run after gui has been started (gvim) [3]
189 " option1: au VimEnter * call SetupVAM()
190 " option2: au GUIEnter * call SetupVAM()
191 " See BUGS sections below [*]
192 " Vim 7.0 users see BUGS section [3]
193
194
195
196 NOTES: ~
197 experimental: load plugins lazily depending on filetype [E1]~
198 >
199 let ft_addons = {
200 \ '^\%(c\|cpp\)$': [ 'plugin-for-c-development' ],
201 \ 'javascript': [ 'plugin-for-javascript' ]
202 \ }
203 au FileType * for l in values(filter(copy(ft_addons), string(expand('<amatch>')).' =~ v:key')) | call vam#ActivateAddons(l, {'force_loading_plugins_now':1}) | endfor
204 < Provide feedback about this. If it works we may add it as builtin
205
206 experimental: setup VAM when GUI has started [E2] ~
207 Depending on the option you choose to run ActivateAddons Vim may not be
208 able to show the questions correctly asking you to install a plugin.
209 If that's the case (for whatever reason) I recommend installing the plugin
210 using |:InstallAddons| or |:ActivateAddons| before adding it to the list in
211 .vimrc
212
213 If you're annoyed by the message: >
214 "Press enter to continue"
215 < There are at least two solutions you can try:
216
96f3202 @ZyX-I Modified “Installation” section:
ZyX-I authored
217 - press q once and Vim should stop asking
218 - set |VAM-auto_install| to 1 (to make VAM stop asking you questions before
219 installing anything)
220 , set |VAM-shell_commands_run_method| to "system" (to make VAM use
221 |system()| for running installation commands and thus avoid |hit-enter|
222 prompts)
223 and set 'nomore' before ActivateAddons call (to avoid |more-prompt|).
224
225
226 Example how to patch vcs checkout functions (eg if you're behind a proxy
227 and need to checkout github urls by http://): >
228 let g:vim_addon_manager = {'scms': {'git': {}}}
229 fun! MyGitCheckout(repository, targetDir)
230 let a:repository.url = substitute(a:repository.url, '^git://github', 'http://github', '')
231 return vam#utils#RunShell('git clone --depth=1 $.url $p', a:repository, a:targetDir)
232 endfun
233 let g:vim_addon_manager.scms.git.clone=['MyGitCheckout']
ca3b3c9 @MarcWeber improve docs:
authored
234 <
235
96f3202 @ZyX-I Modified “Installation” section:
ZyX-I authored
236 Another example: replace git_update and show changelog >
237 let g:vim_addon_manager = {'scms': {'git': {}}}
238 fun! MyGitUpdate(targetDir)
239 let cd = shellescape
240 let oldHash = vam#utils#System('git --git-dir=$p/.git rev-list HEAD -1', a:targetDir)
241 call vam#utils#RunShell('cd $p && git pull', a:targetDir)
242 let newHash = vam#utils#System('git --git-dir=$p/.git rev-list HEAD -1', a:targetDir)
243 if oldHash isnot# newHash
244 silent enew
245 setlocal buftype=nofile bufhidden=wipe
246 call setline(1, a:targetDir)
247 call append(1, split(system(vam#utils#ShellDSL('cd $; git log $[]..$[]', a:targetDir, oldHash, newHash)), "\n"))
248 endif
249 return 0
250 endfun
251 let g:vim_addon_manager.scms.git.update=['MyGitUpdate']
ca3b3c9 @MarcWeber improve docs:
authored
252 <
253
96f3202 @ZyX-I Modified “Installation” section:
ZyX-I authored
254 Startup benchmarking ~
255 Some non-precise benchmarking can be done by >
256 vim --startuptime startup.log -c q
257 < . Timings will be printed to startup.log file. You can do it more precisely
258 by using >
259 vim --cmd 'profile start profile.log' \
260 --cmd 'profile func *' \
261 --cmd 'profile file *' \
262 -c 'profile pause' \
263 -c 'qa!'
264 < Then it will output full profile information where time consumed by each
265 line is shown, with a summary of function call times at the end. You can
266 also get a summary of script file times if you open profile.log and do >
267 let timings=[]
268 g/^SCRIPT/call add(timings, [getline('.')[len('SCRIPT '):], matchstr(getline(line('.')+1), '^Sourced \zs\d\+')]+map(getline(line('.')+2, line('.')+3), 'matchstr(v:val, ''\d\+\.\d\+$'')'))
269 call setline('.', ['count total (s) self (s) script']+map(copy(timings), 'printf("%5u %9s %8s %s", v:val[1], v:val[2], v:val[3], v:val[0])'))
270 < . You can also get times of scripts activation if you run >
271 tlib#cmd#Time('call vam#ActivateAddons(["A"])')
272 < for plugins which were not already activated after vim has started.
273 Requires tlib. Adds time which takes VAM to do activation to actual
274 activation. For filetype, indent, syntax, compiler, colorscheme and
275 autoload plugins time spend in VAM is likely to exceed time used to load
276 plugin (because actual loading will take place later if required), so it is
277 better to read |profiling| instead.
ca3b3c9 @MarcWeber improve docs:
authored
278
279 ------------------------------------------------------------------------------
280 2.2 Names of addons and addon sources *VAM-addon-names*
281
34a420e @ZyX-I Some documentation improvements
ZyX-I authored
282 Because we are human VAM uses readable names as unique identifier for plugins.
283 Those identifieres (= plugin names) are passed to |vam#ActivateAddons()|,
284 |:InstallAddons|, |:ActivateAddons| . The name is automatically derived from
285 plugin titles at www.vim.org.
ca3b3c9 @MarcWeber improve docs:
authored
286
287 types of names:
379bee0 @ZyX-I Fixed command name.
ZyX-I authored
288 1) Plugin name looked up in pool. Try |:AddonsInfo| NAME
ca3b3c9 @MarcWeber improve docs:
authored
289
290 Determining addon names ~
34a420e @ZyX-I Some documentation improvements
ZyX-I authored
291 - From ID: |:AddonsInfo| SCRIPT_ID, pick the word right after string
292 "Plugin: ".
293 - Use |:InstallAddons|' name completion by typing some chars then pressing
294 <C-d> then <Tab>. |c_CTRL-D|
295 - Use <C-x><C-p> completion while editing your vimrc.
296 See |VAM-addon-completion_lhs| if you don’t like the lhs or the whole
297 idea.
298
299 2) Name which gets rewritten internally (see |VAM-name_rewriting|) >
ca3b3c9 @MarcWeber improve docs:
authored
300 github:{Name} => {"type": "git", "url": "git://github.com/{Name}/vim-addon-{Name}}
301 github:{N}/{Repo} => {"type": "git", "url": "git://github.com/{N}/{Repo}"}
302 git:{GIT_URL} => {"type": "git", "url": "GIT_URL"}
34a420e @ZyX-I Some documentation improvements
ZyX-I authored
303 < Don't use if you expect others to create plugins depending on yours. Add
ca3b3c9 @MarcWeber improve docs:
authored
304 your plugin to |VAM-kr| instead.
305
306
34a420e @ZyX-I Some documentation improvements
ZyX-I authored
307 Instead of telling us to add your plugin to |VAM-kr| you can also patch
308 the pool easily: |VAM-kr-patching| - however if you contribute to |VAM-kr|
309 the community will benefit much more.
ca3b3c9 @MarcWeber improve docs:
authored
310
311 *VAM-kr* is the default pool. VAM checks it out by default. Its long name is
312 *vim-addon-manager-known-repositories* (stored in |VAM-known| option).
313
314 *VAM-kr-patching*
315 VAM-kr merges both sources (scm and www.vim.org ones), see |VAM-MergeSources|.
316 The result is provided by vam_known_repositories#Pool() which is the only pool
34a420e @ZyX-I Some documentation improvements
ZyX-I authored
317 used by default. See example and default implementation of vam#install#Pool().
ca3b3c9 @MarcWeber improve docs:
authored
318
319 If you want to add your own soucres consider submitting them to
320 VAM-kr as patch. If you don't there are two ways:
321
322 WAY 1: (still supported) add to your .vimrc before activating VAM (BUG/TODO [5]): >
323 let g:vim_addon_manager = {}
324 let g:vim_addon_manager.plugin_sources = {}
325 let g:vim_addon_manager.plugin_sources['your_plugin_name'] = { plugin dictionary }
326 <
327 WAY 2: define your own Pool function: >
328 let g:vim_addon_manager = {}
329 let g:vim_addon_manager.pool_fun = function('MyPoolFun')
330 fun MyPoolFun()
331 let d = vam#install#Pool()
332 let d['my_plugin'] = { 'type' : 'git', 'url' : ' ... ' }
333 return d
334 endf
335
336 Plugin dictionaries are described in |addon-info-repository|.
337
338 Example: overwriting the MergeSources function (VAM-kr pool implementation): >
339 Yes, you can do this in MyPoolFun shown above as well >
34a420e @ZyX-I Some documentation improvements
ZyX-I authored
340 fun! MyMergeSources(plugin_sources, www_vim_org, scm_plugin_sources, patch_function, snr_to_name)
ca3b3c9 @MarcWeber improve docs:
authored
341
342 " run default:
343 call vam_known_repositories#MergeSources(a:plugin_sources, a:www_vim_org, a:scm_plugin_sources, a:patch_function, a:snr_to_name)
344
345 " patch sources the way you like. This example adds username and password
346 " for SVN repositories. As alternative you could overwrite git urls etc ..
347 for your_plugin in ['svn-driven-key1', ...]
348 let a:plugin_sources[your_plugin]['username'] = 'svn user'
349 let a:plugin_sources[your_plugin]['password'] = 'svn user'
350 endfor
351
352 let a:plugin_sources['your_plugin_name'] = { plugin dictionary }
353 endf
354 " tell VAM to use your MergeSources function:
355 let g:vim_addon_manager = {}
356 let g:vim_addon_manager['MergeSources'] = function('MyMergeSources')
357 <
358
359
360 ------------------------------------------------------------------------------
361 2.3 Example: configurable setup *VAM-complex-setup-sample*
362 >
363 call vam#ActivateAddons(["github:YOURNAME"],{'auto_install' : 0})
364 " this initializes Vim the way *you* want also loading more plugins:
365 call vim_addon_YOURNAME#Activate(['c-dev','ruby-dev'])
366 <
367 My implementation looks like this:
368 https://github.com/MarcWeber/vim-addon-MarcWeber/blob/master/autoload/vim_addon_MarcWeber.vim
369
370 You can then load plugins depending on env vars:
371 Example: >
372 call vim_addon_YOURNAME#Activate(['always']+split($V,','))
373 < Then you can run vim like this from shell >
374 V=c-dev,ruby-dev vim
375 <
376 This section was written to inspire you only.
377
378 ------------------------------------------------------------------------------
379 2.4 Unattended installation *VAM-unattended-installation*
380
381 Note: You should always review foreign code before running it. That said this
382 is how you can update or install unattended (without confirmations ..):
383
384 redir! > /tmp/log-vim.txt
385 silent! ACTION
386 messages
387
388 where ACTION is either UpdateActivatedAddons or vam#InstallAddons()
389
390 This works for http://mawercer.de/~marc/vam/index.php.
391
392 There is also the undocumented g:vim_addon_manager.dont_source option which
393 should be used if you want to checkout eventually untrusted code! If you're
394 going to use the plugins anyway its of no use.
a3f0e64 @rocksolidwebdesign Added documentation
rocksolidwebdesign authored
395
ca3b3c9 @MarcWeber improve docs:
authored
396 You may also want to set auto_install.
397
a1bc46a @MarcWeber document results from issue 77
authored
398 Also see https://github.com/MarcWeber/vim-addon-manager/issues/77:
399 >
400 let g:vim_addon_manager = {
401 \'shell_commands_run_method': 'system',
402 \'auto_install': 1,
403 \}
404 <
4ee69af @MarcWeber improving the patch by introducing a buffer to which vim will write t…
authored
405
a3f0e64 @rocksolidwebdesign Added documentation
rocksolidwebdesign authored
406 and possibly log_to_buf which will prevent you from having to deal with most
407 of those "hit enter to continue" prompts while VAM downloads plugins
408
409 Also see https://github.com/MarcWeber/vim-addon-manager/issues/79:
410 >
411 let g:vim_addon_manager = {
412 \'shell_commands_run_method': 'system',
413 \'auto_install': 1,
414 \'log_to_buf': 1,
415 \}
416 <
417
aa17a4f @ZyX-I Removed vam_ prefix from log_buffer_name option
ZyX-I authored
418 and if you wish, you may customize the default buffer name for the VAM log,
419 just use the log_buffer_name option which defaults to a value of
420 |VAM-plugin_root_dir|/VAM_LOG.txt e.g.
a3f0e64 @rocksolidwebdesign Added documentation
rocksolidwebdesign authored
421 ~/.vim/vim-addons/vim-addon-manager/VAM_LOG.txt
422 >
423 let g:vim_addon_manager = {
424 \'shell_commands_run_method': 'system',
425 \'auto_install': 1,
426 \'log_to_buf': 1,
aa17a4f @ZyX-I Removed vam_ prefix from log_buffer_name option
ZyX-I authored
427 \'log_buffer_name': '/tmp/vam_install.log',
a3f0e64 @rocksolidwebdesign Added documentation
rocksolidwebdesign authored
428 \}
429 <
4ee69af @MarcWeber improving the patch by introducing a buffer to which vim will write t…
authored
430
6d27796 @ZyX-I Section tags work fine no matter where these tags are located.
ZyX-I authored
431 vim: tw=78:ts=8:ft=help:norl
Something went wrong with that request. Please try again.