-
-
Notifications
You must be signed in to change notification settings - Fork 117
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
HUD opened after client initialisatoin closes immidiately #641
Comments
Interesting looking at neovim core doesn't appear, at least by a superficial search through commits, that |
Hm, even weirder. Then maybe another plugin or some other part of my Neovim configuration is now triggering it earlier than expected. |
Tried Neovim 0.9 and 0.10, same issue. |
I cannot reproduce this. If I open a file, either python or clojure, the HUD stay open until I move the cursor. |
Oh! I'm not sure what's worse. I wonder if this could even be somehow related to #639. |
Seems like a timing related thing because I think I only see this on my laptop, not my desktop but I'll confirm that tomorrow. |
Maybe https://neovim.io/doc/user/autocmd.html#autocmd-disable will be helpful here, so while the log gets set up we can't trigger the passive close from cursor moved. |
Checked this out on my full PC (which is pretty darn fast) and I see the HUD pop up then vanish, so seems like it's consistent on both of my machines! There's definitely some new behaviour in Neovim or Conjure that is causing a cursormoved event when it wasn't in the past. How odd! |
I've raised the minimum lifetime for the HUD to 250ms by default. This should mitigate this issue. I do think something must have changed in Neovim around 0.8-0.10 though, I don't think I had issues with CursorMoved firing this much in the past. |
So when I open up a Clojure file it opens the HUD to show me the connection going through to the REPL.
This used to stay open until I moved my cursor but now it's closing immediately. I've narrowed it down to the
CursorMoved
event firing after Neovim opens and the HUD / log is created for the first time. This event is set up to passively close the HUD by callinglog.close-hud-passive
.This didn't work like this in the past so I suspect the event has changed behaviour between Neovim versions.
The text was updated successfully, but these errors were encountered: