17 ms·

Neovim 0.8 Released

326 points by akrifari 4y ago

sigmonsays 4y ago
can't have a vim discussion without someone bringing up emacs
- jhoechtl 4y ago
  Emacs gas sub-par treesitter support and will go by default with eglot which is ok but nowhere as polished as the lsp experience in Neovim.
ajoseps 4y ago
I've tried using neovim for C++ dev but keep ending back in either vscode with intellisense or YCM on Vim. I don't know if I'm just misconfiguring things but I haven't been able to get autocomplete working correctly. Any tips?
- ckolkey 4y ago
  https://github.com/hrsh7th/nvim-cmp https://github.com/hrsh7th/nvim-cmp should be the ticket
- simjue 4y ago
  I've also tried using vim/neovim etc. several times but had the same problem. Recently I've tested lunarvim and autocomplete worked out of the box (with Go).
- addcninblue 4y ago
  You'll need to configure clangd or ccls correctly with neovim's lsp, which in turn requires your build chain to be clean. It's definitely a huge time sink. Feel free to email me if you have specific issues!
  - ativzzz 4y ago
    I was doing a school project in c++ and I tried configuring ccls but in the end I just gave up and did the project without LSP. Like you said it came with some prebuilt tooling and ccls did not feel particularly beginner friendly to get working as I am not familiar at all with the c++ toolchain. It (mostly) worked out of the box in another project with only some minor quirks though
NaN1352 4y ago
Any neovim based "gtk vim" app on linux? gVim is so slow for me, can literally see the window text redraw from top to bottom, where sublime text or vscode switching tabs or scrolling is near instantaneous.
- ckolkey 4y ago
  Something like https://neovide.dev/index.html https://neovide.dev/index.html ?
modernerd 4y ago
If you use Neovim, can you share why you chose it over VS Code, or one of the new terminal-based editors like https://helix-editor.com/ https://helix-editor.com/, or new native GUI editors like https://zed.dev/ https://zed.dev/ ? It's impressive to see what the Neovim community has built — preconfigured setups like https://nvchad.com/ https://nvchad.com/ are especially wild. But it still feels like a huge amount of work, hoop jumping, and _fragility_ just to reach parity with VS Code/Helix/Zed, which are pretty great out of the box, and which were built to be used as rich development environments instead of extensible text editors. I've spent months tweaking Neovim/Emacs configs in the past and I ultimately end up conceding that I'd rather spend that time hacking on projects instead of my editor config. I do feel the pull of these editors, though. I'd love to understand what those who stick with them are doing differently, other than perhaps being more susceptible to sunk cost fallacies. :-)
- ibotty 4y ago
  Because it's vim but better. I don't want an editor that uses, maybe, eighty megs and is constantly swapping!
