3 ms·
I'm on neovim nightly and recently turned off treesitter. The highlighting is nice but it consistently was giving me segfaults while autocompleting, adds substa
by jpe90 5y ago
I'm on neovim nightly and recently turned off treesitter. The highlighting is nice but it consistently was giving me segfaults while autocompleting, adds substantially to my startup time, and renders the editor completely unresponsive when opening large files. I think it's worth mentioning it's still early in development before highly recommending it, but it's cool to tinker with if you're in the mood for it.
- phreeza 5y ago> renders the editor completely unresponsive I thought one of the points of neovim was to support true async stuff. So in theory, it should be possible to just open the file without syntax highlights but still be able to edit?
- OJFord 5y agoI'm not disagreeing with you (because I don't know the original 'points' of neovim and I've never used it) but plain vim now (as of v8 I think) supports 'async stuff'. I'm sure neovim has other benefits to some, but that alone at least I think is no longer one.
- bern4444 5y agoVim only supports async stuff because vim had to keep up with neovim which first introduced async support. I think vim's time is nearly over. Just as it replaced vi, neovim will replace vim. It may not get to the ubiquity of being installed everywhere by default, but certainly as the go to cli editor on devs' work and personal machines