Re: Why Vimball archives are evil?

Hi,

Thanks for the feedback.

> colorpicker

Do you mean http://www.vim.org/scripts/script.php?script_id=3224

Since I don't have the python dependencies installed, I cannot test
it
but I don't see a reason why it shouldn't work when moving the vim
files
into a "plugin" subdirectory -- I'd assume this would have been
necessary with pathogen too?

> c-support

Do you refer to c.vim?
http://www.vim.org/scripts/script.php?script_id=213
it seems to me that the plugin has many filenames hardcoded and
assumes
that it is installed in either ~/vimfiles (windows) or ~/.vim on
other
systems.

> DrawIt

Works for me. You have to use the commands though when invoking it
for
the first time.

> fugitive

This won't work because the commands are defined programmatically.
You
can make it work by adding the following commands to vimrc:

call TPluginCommand('com! -nargs=* Git', 'vim-fugitive',
'fugitive')
call TPluginCommand('com! -nargs=* Gcd', 'vim-fugitive',
'fugitive')
call TPluginCommand('com! -nargs=* Glcd', 'vim-fugitive',
'fugitive')
call TPluginCommand('com! -nargs=* Gcommit', 'vim-fugitive',
'fugitive')
call TPluginCommand('com! -nargs=* Ggrep', 'vim-fugitive',
'fugitive')
call TPluginCommand('com! -nargs=* Glog', 'vim-fugitive',
'fugitive')
call TPluginCommand('com! -nargs=* Gedit', 'vim-fugitive',
'fugitive')
call TPluginCommand('com! -nargs=* Gsplit', 'vim-fugitive',
'fugitive')
call TPluginCommand('com! -nargs=* Gvsplit', 'vim-fugitive',
'fugitive')
call TPluginCommand('com! -nargs=* Gtabedit', 'vim-fugitive',
'fugitive')
call TPluginCommand('com! -nargs=* Gpedit', 'vim-fugitive',
'fugitive')
call TPluginCommand('com! -nargs=* Gread', 'vim-fugitive',
'fugitive')
call TPluginCommand('com! -nargs=* Gwrite', 'vim-fugitive',
'fugitive')
call TPluginCommand('com! -nargs=* Gdiff', 'vim-fugitive',
'fugitive')
call TPluginCommand('com! -nargs=* Gmove', 'vim-fugitive',
'fugitive')
call TPluginCommand('com! -nargs=* Gremove', 'vim-fugitive',
'fugitive')
call TPluginCommand('com! -nargs=* Gblame', 'vim-fugitive',
'fugitive')
call TPluginCommand('com! Gstatus', 'vim-fugitive', 'fugitive')
TPluginAfter \<vim-fugitive\> edit

But you're probably better off by simply loading it on startup:

TPlugin vim-fugitive

> manpageview

Works for me.

> repeat

I don't understand what it does.

> supertab

tplugin doesn't try to guess maps (with the exception of <plug>-type
maps). The user has to explicitely define maps that should load
plugins:

call TPluginMap('imap <tab>', 'supertab', 'supertab')

> surround

The same as above. Due to the complexity of the maps you're probably
better of with loading the plugin:

TPlugin vim-surround

Regards,
Tom

--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php