- qbasic_forever 4y ago
  I don't need parity with VS code. If I want LSP and all kinds of distractions, binging and bonging, and crap jumping out and highlighting at me... I'll use VS code (don't get me wrong, sometimes those distractions are useful). Sometimes I need a terminal text editor. Something to quickly edit a config file, or perhaps even write something more substantial. Vim and Neovim are perfect and available on pretty much any machine which you'll have a terminal open to access.
  - deleted 4y ago
    [deleted]
- stoplying1 4y ago
  Helix is just very, very excellent. I've spent less than 5 minutes total configuring it and I really have virtually not a single complaint and there's WIP for the niceties that aren't present yet (sidebar/treeview, etc). I installed it, had some LSPs already on path. I configured it to show LSP messages and that was about it. It's very cool how gosh darn productive I can be, in such a short time due to the command palette built in. Seems like folks are taking note too. There's a few intro videos on YouTube that do a good job posted in the last few weeks; apparently some big Vim-guy streamer checked it out last week. Active Matrix room and constant code improvements. And native nix flakes support too ;) Btw, I find it a bit weird to include VsCode and Helix here together. Helix is perfectly usable as a Vim replacement for all basic text editing tasks, and a superior zero-config alternative in countless other scenarios.
zetaposter 4y ago
A text editor without a well rounded GUI story isn't worth it for me. There are all these desperate projects each with their own focus, ranging from "simple graphics acceleration" to "tons of bells and whistles, animations and ad-hoc UI extensions". UI should be thought out at PRs and issues, but the same people who develop the main core. But they don't have to, because they're making a terminal application, which has its use cases. But I so no reason why I should type my text in a terminal, when I can use a proper GUI application. And I'm not even suggesting VSCode, even Emacs is better in this regard, which is what I use.
- xwdv 4y ago
  The terminal is superior. You are just not skilled enough or advanced enough in thought to imagine what an interface can truly be.
  - sja 4y ago
    Is this a sarcastic remark? If not, this seems like an extremely reductive stance. Surely one could imagine another skilled person preferring a GUI over the terminal, even if it's not an opinion they share :)
    - xwdv 4y ago
      There is no sarcasm here. Zero.
  - SuperCuber 4y ago
    Your terminal application is an emulator of a decades old technology originally used in physical consoles, with layers upon layers of enhancements that add support for colors, cursor control, etc. At it's core, it's just a grid of characters. The GUI as a platform is quite literally a superset of the terminal, for example because the terminal emulator app is a GUI itself. Hacking the grid of characters to render lines as if it was a GUI is hardly "superior". I say all that as an avid neovim user myself by the way. On mac/linux I use it through the terminal, on Windows I use it through the QT application.
imbnwa 4y ago
Must every neovim release thread be brigaded by naysayers asking the same question for the 1000000th time? If you don't like its value proposition, don't use it. Simple. Keep using your IDE or whatever solution you prefer. This is almost exclusively happens in (neo)vim threads, and its so utterly distracting. That there is an entire community camped around neovim should answer your question about why anyone choses it over {insert non-vim solution}
- gnubison 4y ago
  But then what would we talk about? The update?
pacetherace 4y ago
I feel the proliferation of plugins has made the whole vim/neovim echo system too complicated and overwhelming to adapt for a new user. 1. Vim itself has a learning curve 2. There are many great plugins, but if they don't work for you, then unless you are an advanced user, it is impossible to get everything working without wasting a day 3. I find it weird that to get a vim plugin to work, I might have to install llvm and do a compilation and prey that all the dependencies have been satisfied
- mekster 4y ago
  What's bad is that while neovim tries to make vim much more functional with bunch if plugins, they barely stay stable. I don't know why but even if I install same plugins with same config on various machines of same Linux distro version, some just throw errors on every launch while others tend to work and it's getting to the point of annoyance to keep using it. It does feel like it's piling up parts hoping they don't fall apart. Using vs code with remote config does make it feel saner.
gillh 4y ago
We recently started providing standardized neovim centric dotfiles setup to developers at our startup and this setup has improved productivity quite a lot. Our neovim "distribution" is highly geared towards our tech stack (Golang etc.) and provides fzf based command palette. See: https://github.com/fluxninja/dotfiles https://github.com/fluxninja/dotfiles We aren't using neovim's built-in LSP as we found it to be a bit immature. Instead we are providing coc.nvim.
- deleted 4y ago
  [deleted]
andrewla 4y ago
I've been a Neovim user since inception -- I love the sane default configuration, the pruning away of old and obsolete "compatible" mode things, and the async and terminal support were killer features. When LSP support landed I was pretty firmly set. I hate Lua, though, and more and more of the neovim ecosystem is moving in that direction. And now that vim has caught up on the async and terminal and LSP support I'm finding it hard to justify staying on neovim, except for the burden of sane-ifying my configuration. VimL9 looks fantastic though -- VimScript has always been awkward but very domain-specific; VimL9 moves away from awkwardness but keeps the domain-specificity. Lua is not domain-specific enough, and the debugging and documentation are not good enough for me to pick it up in a pinch. I think it's likely that I'll be making the switch back to vim9 in the near future, although I'll probably give Kakoune a try again before committing.
psalminen 4y ago
I use vscode and neovim. Both have their benefits. Neovim is my main driver for reviewing/editing code. I have a few plugins and many personal functions/key bindings. Vscode is great for quick copy/paste text and their plugin ecosystem. Ie working with azure has been a dream with vscode.
legends2k 4y ago
Congrats on the release! Long live simple, non-proprietary, open editors which can be extended infinitely: Emacs & Vim (and their derivatives) FTW.
alwillis 4y ago
Just built it from source on a beta of macOS Ventura… everything went smoothly. These guys have done a great job.
CapricornNoble 4y ago
That's a LONG list of fixes & features. I'm fairly new to vim (using Neovim as an IDE to learn Rust) but I'm very tempted to pull and build this release.
dyingkneepad 4y ago
Neovim is one of those things that seem maybe cool, but I just can't find a reason to switch. Vim works just fine for me, I don't know what I would be getting by switching, and I'd probably waste some time porting my config and workflow to whatever the differences are (I'm a heavy user of :terminal).
- StevePerkins 4y ago
  I think the selling points are supposed to target plugin authors, and people who like to use a ton of plugins. However, I would imagine that well over 90% of Vim users don't use a single plugin. At all. They defined some look and feel defaults in a ".vimrc" file 10+ years ago, and never thought about it again. At least that's my user profile, anyway. So to me, the NeoVim story is mostly Internet drama, about some salty devs who didn't get their patches merged and have been publicly jihading ever since. It's not enough to merely use NeoVim, you have be angry about it.
