4 ms·
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
by 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 agoOfficial LSP is lightweight, much faster imo. You can try Typescript's tsserver with neovim-lsp .
- maddyboo 5y agoI’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 agoThat 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.