Running into some weird behavior with v3 #478
Unanswered
SchnozzleCat
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Playing with the new goodies in the update, and ran into some behavior that differs from how it previously worked.
This is primarily related to the LSP reference mode (e.g.
Trouble lsp_references
).If auto_refresh is on, it seems to re-fetch the references of the current cursor symbol every ~5 seconds, which is counterintuitive to my workflow, since I want to move through queried references without losing the current set.
If auto_refresh is off, I need to manually call
require("trouble").refresh()
, which isn't a huge deal, but I just want to understand if the refresh mechanism is supposed to behave in this way.Something else I noticed, is that the lsp reference window does not refresh if I hover over a symbol and call
Trouble lsp_references
again, it just keeps the old references. I either need to wait for the ~5 second interval of the auto-refresh, or manually callrefresh()
after requesting the references. Is this behavior intended? Previously IIRC it used to just refresh the window, which seems more intuitive to me.Something else that is strange, is if auto_refresh is off, and is then enabled in a running session with
require("trouble").toggle_refresh()
, something like a symbol window (e.g.Trouble symbols
) will auto-refresh, but the LSP window will lose the automatic refresh that happens every 5 seconds. This behavior is actually closer to what I would want (then I can manually refresh in my binding for LSP references), but that definitely seems inconsistent, at least with the auto_refresh setup setting, unless I am missing something.Trouble 3.1.0, as well as
915179759c9459b69faae90a38da6fc1ca6b90d7
had this behavior for me.Beta Was this translation helpful? Give feedback.
All reactions