Laurențiu Nicola

I've given up on keeping my NVim dotfiles and plugins up to date. Can you say if: - this only happens on the first use, or even later - if...

@winkee01 maybe that's `autoSetHints` from https://github.com/simrat39/rust-tools.nvim/#configuration, also check out the comment above it.

> Nope, I have LSP status in my statusbar. I'd trust `ps` more here, but okay. > How can I provide it? I honestly don't know. Most LSP clients will...

Ah, sorry, I was under the impression that the error message said `waiting for cargo metadata or cargo check` like in https://github.com/rust-lang/rust-analyzer/issues/12138. `content modified` means that the LSP request was...

CC https://github.com/neovim/neovim/issues/16900 The UI problem should be fixed in NVIM 0.7.0: https://github.com/neovim/neovim/releases/tag/v0.7.0.

Note that we've also worked around this in https://github.com/rust-lang/rust-analyzer/pull/12508. I don't know if it still happens during project load, but that's somewhat of a different situation anyway. That said, I...

Yeah, possibly (unless you were actually typing). I think some errors or failed requests during load are somewhat acceptable.

Hmm, it looks like the error shows up right from the start, but NVim never clears it?

Since maybe it's not obvious, `rust-analyzer` itself can already be configured to use a different target directory (e.g. by using `server.extraEnv`), but since #172 `cargo-compete` uses a different toolchain from...

Tokio will migrate to the version of the async traits that gets standardized, but until then it would be nice to support both, if possible.