4 ms·

Neovim 0.5 is awesome. It has native LSP support, Lua configuration support that it feels like true revolution over past versions. But, getting into optimal se

Neovim 0.5 is awesome. It has native LSP support, Lua configuration support that it feels like true revolution over past versions. But, getting into optimal setup in neovim/vim involves lot of configuration. Here is mine if you want to refer: https://github.com/varbhat/dotfiles/tree/main/dot_config/nvim https://github.com/varbhat/dotfiles/tree/main/dot_config/nvi...

jitl 5y ago
I’ve been meaning to convert my config to Lua. I haven’t tried out the official LSP support; I’ve been using coc.vim (https://github.com/neoclide/coc.nvim https://github.com/neoclide/coc.nvim) which supports most of the VSCode plug-in API. Have you tried both? Curious how 0.5’s LSP implementation works for Typescript. (My config is much simpler, a single vim script file: https://github.com/justjake/Dotfiles/blob/new/config/nvim/init.vim https://github.com/justjake/Dotfiles/blob/new/config/nvim/in...)
- varbhat 5y ago
  Official LSP is lightweight, much faster imo. You can try Typescript's tsserver with neovim-lsp .
  - maddyboo 5y ago
    I’m glad to hear that. I’d heard a lot of good things about coc.nvim so I recently switched to it from languageclient-neovim. I have to say I am not very impressed. I don’t care for the configuration format, it’s not as flexible as I’d like, I don’t like installing npm packages to configure language servers that I already have installed, and it just generally feels sloppy. I guess I’m going to need to break my LSP config yet again as I migrate over to the native client. Hopefully this is the last time…
    - lawn 5y ago
      That was my experience with coc as well. After getting over the initial configuration native LSP has been working great. Also, you can use telescope to search for LSD definitions, references etc.
afarrell 5y ago
I’ve found lunarvim to be another good config baseline: https://github.com/ChristianChiarulli/LunarVim https://github.com/ChristianChiarulli/LunarVim Explained here: https://youtu.be/Qm864kVxAss https://youtu.be/Qm864kVxAss
csomar 5y ago
> LSP support This one is quite underrated. Code highlighting, formatting, auto-completion and syntax checks. Doing that on old Vim was a time consuming task and usually something doesn't work, is missing or regularly breaks. Since I started using coc.vim with neovim, it's as good as VSCode.

jitl 5y ago

I’ve been meaning to convert my config to Lua. I haven’t tried out the official LSP support; I’ve been using coc.vim (https://github.com/neoclide/coc.nvim https://github.com/neoclide/coc.nvim) which supports most of the VSCode plug-in API. Have you tried both? Curious how 0.5’s LSP implementation works for Typescript. (My config is much simpler, a single vim script file: https://github.com/justjake/Dotfiles/blob/new/config/nvim/init.vim https://github.com/justjake/Dotfiles/blob/new/config/nvim/in...)

varbhat 5y ago
Official LSP is lightweight, much faster imo. You can try Typescript's tsserver with neovim-lsp .
- maddyboo 5y ago
  I’m glad to hear that. I’d heard a lot of good things about coc.nvim so I recently switched to it from languageclient-neovim. I have to say I am not very impressed. I don’t care for the configuration format, it’s not as flexible as I’d like, I don’t like installing npm packages to configure language servers that I already have installed, and it just generally feels sloppy. I guess I’m going to need to break my LSP config yet again as I migrate over to the native client. Hopefully this is the last time…
  - lawn 5y ago
    That was my experience with coc as well. After getting over the initial configuration native LSP has been working great. Also, you can use telescope to search for LSD definitions, references etc.

afarrell 5y ago

I’ve found lunarvim to be another good config baseline: https://github.com/ChristianChiarulli/LunarVim https://github.com/ChristianChiarulli/LunarVim Explained here: https://youtu.be/Qm864kVxAss https://youtu.be/Qm864kVxAss

csomar 5y ago

> LSP support This one is quite underrated. Code highlighting, formatting, auto-completion and syntax checks. Doing that on old Vim was a time consuming task and usually something doesn't work, is missing or regularly breaks. Since I started using coc.vim with neovim, it's as good as VSCode.