4 ms·

It's not a terminal though, so you can get GUI features that terminal nvim can't do. Personally I use terminal vim not any sort of nvim (maybe I should change

It's not a terminal though, so you can get GUI features that terminal nvim can't do. Personally I use terminal vim not any sort of nvim (maybe I should change over but then I potentially have to maintain two sets of plugins, one for nvim and one for vim. ). No if you want to call this out, I'd call it out for the lack of features. This only supports code completion in JS and TypeScript. I have code completion plus snippets for a lot more then that with vim. Honestly if you want to wow me, someone should build a GUI configuration tool for neovim/vim. One big benefit of GUIs is that you can generally see all the possible settings with tool tips and explanations, and I can see that being useful for vimmers, especially if it did the right thing, like using ft-plugins to do filetype specific settings, instead of a bunch of one line autogroups based on file extension. Yes there are vim config generators, but the neovim api means you could programmatically query the current configuration and display it along with the options, meaning you could have interactive configuration modification.

fmoralesc 9y ago
> This only supports code completion in JS and TypeScript. I have code completion plus snippets for a lot more then that with vim. No, this only supports the extended features fro completion for those languages. It should use the simpler completion system for other languages, in which case you are using vim's support anyway.
nerdponx 9y ago
I've been wanting to do exactly this for a long time, for exactly the reasons you state.
elkelk 9y ago
You'd be surprised, when I switched to nvim my plugins just worked.
cstrahan 9y ago
> maybe I should change over but then I potentially have to maintain two sets of plugins, one for nvim and one for vim I use this in my ~/.config/nvim/init.vim: set runtimepath^=~/.vim runtimepath+=~/.vim/after let &packpath = &runtimepath source ~/.vimrc That lets me directly use vim config from neovim. Then I set up an alias in my zsh profile: alias vim=nvim All of my plugins thus far have worked without a hitch (and I have a lot of configuration/plugins). If I ever run into problems, I can bail out by removing the alias (or for a one-off editing session, I can just run: $ command vim). You might give something like that a go.
- lsiebert 9y ago
  two plugins failed until I installed https://github.com/neovim/python-client https://github.com/neovim/python-client Which seems to have fixed things.

fmoralesc 9y ago

> This only supports code completion in JS and TypeScript. I have code completion plus snippets for a lot more then that with vim. No, this only supports the extended features fro completion for those languages. It should use the simpler completion system for other languages, in which case you are using vim's support anyway.

nerdponx 9y ago

I've been wanting to do exactly this for a long time, for exactly the reasons you state.

elkelk 9y ago

You'd be surprised, when I switched to nvim my plugins just worked.

cstrahan 9y ago

> maybe I should change over but then I potentially have to maintain two sets of plugins, one for nvim and one for vim I use this in my ~/.config/nvim/init.vim: set runtimepath^=~/.vim runtimepath+=~/.vim/after let &packpath = &runtimepath source ~/.vimrc That lets me directly use vim config from neovim. Then I set up an alias in my zsh profile: alias vim=nvim All of my plugins thus far have worked without a hitch (and I have a lot of configuration/plugins). If I ever run into problems, I can bail out by removing the alias (or for a one-off editing session, I can just run: $ command vim). You might give something like that a go.

lsiebert 9y ago
two plugins failed until I installed https://github.com/neovim/python-client https://github.com/neovim/python-client Which seems to have fixed things.