From: Eli Zaretskii <eliz@gnu.org>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: 23980@debbugs.gnu.org, chris.w.feng@gmail.com
Subject: bug#23980: 25.0.95; Events put in `unread-command-events' can be wrongly handled
Date: Wed, 19 Dec 2018 17:27:14 +0200 [thread overview]
Message-ID: <83h8f9czal.fsf@gnu.org> (raw)
In-Reply-To: <37124b3a-54d8-4da8-22c0-7d739ec0a4b8@yandex.ru> (message from Dmitry Gutov on Wed, 19 Dec 2018 15:54:31 +0200)
> Cc: 23980@debbugs.gnu.org, chris.w.feng@gmail.com
> From: Dmitry Gutov <dgutov@yandex.ru>
> Date: Wed, 19 Dec 2018 15:54:31 +0200
>
> On 22.02.2018 9:39, Eli Zaretskii wrote:
>
> >> Maybe consider it for inclusion if we end up having more pretests? This
> >> patch has been in master for a few months, and it's two lines long, so
> >> it must be *somewhat* safe.
> >
> > Yes, a good idea.
>
> Any chance we can backport it now? I have hard-to-reproduce bug report
> from users of third-party code (company-mode plus elpy) which, I am
> told, is definitely fixed by applying this patch to emacs-26:
>
> https://github.com/jorgenschaefer/elpy/issues/1396#issuecomment-448142207
Risky... but okay, let's do it.
Thanks.
next prev parent reply other threads:[~2018-12-19 15:27 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
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 [this message]
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
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=83h8f9czal.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=23980@debbugs.gnu.org \
--cc=chris.w.feng@gmail.com \
--cc=dgutov@yandex.ru \
/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).