4 ms·

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

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/
- BaculumMeumEst 4y ago
  Treesitter is slower to parse a file initially but quicker at handling incremental changes. You probably won’t notice unless you open a huge source file.
  - robenkleene 4y ago
    Never used Treesitter, but I'd assume all this happens async? I.e., does Neovim actually block text editing untill the parsing is finished or do you just see unstyled content until it finishes? (I'd just be surprised if anything new worked that way in 2022, let alone something built for async like Neovim.)
    - BaculumMeumEst 4y ago
      It blocks text editing until it finishes.

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/

BaculumMeumEst 4y ago
Treesitter is slower to parse a file initially but quicker at handling incremental changes. You probably won’t notice unless you open a huge source file.
- robenkleene 4y ago
  Never used Treesitter, but I'd assume all this happens async? I.e., does Neovim actually block text editing untill the parsing is finished or do you just see unstyled content until it finishes? (I'd just be surprised if anything new worked that way in 2022, let alone something built for async like Neovim.)
  - BaculumMeumEst 4y ago
    It blocks text editing until it finishes.