Fork me on GitHub

After struggling with Neovim's 0.5beta buggy LSP client, I'm now using CoC which is much much much smoother. It's a shame that 0.5 is being held up and that to get better versions of the LSP client you'll have to upgrade your Neovim. I think it will probably hamper adoption.


So which version are you using now? I was never able to setup any vim lsp properly but I very much want it


I use neovim 0.4.4. There are some useful instructions here on how to setup the client (including a link to my repo of my vim config. I use CoC, clojure-lsp and conjure).


Thanks, I will check it out but now I am even more confused about where and how much the nvim version matter


anybody here mess with vim-lsp? I have some basics setup, and tried coc at one point as well, but had something going on with CoC that I just backed it out. Wondering if there is a nice reference vim-lsp setup config; if I hold out further for nvim 0.5 and try that instead; or just try CoC again…


I’m using neovim 0.5 prerelease via a vimr prerelease. But I’m not using treesitter or lsp from neovim. Instead I use CoC as a plug-in.


neovim 0.5 has been great


i am trying to get rid of coc in favour of native lsp support, haven’t had time to set it up (mostly using emacs these days..)


this is getting more and more complex


Not really @ashnur -- the native LSP client of 0.5 is opt-in. If you don't configure it, you get nothing, you can pretend it doesn't exist. Same as the treesitter support.


because i see lots of independent things that interact in a non-obvious manner, i used the word complex, what do you mean not really? there is no intertwining of multiple things?


Not as far as I can see. LSP is a feature in Neovim 0.5 which is basically a Lua api. It doesn't interact with anything else.


Treesitter is a different way to do some things such as highlighting and folding -- but it doesn't interact with LSP.


Both are disabled unless the user opt-ins in configuration.


you mean, it's simple, if i don't do anything? i can certainly agree with that analysis 🙂


What if the aim is not to not do anything, but to figure out the best possible way to enable and configure these features, that's not complex either?


The new features don't interact with each other 😉


But yes -- if you want to enable the new native features (at least the LSP) it's a lot of new configuration you now own.


Gotta run 🙂