- jasonpeacock 4y ago
  In additional to all the features that others mention, I chose to support the Neovim project. It's a more open alternative without a BDFL that is willing to move forward and modernize the editor, drop support for ancient platforms, and regularly release improvements. A big deal was splitting the editor engine from the interface so that it's embeddable in other editors.
- da4id 4y ago
  I tried moving to neovim from vim mainly to try Copilot.
- sgk284 4y ago
  Vim user for 15+ years here. Switched to neovim last December to try out Github's Copilot plugin (which only supported neovim), and it was basically a drop-in replacement for vim. And I haven't looked back. I'm also a heavy user of terminal though, and that was the one thing I spent extra time on, because there were subtle differences that I didn't like. If you give neovim a shot again, try this in your ~/.config/nvim/init.vim (aside: I do miss the simpler path of ~/.vimrc): " Neovim's default terminal mode bindings aren't great. " This makes them behave like vim's. tnoremap <Esc> <C-\><C-n><C-w> tnoremap <C-w> <C-\><C-n><C-w> "Always enter the terminal in insert mode autocmd BufWinEnter,WinEnter,BufEnter term://* startinsert autocmd TermOpen,TermEnter * startinsert command! -nargs=0 Terminal :vsplit | term This allows navigating across splits more seamlessly, and I like defaulting to insert mode whenever I move into a terminal. I also added the :Terminal command because I prefer them in a vsplit by default.
coinbasetwwa 4y ago
I still haven’t recovered from the last couple updates… I’ll probably be making the switch to VIM very soon.
- hyperpl 4y ago
  Hi could you please elaborate?
- ollien 4y ago
  Do you mind elaborating?
- kuratkull 4y ago
  You make it seem like some obvious things were recently broken/changed. I have used NeoVim for a couple of years, I haven't noticed any breaking changes. Please elaborate
renewiltord 4y ago
This is possibly my favourite kickstarted project. I use this every day and got far more than my contribution was worth. Quite happy. My latest thing is I use it with C-x C-e in the terminal and copilot.vim to get shell autocompletions!
hd4 4y ago
They added a msi installer since 0.6 so that's pretty cool
- g_delgado14 4y ago
  Dumb question; what's an msi installer?
  - freeCandy 4y ago
    The installer for Windows https://en.wikipedia.org/wiki/Windows_Installer https://en.wikipedia.org/wiki/Windows_Installer
BaculumMeumEst 4y ago
I really wish neovim could ship usable default colorscheme and round out its lsp support with autocompletion. Treesitter isn’t for me; it’s slower to open files and I have no idea how people make sense of so many different color groups. Still sticking with vanilla vim and CoC for the time being, they’re rock solid.
- yjftsjthsd-h 4y ago
  > usable default colorscheme What's wrong with the default colorscheme?
  - BaculumMeumEst 4y ago
    https://ibb.co/TR9sWj8 https://ibb.co/TR9sWj8
    - tmtvl 4y ago
      That looks pretty good, I don't know what the default colour scheme looks like, but if you are proposing this as an improvement I hope it gets in.
- thetic 4y ago
  This is planned for the next release: https://github.com/neovim/neovim/issues/14790 https://github.com/neovim/neovim/issues/14790
- deleted 4y ago
  [deleted]
- alwillis 4y ago
  Treesitter isn’t for me; it’s slower to open files I certainly haven’t experienced any slowness with opening files with Neovim with Treesitter. It certainly enables much better syntax highlighting, among other things [1]. If anything, it’s faster than the regex-based syntax highlighting that Vim traditionally used. CoC is a 3rd party LSP plugin that works with Vim and Neovim. [1]: https://neovim.io/doc/treesitter/ https://neovim.io/doc/treesitter/
