-
Notifications
You must be signed in to change notification settings - Fork 5
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
Ignore time that emacs is waiting for input (root cause: read-key-sequence
not advised)
#14
Comments
Hi, thanks for trying this out! This **should ** already be accounted for because any times that you're waiting for input in that way,
It's possible that those packages are using something different to delay for user input, in which case I need to advise and/or hook on those things. If you can try to make/confirm repro case with just |
evil uses
|
Ahhhhah, OK. Thanks for jumping in with the callstack @unhammer. Did you get this from the profile that was generated? Very nice. 💯 This doesn't have anything to do with evil being super fancy, which I feared. Rather that I didn't handle
And the callstack above shows that: there's an idle timer running inside So, the C level I'm going to update the title of this issue and then add a checklist in the next comment. |
read-key-sequence-vector
not advised)
read-key-sequence-vector
not advised)read-key-sequence
not advised)
|
Progress!
The native C callstacks that could call
Found 3 more functions that need to be advised; none of them are called from C code (except for one use in
|
I've tested this with direct calls to |
Fixes it for me, I can |
Fastest user feedback ever. <grin> |
Works for me too! Thank you for the quick fix. |
This is great and I can see this being super helpful, thank you!
I've noticed one issue so far that makes the log rather noisy:
If I'm using evil, for example, and I hit
d
, then wait before hittingd
again, I'll seeSimilarly if I'm using which-key and wait for which-key to appear, then I see:
The text was updated successfully, but these errors were encountered: