Skip to content
This repository has been archived by the owner on Nov 10, 2020. It is now read-only.

support for neovim #65

Open
bitboxer opened this issue Apr 8, 2015 · 6 comments
Open

support for neovim #65

bitboxer opened this issue Apr 8, 2015 · 6 comments

Comments

@bitboxer
Copy link
Collaborator

bitboxer commented Apr 8, 2015

I am using vundle in my neovim and need to make the vundle thing to start neovim, not vim to update everything. What would you think is the best approach here?

@moonglum
Copy link
Owner

moonglum commented Apr 9, 2015

Sorry, I don't get this entirely. In Neovim, you are still using vundle, right? So the only difference would be that you invoke neovim +BundleInstall\! +qall instead of vim +BundleInstall\! +qall?

@bitboxer
Copy link
Collaborator Author

bitboxer commented Apr 9, 2015

Yep.

@moonglum
Copy link
Owner

moonglum commented Apr 9, 2015

Where do we need to install the Vundle package? Because currently it installs to .vim/bundles. Does it need to go to .nvim/bundles instead?

@bitboxer
Copy link
Collaborator Author

bitboxer commented Apr 9, 2015

It depends on your configuration of neovim 😉 .

@moonglum
Copy link
Owner

moonglum commented Apr 9, 2015

Oh, ok. So I would tend to say that this should be part of the package.yml then. Something where I can say:

vim: nvim
vim_home: ~/.vim

What do you think? Can we make that a part of the vundle configuration?

@bitboxer
Copy link
Collaborator Author

Yes, that sounds good!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants