4 ms·

lots of stuff. but mainly: * ease of getting started. nvim is just vim, you can bring over your vim config and it'll just work. * integrated lsp. you could ha

lots of stuff. but mainly: * ease of getting started. nvim is just vim, you can bring over your vim config and it'll just work. * integrated lsp. you could have vscode like auto completion natively * tree-sitter. google it to believe it and much, much more

thiht 5y ago
> tree-sitter. google it to believe it After Googling I have no idea what it is, it's a parser but for what? Syntax highlighting? That doesn't seem so impressive
- e12e 5y ago
  https://tree-sitter.github.io/tree-sitter/ https://tree-sitter.github.io/tree-sitter/ Yes, but it enables many tools to cooperate on highlighting/"understanding" synntax.
njharman 5y ago
My vim config includes bunch of customization for bunch of plugins written in vimscript. Will that just work?
- kellyjprice 5y ago
  Probably. I have not had any problems switching between the two. It's meant to be a drop in replacement, but I'm not sure how perfect that is.
  - arp242 5y ago
    Compatibility was a goal at the start, but now it seems to be on a "best effort" basis at best. It's very much non-perfect because opening anything in neovim with my Vim config gives me a forest of errors and loads of things don't work, including some pretty basic stuff like expression mappings. See my other comment in this thread as well.
arp242 5y ago
> you can bring over your vim config and it'll just work. Except when it doesn't: $ nvim init.vim Error detected while processing /home/martin/.config/nvim/init.vim: line 44: E474: Invalid argument: completeopt=menuone,popuphidden,noselect line 50: E518: Unknown option: completepopup=highlight:Pmenu,border:off E824: Incompatible undo file: /home/martin/.cache/vim/undo/%home%martin%.config%nvim%init.vim Or when opening a Go file: $ nvim a.go Error detected while processing function edc#init[34]..<SNR>66_apply[40]..<SNR>66_save: line 8: E121: Undefined variable: v:none E116: Invalid arguments for function get E15: Invalid expression: get(b:edc_save, a:setting, v:none) isnot v:none Error detected while processing function edc#init[34]..<SNR>66_apply[32]..<SNR>66_save: line 8: E121: Undefined variable: v:none E116: Invalid arguments for function get E15: Invalid expression: get(b:edc_save, a:setting, v:none) isnot v:none Error detected while processing function edc#init[34]..<SNR>66_apply[2]..<SNR>66_save: line 8: E121: Undefined variable: v:none E116: Invalid arguments for function get E15: Invalid expression: get(b:edc_save, a:setting, v:none) isnot v:none Error detected while processing function edc#init[34]..<SNR>66_apply[14]..<SNR>66_save: line 8: E121: Undefined variable: v:none E116: Invalid arguments for function get E15: Invalid expression: get(b:edc_save, a:setting, v:none) isnot v:none Error detected while processing function gopher#go#set_build_package[11]..gopher#go#module: line 12: E117: Unknown function: chdir And they don't even always show properly on startup (just "press ENTER", need to use :messages). There's loads of incompatibilities; some behaviour is different as well. I can't get it to stop clearing the terminal on exit for example; my 'nnoremap <Leader>p "*p' mapping just inserts '"', my Control+space mapping doesn't work for whatever reason, for some reason a lot of stuff looks different even though it has the same colour scheme, quite a number of my custom functions/commands/mappings error out for various reasons, etc. etc. And not all of these are very complex either: <C-Space> is a simple expression map: inoremap <expr> <C-@> pumvisible() ? "\<C-n>" : "\<C-x>\<C-u>" – Pressing <C-x><C-u> works, but this doesn't(?) "You can bring over your vim config and it'll just work" might be true is you have a simple vimrc with a few basic ":set"s, but it breaks down very fast.
- humility 5y ago
  I stand corrected. Is your experience based on nvim v0.5?

thiht 5y ago

> tree-sitter. google it to believe it After Googling I have no idea what it is, it's a parser but for what? Syntax highlighting? That doesn't seem so impressive

e12e 5y ago
https://tree-sitter.github.io/tree-sitter/ https://tree-sitter.github.io/tree-sitter/ Yes, but it enables many tools to cooperate on highlighting/"understanding" synntax.

njharman 5y ago

My vim config includes bunch of customization for bunch of plugins written in vimscript. Will that just work?

kellyjprice 5y ago
Probably. I have not had any problems switching between the two. It's meant to be a drop in replacement, but I'm not sure how perfect that is.
- arp242 5y ago
  Compatibility was a goal at the start, but now it seems to be on a "best effort" basis at best. It's very much non-perfect because opening anything in neovim with my Vim config gives me a forest of errors and loads of things don't work, including some pretty basic stuff like expression mappings. See my other comment in this thread as well.

arp242 5y ago

> you can bring over your vim config and it'll just work. Except when it doesn't: $ nvim init.vim Error detected while processing /home/martin/.config/nvim/init.vim: line 44: E474: Invalid argument: completeopt=menuone,popuphidden,noselect line 50: E518: Unknown option: completepopup=highlight:Pmenu,border:off E824: Incompatible undo file: /home/martin/.cache/vim/undo/%home%martin%.config%nvim%init.vim Or when opening a Go file: $ nvim a.go Error detected while processing function edc#init[34]..<SNR>66_apply[40]..<SNR>66_save: line 8: E121: Undefined variable: v:none E116: Invalid arguments for function get E15: Invalid expression: get(b:edc_save, a:setting, v:none) isnot v:none Error detected while processing function edc#init[34]..<SNR>66_apply[32]..<SNR>66_save: line 8: E121: Undefined variable: v:none E116: Invalid arguments for function get E15: Invalid expression: get(b:edc_save, a:setting, v:none) isnot v:none Error detected while processing function edc#init[34]..<SNR>66_apply[2]..<SNR>66_save: line 8: E121: Undefined variable: v:none E116: Invalid arguments for function get E15: Invalid expression: get(b:edc_save, a:setting, v:none) isnot v:none Error detected while processing function edc#init[34]..<SNR>66_apply[14]..<SNR>66_save: line 8: E121: Undefined variable: v:none E116: Invalid arguments for function get E15: Invalid expression: get(b:edc_save, a:setting, v:none) isnot v:none Error detected while processing function gopher#go#set_build_package[11]..gopher#go#module: line 12: E117: Unknown function: chdir And they don't even always show properly on startup (just "press ENTER", need to use :messages). There's loads of incompatibilities; some behaviour is different as well. I can't get it to stop clearing the terminal on exit for example; my 'nnoremap <Leader>p "*p' mapping just inserts '"', my Control+space mapping doesn't work for whatever reason, for some reason a lot of stuff looks different even though it has the same colour scheme, quite a number of my custom functions/commands/mappings error out for various reasons, etc. etc. And not all of these are very complex either: <C-Space> is a simple expression map: inoremap <expr> <C-@> pumvisible() ? "\<C-n>" : "\<C-x>\<C-u>" – Pressing <C-x><C-u> works, but this doesn't(?) "You can bring over your vim config and it'll just work" might be true is you have a simple vimrc with a few basic ":set"s, but it breaks down very fast.

humility 5y ago
I stand corrected. Is your experience based on nvim v0.5?