On Jan 10, 7:08 pm, Marc Weber wrote: > > Thank you for you feedback. > I tried improving the documentation now.
Ok, it looks a little bit better...but I insist that it can be even simpler: in the "add to .vimrc" section I think you should only mention the runtimepath setting and say "that's it!". Afterwards, mention how to activate plugins...I still don't understand what "name1", "name2" means (ok I do, but it's weird...it looks like I should be able to cut&paste the lines in the help file, but that currently would not work [unless there is are plugins called "name1" and "name2"]). > About README: There is one catch: > If all plugins contain a README you can't install them into .vim without > causing conflicts. Tim Pope told me about this. That's why I removed the > README. But maybe I should readd it because getting started is more > important. I see...that is kind of unfortunate. However, following your instructions the addon-manager plugin should go into its own folder anyway so it's not really that much of a problem then, I guess. > > Is there any way to get information on a plugin? I mean, I can get a > > whole list of names with > > ActivateAddons <c-d> > > but that isn't very helpful. > > You made me feel lucky. This shows that you managed to install the > plugin and that you like it. You like it because it let's you getting > things done faster than usingwww.vim.org. That was one of my primary > goals. And now you want to have the features whichwww.vim.orgprovides. > > How should this look like? > May I assist you implementing the missing feature? > Reimplementing thehttp://www.vim.org/search.phpdoesn't make much > sense. That's why I stopped thinking about it. Sorry, I don't really have any good ideas...but at least some minimal information such as one line (a title) stating what the plugin is for and a URL (pointing to vim.org most likely) where you could get more info could be useful. I'm thinking of something like what MacPorts does for you (ok, you don't run OS X so you probably won't know what I'm talking about but I don't know any equivalent in the Linux world). Anyway, I ran into some problems trying to install the LustyExplorer plugin: Error detected while processing function scriptmanager#Activate..scriptmanager#ActivateRecursively..scriptmanager#Install..scriptmanager#Checkout: line 43: E605: Exception not caught: don't know how to checkout source location: {'version': '2.1.1', 'url': 'http://www.vim.org/scripts/ download_script.php?src_id=11526', 'vim_version': '7.0', 'date': '2009-10-13', 'vim_script_nr': 1890, 'type': 'archive', 'script-type': 'utility', 'archive_name': 'lusty-explorer.vim'} Error detected while processing function scriptmanager#Activate..scriptmanager#ActivateRecursively..scriptmanager#Install: line 18: E171: Missing :endif Error detected while processing function scriptmanager#Activate..scriptmanager#ActivateRecursively: line 10: E171: Missing :endif I'm not sure what this means? Is it not possible to install plain .vim scripts perhaps? Björn
-- You received this message from the "vim_use" maillist. For more information, visit http://www.vim.org/maillist.php
