Closed rockyzhang24 closed 2 years ago
Please describe the reproduction of this issue step-by-step from pre-conditions.
Sure.
lua require "fidget".setup {}
in init.vim
lua
LSP server and enable it via nvim-lspconfig. For this step, just use lua
as an example because lua
LSP server needs longer time for initialization, so it will be easier to reproduce this issue.clever-f
. lua
file and then we can see that the progress of the lua
LSP server initialization is shown on the bottom right corner by fidget.nvim
.f
plus any char, then the issue will be appear. Thank you so much.
Also see https://github.com/j-hui/fidget.nvim/issues/68 please.
Is it possible to fix this bug @rhysd ? I have been using clever-f for a really long time and I cannot live without it ðŸ˜
This is an issue of fidget.nvim (which is being fixed in the reported issue), so you can close this one.
@wookayin Sure.
@wookayin Thank you for clarifying that.
Have been using
clever-f
for a really long time. Recently, I encounter an error that is shown belowI am using fidget.nvim to show the progress of LSP. I am not sure whether this issue is caused by
clever-f
orfidget.nvim
. It seems that this issue is related to https://github.com/neovim/neovim/issues/16278, i.e., the<expr>
+getchar()
thing.This issue happens during the initialization of the LSP servers. After the initialization, no issues.
Nvim version: NVIM v0.7.0-dev+1429-g8bdcd832a
Thank you very much.