GNU bug report logs - #31692
aggressive-indent-mode causes Emacs to sometimes drop key events

Previous Next

Full log

View this message in rfc822 format

From: Eli Zaretskii <eliz <at> gnu.org>
To: Michael Heerdegen <michael_heerdegen <at> web.de>
Cc: radon.neon <at> gmail.com, 31692 <at> debbugs.gnu.org
Subject: bug#31692: Emacs sometimes drops key events
Date: Wed, 06 Jun 2018 17:52:30 +0300

> From: Michael Heerdegen <michael_heerdegen <at> web.de>
> Cc: radon.neon <at> gmail.com,  31692 <at> debbugs.gnu.org
> Date: Wed, 06 Jun 2018 04:58:31 +0200
> 
> Eli Zaretskii <eliz <at> gnu.org> writes:
> 
> > Does it produce the character you type, though?  Because if it
> > doesn't, then whether or not you see "Quit" doesn't matter much, IMO,
> > at least not for the main issue at hand.
> 
> Hmm, right, it doesn't.
> 
> But I do not only see the issue in the aggressive-indent-mode, but also
> an issue in Emacs...you don't?

Not necessarily.  The forms of the body are aborted, as documented,
and that includes discarding all input, so the character that
interrupted while-no-input gets discarded as well.

> For `aggressive-indent-mode' - I think they should use an idle timer:
> Add something to `post-command-hook' that activates the timer, or resets
> the idle time when the timer is already there.  When the timer fires,
> you don't need `sit-for' - and the problem only occurs when
> `while-no-input' and `sit-for' are combined.  The timer just calls the
> aggressive indent function wrapped in `while-no-input'.

I actually don't understand why not use just sit-for.  Why is
while-no-input needed on top of that?

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.