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

Previous Next

Full log

Message #20 received at 11447 <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 <at> debbugs.gnu.org
Subject: Re: bug#11447: 24.1.50; notifications-notify eats keystrokes
Date: Fri, 11 May 2012 11:20:22 -0400

>>> (with-timeout ((if timeout (/ timeout 1000.0) 25))
>>> (while (eq (gethash key dbus-return-values-table :ignore) :ignore)
>>> ! 	(let ((event (let (unread-command-events) (read-event nil nil 0.1))))
>>> ! 	  (when (and event (not (ignore-errors (dbus-check-event event))))
>>> ! 	    (setq unread-command-events
>>> ! 		  (append unread-command-events (list event)))))))
>> 
>> Shouldn't this code use input-pending-p instead?

> Maybe, but I don't know how. I've tried this:

>     (with-timeout ((if timeout (/ timeout 1000.0) 25))
>       (while (eq (gethash key dbus-return-values-table :ignore) :ignore)
>       (or (input-pending-p) (sit-for 0.1 'nodisp))))

Well, actually if you use sit-for you don't need input-pending-p.

> With the example in this bug report, I get blocked then.

What do you mean by "blocked"?

> A key might be placed in `unread-command-events', and I still must
> handle it.

What do you mean by "handle it"?

Could let-binding unread-command-events around the call to sit-for
address the issue?


        Stefan

Previous Next

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