all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Dmitry Gutov <dgutov@yandex.ru>
To: Eli Zaretskii <eliz@gnu.org>, Chris Feng <chris.w.feng@gmail.com>
Cc: 23980@debbugs.gnu.org
Subject: bug#23980: 25.0.95; Events put in `unread-command-events' can be wrongly handled
Date: Tue, 20 Feb 2018 23:16:47 +0200	[thread overview]
Message-ID: <cc68c767-5d91-26e4-ee81-16b6c5e643df@yandex.ru> (raw)
In-Reply-To: <83y3jn7bi5.fsf@gnu.org>

On 2/20/18 8:37 PM, Eli Zaretskii wrote:

> I'd need someone (Chris?) to tell which situations cause (t SOMETHING)
> be put into unread-command-events.  If these situations are rare
> enough, maybe we can risk it.

At least one of the places that do that is sit-for. See the long comment 
at the end of its definition (I don't really understand its last 
sentence, FWIW).





  reply	other threads:[~2018-02-20 21:16 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-14 14:03 bug#23980: 25.0.95; Events put in `unread-command-events' can be wrongly handled Chris Feng
2017-11-19  9:39 ` Chris Feng
2018-02-20 15:35   ` Dmitry Gutov
2018-02-20 18:37     ` Eli Zaretskii
2018-02-20 21:16       ` Dmitry Gutov [this message]
2018-02-21  4:22         ` Eli Zaretskii
2018-02-21  7:40           ` Chris Feng
2018-02-21 10:47             ` Dmitry Gutov
2018-02-21 12:23               ` Dmitry Gutov
2018-02-21 17:48               ` Eli Zaretskii
2018-02-21 21:45                 ` Dmitry Gutov
2018-02-22  7:39                   ` Eli Zaretskii
2018-12-19 13:54                     ` Dmitry Gutov
2018-12-19 15:27                       ` Eli Zaretskii
2018-12-19 16:07                         ` Dmitry Gutov

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=cc68c767-5d91-26e4-ee81-16b6c5e643df@yandex.ru \
    --to=dgutov@yandex.ru \
    --cc=23980@debbugs.gnu.org \
    --cc=chris.w.feng@gmail.com \
    --cc=eliz@gnu.org \
    /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.