nvim's 0.5.0 release includes a native lsp-client: nvim-lsp.
I have toyed with neovim for a while as a long time vim user and decided to make the ...
For further actions, you may consider blocking this person and/or reporting abuse
I'm testing this out as my "daily driver" for coding in rust. There are definitely some rough edges! I'll update with my improvements once I've smoothed things out :)
Hello, great article.
How did you install clippy (and in what OS)?
I mean, does
rustup component add clippy
actually (still) work for you?Never mind, the
rustup
package I installed had issues withclippy
.I've not heard of that before, the rustup team might be interested in your experience. Not sure where to feed that back exactly but a GitHub issue would be a good guess :)
github.com/rust-lang/rustup/issues
I'm just on Linux, Ubuntu.
Thank you for the reply.
Short story: I started installing
rustup
as package for the distro that I use (Solus) and it has issues ending with aclippy-driver
failure (everything else seems to work well).rustup
installed with thecurl
scripted works fine so far, actually.Hmm. I don't know why, but the autocompletion with nvim-lsp / deocomplete-lsp seems to be messed up for me.
I have a struct with a field "curr". In a function that takes an instance of that struct, I typed "self." and got the pop with its fields including "curr". When I selected that with
<C-n>
(same with (super)tab), it inserted an extra copy of the whole line, so I ended up withself. self.curr
instead ofself.curr
.Might have to go back to Neovim 0.4.3 and/or use autozimu's language client plugin again.
New to neovim (and vi variations in general). I'm definitely feeling a bit lost here. I'm now getting this error on startup:
And that's with my init.vim stripped down to only the lsp plugin
The closest I've found via google is a gitter message that notes "you have a borked install" and provides no further detail. Any help would be cool.
Nvm. I ended up building and installing the current HEAD from source. Pretty painless (instructions are on the neovim repo), definitely more successful for me than whacking archive contents somewhere on my path. The rest seemed to more or less work.
One quick easy win: add the autocommands to an augroup, and start it with
au!
to avoid duplication if you source your vim config while running. Probably obvious to vim veterans, but new and super useful for me.eg
In hindsight perhaps your target audience did not include new vim users, but some of these basics (i guess?) would be helpful for any of us considering a switch and coincidentally also working in Rust.
New rust user here, tempting to update nvim to 0.5.0 but don't want to break current functionality, are there any other ways pre 0.5.0? I use deoplete for python, c, c++.
Hi, I'm using 0.4.3 and I currently use
autozimu/LanguageClient-neovim
plugin. It already has direct integration with deoplete and can connect to any Language Server, for Rust you only needrls
installed and provide the server initialization command. You'll find the Rust setup in the repo readme.Thanks for the tip! I'll try that this weekend for sure. Saludos!