GNU bug report logs - #11447
24.1.50; notifications-notify eats keystrokes

Previous Next

Package: emacs;

Reported by: Peter Münster <pmlists <at> free.fr>

Date: Thu, 10 May 2012 20:46:01 UTC

Severity: normal

Found in version 24.1.50

Done: Michael Albinus <michael.albinus <at> gmx.de>

Bug is archived. No further changes may be made.

Full log


Message #32 received at 11447-done <at> debbugs.gnu.org (full text, mbox):

From: Stefan Monnier <monnier <at> iro.umontreal.ca>
To: Michael Albinus <michael.albinus <at> gmx.de>
Cc: Peter Münster <pmlists <at> free.fr>,
	11447-done <at> debbugs.gnu.org
Subject: Re: bug#11447: 24.1.50; notifications-notify eats keystrokes
Date: Sun, 13 May 2012 09:14:24 -0400
>> (let ((seen ()))
>> (unwind-protect
>> (let ((event (read-event)))
>> (when (and event (not (ignore-errors (dbus-check-event event))))
>> (push event seen)))
>> (setq unread-command-events
>> (append unread-command-events (nreverse seen)))))

> Unfortunately, it doesn't work either. When unread-command-events is
> non-nil, read-event takes the events from there instead of reading them
> from the input streams.

You mean, if unread-command-events is already non-nil when entering
the loop?  Yes, I guess it's a problem.

> This happens after the first time a character has been read in the
> loop,

That shouldn't be the case unless *you* put that char (well, event) on
unread-command-events.

> I've committed my original patch (minus the read-event timeout). Bug is
> closed.

OK, thank you,


        Stefan




This bug report was last modified 13 years and 61 days ago.

Previous Next


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