sva_ 4y ago
Finally I can get off the dev branch (which has been extremely stable though)

Neovim 0.8 Released

326 points by akrifari 4y ago

sigmonsays 4y ago

can't have a vim discussion without someone bringing up emacs

jhoechtl 4y ago
Emacs gas sub-par treesitter support and will go by default with eglot which is ok but nowhere as polished as the lsp experience in Neovim.

ajoseps 4y ago

I've tried using neovim for C++ dev but keep ending back in either vscode with intellisense or YCM on Vim. I don't know if I'm just misconfiguring things but I haven't been able to get autocomplete working correctly. Any tips?

ckolkey 4y ago
https://github.com/hrsh7th/nvim-cmp https://github.com/hrsh7th/nvim-cmp should be the ticket
simjue 4y ago
I've also tried using vim/neovim etc. several times but had the same problem. Recently I've tested lunarvim and autocomplete worked out of the box (with Go).
addcninblue 4y ago
You'll need to configure clangd or ccls correctly with neovim's lsp, which in turn requires your build chain to be clean. It's definitely a huge time sink. Feel free to email me if you have specific issues!
- ativzzz 4y ago
  I was doing a school project in c++ and I tried configuring ccls but in the end I just gave up and did the project without LSP. Like you said it came with some prebuilt tooling and ccls did not feel particularly beginner friendly to get working as I am not familiar at all with the c++ toolchain. It (mostly) worked out of the box in another project with only some minor quirks though

NaN1352 4y ago

Any neovim based "gtk vim" app on linux? gVim is so slow for me, can literally see the window text redraw from top to bottom, where sublime text or vscode switching tabs or scrolling is near instantaneous.

ckolkey 4y ago
Something like https://neovide.dev/index.html https://neovide.dev/index.html ?

modernerd 4y ago

If you use Neovim, can you share why you chose it over VS Code, or one of the new terminal-based editors like https://helix-editor.com/ https://helix-editor.com/, or new native GUI editors like https://zed.dev/ https://zed.dev/ ? It's impressive to see what the Neovim community has built — preconfigured setups like https://nvchad.com/ https://nvchad.com/ are especially wild. But it still feels like a huge amount of work, hoop jumping, and _fragility_ just to reach parity with VS Code/Helix/Zed, which are pretty great out of the box, and which were built to be used as rich development environments instead of extensible text editors. I've spent months tweaking Neovim/Emacs configs in the past and I ultimately end up conceding that I'd rather spend that time hacking on projects instead of my editor config. I do feel the pull of these editors, though. I'd love to understand what those who stick with them are doing differently, other than perhaps being more susceptible to sunk cost fallacies. :-)

