Replies: 2 comments
-
|
I did a little bisecting and it seems to be something with |
Beta Was this translation helpful? Give feedback.
-
|
I don't really know, and I've never bothered to debug such problems, since it is wild west. C-g is a bit of the weak spots of Elisp imo. It can happen at arbitrary places, potentially leading to inconsistent state (asynchronous exceptions), but it can also be caught anywhere, leading to blocking. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
I'm running Emacs 31.0.50, and I have the most up-to-date versions of Vertico and Consult installed. This is something I noticed recently. I haven't yet been able to get down to a MRE yet, but I wanted to get some early feedback and/or help because this driving me nuts and I'm having a hard time debugging it myself.
When I do
consult-lineand then try to abort (with or without typing something) withC-g, sometimes it takes me multiple times to actually quit. When it doesn't work I see[Quit]appear for a second or two after the prompt, and I hear the bell sound. I can keep typing in the minibuffer after this happens and vertico/consult remain responsive. Eventually one of theC-g's will get through and I'll actually exit.Whenever I hit
C-](abort-recursive-edit) then I exit the interface immediately.What could be causing this? How would I go about debugging such a thing? I'll be trying to bisect my config down to a MRE eventually, but this seems to not happen immediately after startup and only manifests after a few minutes into my editing session, so it's going to be a massive pain to reliably trace down the bug.
Beta Was this translation helpful? Give feedback.
All reactions