#Neobundle-Packages
Bringing vim packages to 2014 with the aid of NeoBundle
The goal of this project is to gather a list of jsons for installable packages in NeoBundle
Shougou has created a neobundle-vim-recipes repository which unifies NeoBundle recipes, but they are in a vim-format, and I want it to be JSON.
Also I recently read an article by Genki Sugimoto on the subject of using YAML recipes for NeoBundle. I loved this, but still want to use the common JSON format. Manage Vim Plugins the Beautiful Way using Yaml
Also - I want a format that could in the future be the database of vim plugins (similar to NPM which is my aspiration for this).
My main focus in creating JSON NeoBundle recipes is 2 things:
- An easy-parseable and modern format.
- Utilizing the lazy loading feature in NeoBundle, which is crucial when you have many installed plugins.
(I have 76 packages and that number is growing)
Notice: even though this plugin works, please be prepared for major API changes as this develops
- Get bundle path from NeoBundle (done)
- Add more packages to test performance
{
"name": "ctrlp",
"lazy": true,
"autoload": {
"commands": ["CtrlP", "CtrlPBuffer", "CtrlPMRU", "CtrlPMixed"]
},
"version": "",
"description": "",
"license": "",
"repository": "kien/ctrlp.vim",
"homepage": "https://github.com/kien/ctrlp.vim",
"bugs": "https://github.com/kien/ctrlp.vim/issues",
"author": {
"name": "",
"email": ""
},
"engines": {
"vim": ""
},
"keywords": [
"vim",
"search"
]
}
Suppose that there is a ctrlp.json
file that lies in the packages/
directory. You load it via:
call neobundle_packages#parse_bundle('ctrlp')
And that will load the ctrlp.vim
json package along side it's lazy loading instructions.
- A growing list of supported plugins
- A growing conventions that a plugin list database should be created (vim.org is kinda 1999)
- Support on the side of developers exporting their plugins using
(Plug)
orglobal commands
.
MIT © Gilad Peleg