Its time to change the naming of the commands - all should start by VAM ..

[MarcWeber]

https://github.com/gmarik/Vundle.vim/issues/241#issuecomment-34549179

This bug is related to https://bitbucket.org/vimcommunity/vim-pi/issue/91/

[ZyX-I]

I remember it being suggested earlier. Most likely not in an issue though.

Starting with “VAM” is not enough I think. I suggest naming also follow “VAM{action}{subject}”: i.e. VAMListAddons, VAMRunInstallHook, VAMActivateAddons (these are trivial), VAMActivateInstalled (no “Addons” suffix), VAMUpdateAddons, VAMUpdateActivated (no “Addons” suffix), VAMUninstallUnused (“Unused” and not “NotLoadedAddons”), VAMDescribeAddon (not “AddonsInfo”), VAMBisectAddons (reverse order), VAMRecordBad (not BADVAMBisect), VAMRecordGood (“OK” is a very poor choice for the opposite of “bad”. And unexpected: mercurial and git use good/bad pair; bzr uses yes/no (intention: they say bisect may be used to find features, thus bisect finds where “yes” changes to “no” or the opposite and words are rather neutral)).

[Shougo]

+1

[ZyX-I]

There is an alternative approach to naming convention I used in aurum: deduce such names so that commands can always be abbreviated with VAM prefix and one letter: VAMInstall, VAMActivate, VAMDescribe (note: do not use Plugin here. If we call plugins addons we must be consistent), VAMUpdate, VAMListActive, VAMRemoveNotLoaded, VAMBisect, VAMbad, VAMgood. Do not have good name for VAMActivateInstalled though. Previous approach is probably better as VAM* commands are not expected to be used too much, unlike aurum ones, so no need to reduce typing that much.

[MarcWeber]

Do we want to continue calling them addons? vim.sf.net calls them "scripts", vundle calls them "bundle", we call them addons, another way would be calling them "plugins". We could also call the command VAMGrep or VAMFind or VAMDisplay .. grepping comes close to what the command actually does

[ZyX-I]

Lets reserve :VAMGrep for something more like grepping (e.g. searching all plugin sources). About names: VAM is an abbreviation for Vim Addon Manager. You already have this term in the plugin name.

By the way, when speaking Russian I call them something that can be translated back as "addition": this is (and "addon") what my dictionary says how "дополнение" should be translated. I used to think "extension" is also one of the possible translations for this word.

11.02.14, 15:32, "Marc Weber" notifications@github.com":

Do we want to continue calling them addons? vim.sf.net calls them "scripts", vundle calls them "bundle", we call them addons, another way would be calling them "plugins". We could also call the command VAMGrep or VAMFind or VAMDisplay .. grepping comes close to what the command actually does — Reply to this email directly or view it on GitHub.

[MarcWeber]

And we have "package" - due to vim-pi. We should be descriptive enough so that people just understand without looking up.

[ZyX-I]

Plugin, not package. If you saw "package" somewhere please fix it or tell me.

11.02.14, 16:03, "Marc Weber" notifications@github.com":

And we have "package" - due to vim-pi. We should be descriptive enough so that people just understand without looking up. — Reply to this email directly or view it on GitHub.

[vivien]

IMHO sticking with Vim's vocabulary, i.e. scripts makes more sense.

[MarcWeber]

Excerpts from Vivien Didelot's message of Tue Feb 11 15:43:52 +0000 2014:

IMHO sticking with Vim's vocabulary, i.e. scripts makes more sense. Thus rename vim-pi to vim-si ?

I personally don't have additional goals right now. The important features are working - people know about the solution. README has been improved. It's time for me to shut up again. People don't miss anything

• people are happy. Not many people seem to be interested in vim-wiki.mawercer.de either - so its time to shift focus for a while

[ZyX-I]

VSM does not look as good. I also do not like the idea of rebranding much.

11.02.14, 19:43, "Vivien Didelot" notifications@github.com":

IMHO sticking with Vim's vocabulary, i.e. scripts makes more sense. — Reply to this email directly or view it on GitHub.