Build and use neovim files

[neovim]

Build and use neovim files

[wellle]

That sounds like a good idea to reduce the friction of trying neovim without breaking the current vim setup.

In the meantime you could use an alias like this

alias neovim='/usr/bin/neovim -u ~/.neovimrc'

and put this in your ~/.neovimrc:

set nocompatible
set runtimepath=~/.neovim/

I use a similar setup to have a stock installation where I can test vim plugins independently from my vim setup.

[ashleyh]

Agreed

[tarruda]

I agree with this. Can someone send a PR?

[wellle]

Will do.

[enehring]

This might be beyond the scope of the issue opened, but I know there is somewhat of a push (at least in the linux circle) to move config files to ~/.config/ instead of just populating $HOME with lots of dotfiles.

So instead of having ~/.neovim/ and ~/.neovimrc, what if config files were looked for in ~/.config/neovim/ and ~/.config/neovimrc (or even ~/.config/neovim/neovimrc)?

I know this goes against the conventions that vim has established, but I figure:
a.) It helps keep the home directory less cluttered and
b.) If people don't like the behavior, changing it is just a symlink away. Neovim could even make the symlinks itself as a "legacy" option.

What does everyone think?

[Soares]

+1 to ~/.config. At the least, vim should respect $XDG_CONFIG_HOME and friends on systems which implement the XDG spec.

[tbelaire]

I'm not opposed to using the .config directory if we're already going to be moving the configs.

[sbeckeriv]

Some goals I had in mind are :

1. Its easy to create a new setup to test
2. Its easy to create a new environment to develop in
3. Easy to config conventions

The config directory would achieve my goal of not messing with my vim configs.

I didn't want to suggest permanently moving the files or change the values. I want to help support the project and I think this will be slightly easier for me if neovim lived in a sandbox from my vim. I know about the configs now, however, low friction helps the cause.

Research:
XDG https://groups.google.com/forum/#!topic/vim_dev/zBSo5Xnno9Q

[tbelaire]

Would we have a .vim directory inside config? I'm a bit fuzzy on what we
are planning.

Will things like Vundle continue to work?
If so, then everything is great.

On Sat, Feb 22, 2014 at 5:11 PM, Stephen Becker IV <[email protected]

wrote:

Some goals I had in mind are :

1. Its easy to create a new setup to test
2. Its easy to create a new environment to develop in
3. Easy to config conventions

The config directory would achieve my goal of not messing with my vim
configs.

I didn't want to suggest permanently moving the files or change the
values. I want to help support the project and I think this will be
slightly easier for me if neovim lived in a sandbox from my vim. I know
about the configs now, however, low friction helps the cause.

Research:
XDG https://groups.google.com/forum/#!topic/vim_dev/zBSo5Xnno9Q

Reply to this email directly or view it on GitHubhttps://github.com//issues/26#issuecomment-35820645
.

[sbeckeriv]

Vundle looks like it will work from a quick search of the code.

Given runtimepath can set any path everything should work.

[tarruda]

Closed by #44