Hi, > > (You may want to remove ~/.theonevimlib_config afterwards) > > $ git clone git://mawercer.de/theonevimlib
I think the entry level would be much lower if there were an http interface to peek what is about to be expected. Github or similar providers would already provide such a web interface. > I like this part. The plugin only defines the functionality, it's up to > the user to bind this to keys. But how to avoid that the user has to > set up a dozen maps for every plugin he installs? We still need > defaults. IMHO plugin developers should provide a function that defines those maps with a user customizable prefix. This function could be called from some sort of after/vimrc.vim. In any case, such good practice (which had to be defined by Bram) should best be described in the vim help file. > > * no longer waste dev time rewriting the same stuff again and again. > > (such as template systems etc).. We should try to get all features > > into one "plugin" and enhance that. I think there is still enough > > which can be improved. > > Rewriting stuff can be much quicker than agreeing on "one way" and > putting everything into one. It depends. I beg to differ. IMHO vim would greatly benefit from some sort of grand unified template system because sooner or later people would start sharing templates. I actually think it would be best to integrate one template system that provides a certain feature set (at least those features I personally find useful ;-) into the standard vim library. Regards, Thomas. --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_use" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
