From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: "Peter Münster" <pmlists@free.fr>, 11447@debbugs.gnu.org
Subject: bug#11447: 24.1.50; notifications-notify eats keystrokes
Date: Fri, 11 May 2012 11:20:22 -0400 [thread overview]
Message-ID: <jwv7gwiycd6.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87ipg2reoh.fsf@gmx.de> (Michael Albinus's message of "Fri, 11 May 2012 16:10:54 +0200")
>>> (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
next prev parent reply other threads:[~2012-05-11 15:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-10 20:45 bug#11447: 24.1.50; notifications-notify eats keystrokes Peter Münster
2012-05-11 8:07 ` Michael Albinus
2012-05-11 11:22 ` Peter Münster
2012-05-11 13:24 ` Stefan Monnier
2012-05-11 14:10 ` Michael Albinus
2012-05-11 15:20 ` Stefan Monnier [this message]
2012-05-11 15:27 ` Michael Albinus
2012-05-11 17:28 ` Stefan Monnier
2012-05-13 9:11 ` Michael Albinus
[not found] ` <jwv1umo2pjf.fsf-monnier+emacs@gnu.org>
2012-05-13 14:19 ` Michael Albinus
2012-05-13 14:46 ` Stefan Monnier
2012-05-13 15:15 ` Michael Albinus
2012-05-13 15:44 ` Stefan Monnier
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jwv7gwiycd6.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=11447@debbugs.gnu.org \
--cc=michael.albinus@gmx.de \
--cc=pmlists@free.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.