On 10/18/2009 12:52 PM, Niels Heirbaut wrote: > Hi, > > [...] I made in my home tmp > directory the following directory structure: > > plugin/a.vim > > If I then open open a new GViM in the tmp directory, set the contents > to 'plugin/a.vim' and issue the command 'ggVG:MkVimball a' I get the > following error: '***vimball*** unable to read file<plugin/a.vim>', > although the file is there and the permissions on the file and > directory allow for reading them. I tried it with other plugins as > well but these gave me the same result. >
Vimballs use the 'runtimepath' variable by default. Since your files aren't beneath ~/.vim (or another directory in the 'runtimepath'), MkVimball isn't finding them. You can override the use of ~/.vim via the global variable g:vimball_home - see the Vimball help for details, but this worked for me in a quick test: :let g:vimball_home="/home/mike/tmp" with /home/mike/tmp/plugin/test.vim as the file, and with the following text in a buffer: plugin/test.vim and by visually selecting that line and executing :MkVimball testvimball. Michael Henry --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_use" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
