3 ms·

I highly recommend looking into Treesitter for anyone who wants to improve syntax highlighting. I know its supported today natively in neovim. Not sure about r

I highly recommend looking into Treesitter for anyone who wants to improve syntax highlighting. I know its supported today natively in neovim. Not sure about regular vim or other editors/ides. But its a massive improvement on the otherwise regex approach to syntax highlighting every editor takes.

divbzero 5y ago
This might be the push I need to finally make the switch to Neovim.
- nathias 5y ago
  make sure you use versions above 0.5
- OJFord 5y ago
  'All' of the (three or so?) neovim plugins I've come across wanting to use, and found Ah damn, 'neovim' in the name, work just fine in vanilla vim, FYI. I don't know how much (or if anything) a plugin has to do to support it, but there's some kind of python RPC thing that allows it. IME it's been install that once, and neovim plugins 'just work'. (But I have only found/tried ones that explicitly mention it.) (Edit, this: https://github.com/roxma/vim-hug-neovim-rpc https://github.com/roxma/vim-hug-neovim-rpc)
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 ago
    I'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 ago
      Vim 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

divbzero 5y ago

This might be the push I need to finally make the switch to Neovim.

nathias 5y ago
make sure you use versions above 0.5
OJFord 5y ago
'All' of the (three or so?) neovim plugins I've come across wanting to use, and found Ah damn, 'neovim' in the name, work just fine in vanilla vim, FYI. I don't know how much (or if anything) a plugin has to do to support it, but there's some kind of python RPC thing that allows it. IME it's been install that once, and neovim plugins 'just work'. (But I have only found/tried ones that explicitly mention it.) (Edit, this: https://github.com/roxma/vim-hug-neovim-rpc https://github.com/roxma/vim-hug-neovim-rpc)

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 ago
  I'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 ago
    Vim 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