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

Previous Next

Package: emacs;

Reported by: Radon Rosborough <radon.neon <at> gmail.com>

Date: Sun, 3 Jun 2018 02:23:02 UTC

Severity: normal

Done: Eli Zaretskii <eliz <at> gnu.org>

Bug is archived. No further changes may be made.

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:45:16 +0300
> From: Michael Heerdegen <michael_heerdegen <at> web.de>
> Cc: Radon Rosborough <radon.neon <at> gmail.com>,  31692 <at> debbugs.gnu.org
> Date: Tue, 05 Jun 2018 23:40:55 +0200
> 
> AFAIU, this quit-like effect should be limited to `while-no-input' and
> not be propagated to top-level.

I don't think I understand what you mean by "not propagated".  The
documentation says that if input arrives, the forms in the body of
while-no-input are _aborted_ as if by interrupt.

> I also read the documentation of the
> low-level tools with which this is implemented - `throw-input' and
> `quit-flag', and that also gives me the impression that generating a
> "quit" signal is not intended (that would also be not very useful).  We
> only want a quit to come through when the user really quits (C-g) -
> that's while `while-no-input' (which uses `with-local-quit' that sets
> `quit-flag') explicitly quit - but only when a quit had been
> intercepted.

But in your case while-no-input was the top-level form, no?  So where
else can a quit throw?




This bug report was last modified 7 years and 19 days ago.

Previous Next


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