Ecosyste.ms: Awesome

An open API service indexing awesome lists of open source software.

Awesome Lists | Featured Topics | Projects

https://github.com/pgilad/neobundle-packages

Neobundle list of packages in json format
https://github.com/pgilad/neobundle-packages

neobundle neobundle-packages vim vim-plugins vim-script

Last synced: 3 months ago
JSON representation

Neobundle list of packages in json format

Host: GitHub
URL: https://github.com/pgilad/neobundle-packages
Owner: pgilad
Created: 2014-03-14T21:16:38.000Z (almost 11 years ago)
Default Branch: master
Last Pushed: 2019-02-13T09:29:17.000Z (almost 6 years ago)
Last Synced: 2024-10-04T19:43:26.850Z (4 months ago)
Topics: neobundle, neobundle-packages, vim, vim-plugins, vim-script
Language: Vim script
Size: 7.81 KB
Stars: 6
Watchers: 4
Forks: 1
Open Issues: 0
Metadata Files:
- Readme: README.md

Awesome Lists containing this project

README

#Neobundle-Packages
> Bringing vim packages to 2014 with the aid of NeoBundle

## Goal

The goal of this project is to gather a list of jsons for installable packages in [NeoBundle](https://github.com/Shougo/neobundle.vim)

**Shougou** has created a [neobundle-vim-recipes](https://github.com/Shougo/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](http://genkisugimoto.com/blog/manage-vim-plugins-via-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:
1. An easy-parseable and modern format.
2. 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**

## Immediate Goals

- Get bundle path from NeoBundle (**done**)
- Add more packages to test performance

## Sample ctrlp.json

```json
{
"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"
]
}
```

## Usages

#### Loading a package from a known json package:

Suppose that there is a `ctrlp.json` file that lies in the `packages/` directory. You load it via:
```vim
call neobundle_packages#parse_bundle('ctrlp')
```

And that will load the `ctrlp.vim` json package along side it's lazy loading instructions.

## Future

- 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)` or `global commands`.

## License