| Newsgroups |
gmane.emacs.help |
| Message-ID |
<[email protected]> |
On 2026-03-02, at 15:03, Eli Zaretskii <[email protected]> wrote:
>> Ok, sorry to still bother you, but why wouldn't it work?
>
> Because what exactly restarts the idle time is elusive, hard to
> explain with 110% accuracy, and might vary between systems.
I see. So, basically this means that the fact that my "solution" worked
might have been a lucky coincidence.
>> It seems robust for me, since it simulates the user doing something
>> (admittedly, a "nil" something), and I performed a few tests
>> (admittedly, not very extensive), and it seemed to work every
>> time...
>
> Why do you think that setting unread-command-events has any influence
> on Emacs idleness? There was no input event, so we (the Emacs
> maintainers) could decide that doing so has no effect on idleness.
I thought (some part of) Emacs treats it as a signal "user did
something", and (another part of) Emacs noticed "ah, it is nil, so
nothing to do" - but the first part already reset the idle time.
Anyway, the bottom line is clear - relying on setting
`unread-command-events' is a bad idea.
Thank you for your time!
--
Marcin Borkowski
https://mbork.pl