2008/12/3 Marc Weber <[EMAIL PROTECTED]>: > > On Wed, Dec 03, 2008 at 01:53:07PM +0000, A. S. Budden wrote: >> >> 2008/12/3 Marc Weber <[EMAIL PROTECTED]>: >> > http://github.com/MarcWeber/theonevimlib/tree/master >> [snip] >> > edit configuration file your editing config file >> > /home/marc/.theonevimlib_config >> [snip] >> >> I'm curious: why did you choose to keep the configuration separate to >> the vim configuration? > I don't see why you shouldn't be able to symlink ~/.theonevimlib_config > to another location so that you can track it wit svn as well? it's even > better. You can define a function which returns the list of > configuration files. So you decide where to store this setup. > For details see > http://github.com/MarcWeber/theonevimlib/tree/master/core/autoload/config.vim > option config.filesFunc. You can tweak it easily to merge project > specific setups as well. > > The main reason is: There are many vim users out there. And you'll meet > some which already have mapped <F5> to functionality X. So your plugin > wants to map <F5> as well? What to do now? Keep local patches (using > subversion?) > Force the other user to change his mapping? ... > That's why the separate configuration is the onlny way to go (IMHO).. > Wether it must look the way its done in the exapmle I don't know yet. > You can also use configuration option like this
Maybe I'm missing the point, but I still don't understand why this file can't be ~/.vim/theonevimlib_config rather than ~/.theonevimlib_config - this won't make any difference to other users as this file is only in MY configuration. Of course, if you can customise the location of this config file (as hinted to in your post with "You can define a function which returns the list of configuration files.") then my concerns are irrelevant... Al --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_use" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