ibotty 4y ago
Because it's vim but better. I don't want an editor that uses, maybe, eighty megs and is constantly swapping!
qbasic_forever 4y ago
I don't need parity with VS code. If I want LSP and all kinds of distractions, binging and bonging, and crap jumping out and highlighting at me... I'll use VS code (don't get me wrong, sometimes those distractions are useful). Sometimes I need a terminal text editor. Something to quickly edit a config file, or perhaps even write something more substantial. Vim and Neovim are perfect and available on pretty much any machine which you'll have a terminal open to access.
- deleted 4y ago
  [deleted]
stoplying1 4y ago
Helix is just very, very excellent. I've spent less than 5 minutes total configuring it and I really have virtually not a single complaint and there's WIP for the niceties that aren't present yet (sidebar/treeview, etc). I installed it, had some LSPs already on path. I configured it to show LSP messages and that was about it. It's very cool how gosh darn productive I can be, in such a short time due to the command palette built in. Seems like folks are taking note too. There's a few intro videos on YouTube that do a good job posted in the last few weeks; apparently some big Vim-guy streamer checked it out last week. Active Matrix room and constant code improvements. And native nix flakes support too ;) Btw, I find it a bit weird to include VsCode and Helix here together. Helix is perfectly usable as a Vim replacement for all basic text editing tasks, and a superior zero-config alternative in countless other scenarios.

zetaposter 4y ago

A text editor without a well rounded GUI story isn't worth it for me. There are all these desperate projects each with their own focus, ranging from "simple graphics acceleration" to "tons of bells and whistles, animations and ad-hoc UI extensions". UI should be thought out at PRs and issues, but the same people who develop the main core. But they don't have to, because they're making a terminal application, which has its use cases. But I so no reason why I should type my text in a terminal, when I can use a proper GUI application. And I'm not even suggesting VSCode, even Emacs is better in this regard, which is what I use.

xwdv 4y ago
The terminal is superior. You are just not skilled enough or advanced enough in thought to imagine what an interface can truly be.
- sja 4y ago
  Is this a sarcastic remark? If not, this seems like an extremely reductive stance. Surely one could imagine another skilled person preferring a GUI over the terminal, even if it's not an opinion they share :)
  - xwdv 4y ago
    There is no sarcasm here. Zero.
- SuperCuber 4y ago
  Your terminal application is an emulator of a decades old technology originally used in physical consoles, with layers upon layers of enhancements that add support for colors, cursor control, etc. At it's core, it's just a grid of characters. The GUI as a platform is quite literally a superset of the terminal, for example because the terminal emulator app is a GUI itself. Hacking the grid of characters to render lines as if it was a GUI is hardly "superior". I say all that as an avid neovim user myself by the way. On mac/linux I use it through the terminal, on Windows I use it through the QT application.

imbnwa 4y ago

Must every neovim release thread be brigaded by naysayers asking the same question for the 1000000th time? If you don't like its value proposition, don't use it. Simple. Keep using your IDE or whatever solution you prefer. This is almost exclusively happens in (neo)vim threads, and its so utterly distracting. That there is an entire community camped around neovim should answer your question about why anyone choses it over {insert non-vim solution}

gnubison 4y ago
But then what would we talk about? The update?

pacetherace 4y ago

I feel the proliferation of plugins has made the whole vim/neovim echo system too complicated and overwhelming to adapt for a new user. 1. Vim itself has a learning curve 2. There are many great plugins, but if they don't work for you, then unless you are an advanced user, it is impossible to get everything working without wasting a day 3. I find it weird that to get a vim plugin to work, I might have to install llvm and do a compilation and prey that all the dependencies have been satisfied

mekster 4y ago
What's bad is that while neovim tries to make vim much more functional with bunch if plugins, they barely stay stable. I don't know why but even if I install same plugins with same config on various machines of same Linux distro version, some just throw errors on every launch while others tend to work and it's getting to the point of annoyance to keep using it. It does feel like it's piling up parts hoping they don't fall apart. Using vs code with remote config does make it feel saner.

gillh 4y ago

We recently started providing standardized neovim centric dotfiles setup to developers at our startup and this setup has improved productivity quite a lot. Our neovim "distribution" is highly geared towards our tech stack (Golang etc.) and provides fzf based command palette. See: https://github.com/fluxninja/dotfiles https://github.com/fluxninja/dotfiles We aren't using neovim's built-in LSP as we found it to be a bit immature. Instead we are providing coc.nvim.

deleted 4y ago
[deleted]

andrewla 4y ago

I've been a Neovim user since inception -- I love the sane default configuration, the pruning away of old and obsolete "compatible" mode things, and the async and terminal support were killer features. When LSP support landed I was pretty firmly set. I hate Lua, though, and more and more of the neovim ecosystem is moving in that direction. And now that vim has caught up on the async and terminal and LSP support I'm finding it hard to justify staying on neovim, except for the burden of sane-ifying my configuration. VimL9 looks fantastic though -- VimScript has always been awkward but very domain-specific; VimL9 moves away from awkwardness but keeps the domain-specificity. Lua is not domain-specific enough, and the debugging and documentation are not good enough for me to pick it up in a pinch. I think it's likely that I'll be making the switch back to vim9 in the near future, although I'll probably give Kakoune a try again before committing.

psalminen 4y ago

I use vscode and neovim. Both have their benefits. Neovim is my main driver for reviewing/editing code. I have a few plugins and many personal functions/key bindings. Vscode is great for quick copy/paste text and their plugin ecosystem. Ie working with azure has been a dream with vscode.

legends2k 4y ago

Congrats on the release! Long live simple, non-proprietary, open editors which can be extended infinitely: Emacs & Vim (and their derivatives) FTW.

alwillis 4y ago

Just built it from source on a beta of macOS Ventura… everything went smoothly. These guys have done a great job.

CapricornNoble 4y ago

That's a LONG list of fixes & features. I'm fairly new to vim (using Neovim as an IDE to learn Rust) but I'm very tempted to pull and build this release.

dyingkneepad 4y ago

Neovim is one of those things that seem maybe cool, but I just can't find a reason to switch. Vim works just fine for me, I don't know what I would be getting by switching, and I'd probably waste some time porting my config and workflow to whatever the differences are (I'm a heavy user of :terminal).

