-
-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Invalid Event "User LspProgressStatusUpdated" #94
Comments
Hi @dreamerlzl , from #78 , can you update your statusline config follow below (add vim.api.nvim_create_augroup("lualine_augroup", { clear = true })
vim.api.nvim_create_autocmd("User", {
group = "lualine_augroup",
pattern = "LspProgressStatusUpdated",
callback = require("lualine").refresh,
}) |
That works like a charm. Thank you so much for the instant reply! |
Hi @Integralist, the reason is usually, the status message from lsp, cannot be correctly rendered in lualine. It's usually bacause of the If you can always reproduce this issue, please enable |
Yup I can reproduce every time 🙂 I'll provide the details you need tomorrow. Thanks 👍 |
@linrongbin16 here's the log... I'm not sure there's anything useful in it though 😬
|
hi @Integralist, yes it's useful. Neovim statusline will escape the So you can see, in the log, when we want to show But in this line:
You can see the line is truncated, and the last chars are I guess that's the exception. Are you specifying the |
I'm not setting that. What would you recommend I set that to? |
To clarify you can see my config here... https://github.com/Integralist/nvim/blob/main/lua/plugins/ui.lua |
hi @Integralist, would you please try branch |
@linrongbin16 yup that branch fixes things 🙂 |
I will merge it later, now I am not in front of my keyboard (I edit this PR with my phone). update: @Integralist , it's merged into main branch, please use main branch and try again. |
Rongbin, thank you for your work.
The Problem
Whenever I launch neovim, I will meet the following error:
Environment
The text was updated successfully, but these errors were encountered: