unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Michael Albinus <michael.albinus@gmx.de>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: "Peter Münster" <pmlists@free.fr>, 11447@debbugs.gnu.org
Subject: bug#11447: 24.1.50; notifications-notify eats keystrokes
Date: Sun, 13 May 2012 17:15:37 +0200	[thread overview]
Message-ID: <873974qfhi.fsf@gmx.de> (raw)
In-Reply-To: <jwvpqa816mb.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Sun, 13 May 2012 10:46:52 -0400")

Stefan Monnier <monnier@iro.umontreal.ca> writes:

>> Yes, that happens with your proposed
>
>> (setq unread-command-events
>>       (append unread-command-events (nreverse seen)))))
>
> Note that I only do it at the end of the loop, so it shouldn't affect
> the sit-for.

You do it inside the loop, every next loop cycle unread-command-events
could be non-nil, which confuses read-event.

Maybe you wanted to cumulate the read events in seen inside the loop,
and you wanted to append all events from seen to unread-command-events
outside the loop. That might work.

(Likely it isn't that important which version of the patch we use ...)

>         Stefan

Best regards, Michael..





  reply	other threads:[~2012-05-13 15:15 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
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 [this message]
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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=873974qfhi.fsf@gmx.de \
    --to=michael.albinus@gmx.de \
    --cc=11447@debbugs.gnu.org \
    --cc=monnier@iro.umontreal.ca \
    --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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).