StevePerkins 4y ago
I think the selling points are supposed to target plugin authors, and people who like to use a ton of plugins. However, I would imagine that well over 90% of Vim users don't use a single plugin. At all. They defined some look and feel defaults in a ".vimrc" file 10+ years ago, and never thought about it again. At least that's my user profile, anyway. So to me, the NeoVim story is mostly Internet drama, about some salty devs who didn't get their patches merged and have been publicly jihading ever since. It's not enough to merely use NeoVim, you have be angry about it.
jasonpeacock 4y ago
In additional to all the features that others mention, I chose to support the Neovim project. It's a more open alternative without a BDFL that is willing to move forward and modernize the editor, drop support for ancient platforms, and regularly release improvements. A big deal was splitting the editor engine from the interface so that it's embeddable in other editors.
da4id 4y ago
I tried moving to neovim from vim mainly to try Copilot.
sgk284 4y ago
Vim user for 15+ years here. Switched to neovim last December to try out Github's Copilot plugin (which only supported neovim), and it was basically a drop-in replacement for vim. And I haven't looked back. I'm also a heavy user of terminal though, and that was the one thing I spent extra time on, because there were subtle differences that I didn't like. If you give neovim a shot again, try this in your ~/.config/nvim/init.vim (aside: I do miss the simpler path of ~/.vimrc): " Neovim's default terminal mode bindings aren't great. " This makes them behave like vim's. tnoremap <Esc> <C-\><C-n><C-w> tnoremap <C-w> <C-\><C-n><C-w> "Always enter the terminal in insert mode autocmd BufWinEnter,WinEnter,BufEnter term://* startinsert autocmd TermOpen,TermEnter * startinsert command! -nargs=0 Terminal :vsplit | term This allows navigating across splits more seamlessly, and I like defaulting to insert mode whenever I move into a terminal. I also added the :Terminal command because I prefer them in a vsplit by default.

coinbasetwwa 4y ago

I still haven’t recovered from the last couple updates… I’ll probably be making the switch to VIM very soon.

hyperpl 4y ago
Hi could you please elaborate?
ollien 4y ago
Do you mind elaborating?
kuratkull 4y ago
You make it seem like some obvious things were recently broken/changed. I have used NeoVim for a couple of years, I haven't noticed any breaking changes. Please elaborate

renewiltord 4y ago

This is possibly my favourite kickstarted project. I use this every day and got far more than my contribution was worth. Quite happy. My latest thing is I use it with C-x C-e in the terminal and copilot.vim to get shell autocompletions!

hd4 4y ago

They added a msi installer since 0.6 so that's pretty cool

g_delgado14 4y ago
Dumb question; what's an msi installer?
- freeCandy 4y ago
  The installer for Windows https://en.wikipedia.org/wiki/Windows_Installer https://en.wikipedia.org/wiki/Windows_Installer

BaculumMeumEst 4y ago

I really wish neovim could ship usable default colorscheme and round out its lsp support with autocompletion. Treesitter isn’t for me; it’s slower to open files and I have no idea how people make sense of so many different color groups. Still sticking with vanilla vim and CoC for the time being, they’re rock solid.

yjftsjthsd-h 4y ago
> usable default colorscheme What's wrong with the default colorscheme?
- BaculumMeumEst 4y ago
  https://ibb.co/TR9sWj8 https://ibb.co/TR9sWj8
  - tmtvl 4y ago
    That looks pretty good, I don't know what the default colour scheme looks like, but if you are proposing this as an improvement I hope it gets in.
thetic 4y ago
This is planned for the next release: https://github.com/neovim/neovim/issues/14790 https://github.com/neovim/neovim/issues/14790
deleted 4y ago
[deleted]
alwillis 4y ago
Treesitter isn’t for me; it’s slower to open files I certainly haven’t experienced any slowness with opening files with Neovim with Treesitter. It certainly enables much better syntax highlighting, among other things [1]. If anything, it’s faster than the regex-based syntax highlighting that Vim traditionally used. CoC is a 3rd party LSP plugin that works with Vim and Neovim. [1]: https://neovim.io/doc/treesitter/ https://neovim.io/doc/treesitter/

sva_ 4y ago

Finally I can get off the dev branch (which has been extremely stable though)