From: Artur Malabarba <bruce.connor.am@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Michael Heerdegen <michael_heerdegen@web.de>,
radon.neon@gmail.com, 31692@debbugs.gnu.org,
Noam Postavsky <npostavs@gmail.com>
Subject: bug#31692: Emacs sometimes drops key events
Date: Tue, 5 Jun 2018 18:39:25 -0300 [thread overview]
Message-ID: <CAAdUY-JqiFQV3BQhfK4pwwiwk3F0Ftt2WLXm_Tu=6xs4G02oUA@mail.gmail.com> (raw)
In-Reply-To: <83d0x5b909.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 641 bytes --]
Thanks for the cc.
I'll admit that issue flew under my radar.
I'm not sure how to fix it, though. Is there a way to ensure that the input
that interrupts `while-no-input' still gets properly handled by emacs?
On Tue, Jun 5, 2018, 11:31 AM Eli Zaretskii <eliz@gnu.org> wrote:
> > From: Noam Postavsky <npostavs@gmail.com>
> > Cc: Michael Heerdegen <michael_heerdegen@web.de>, radon.neon@gmail.com,
> 31692@debbugs.gnu.org
> > Date: Tue, 05 Jun 2018 07:57:55 -0400
> >
> > Although since it's in GNU ELPA, I guess reporting it here is also
> > correct.
>
> Reporting here is OK, but I think then the developer should be CC'ed
> (done).
>
[-- Attachment #2: Type: text/html, Size: 1483 bytes --]
next prev parent reply other threads:[~2018-06-05 21:39 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-03 2:21 bug#31692: Emacs sometimes drops key events Radon Rosborough
2018-06-03 2:36 ` Eli Zaretskii
2018-06-03 4:54 ` Radon Rosborough
2018-06-03 15:05 ` Eli Zaretskii
2018-06-03 19:23 ` Alan Third
2018-06-04 10:41 ` João Távora
2018-06-05 0:59 ` Michael Heerdegen
2018-06-05 2:37 ` Eli Zaretskii
2018-06-05 2:41 ` Radon Rosborough
2018-06-05 4:11 ` Eli Zaretskii
2018-06-05 21:40 ` Michael Heerdegen
2018-06-06 2:37 ` Eli Zaretskii
2018-06-06 2:58 ` Michael Heerdegen
2018-06-06 14:52 ` Eli Zaretskii
2018-06-06 23:12 ` Michael Heerdegen
2018-06-07 15:20 ` Eli Zaretskii
2018-06-06 14:45 ` Eli Zaretskii
2018-06-06 22:50 ` Michael Heerdegen
2018-06-07 15:20 ` Eli Zaretskii
2018-06-07 15:30 ` Stefan Monnier
2018-06-07 15:52 ` Eli Zaretskii
2018-06-07 18:44 ` Stefan Monnier
2018-06-08 22:17 ` Michael Heerdegen
2018-06-11 21:08 ` Michael Heerdegen
2018-06-12 2:27 ` Eli Zaretskii
2018-06-16 8:26 ` Eli Zaretskii
2018-06-16 8:28 ` Eli Zaretskii
2018-06-17 4:39 ` Michael Heerdegen
2018-07-05 19:07 ` Michael Heerdegen
2018-07-05 19:27 ` Eli Zaretskii
2018-07-06 17:43 ` Michael Heerdegen
2018-06-05 2:48 ` Michael Heerdegen
2018-06-05 4:13 ` Eli Zaretskii
2018-06-05 11:57 ` Noam Postavsky
2018-06-05 14:31 ` Eli Zaretskii
2018-06-05 21:39 ` Artur Malabarba [this message]
2018-06-06 14:39 ` Eli Zaretskii
2018-06-03 12:13 ` Noam Postavsky
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='CAAdUY-JqiFQV3BQhfK4pwwiwk3F0Ftt2WLXm_Tu=6xs4G02oUA@mail.gmail.com' \
--to=bruce.connor.am@gmail.com \
--cc=31692@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=michael_heerdegen@web.de \
--cc=npostavs@gmail.com \
--cc=radon.neon@gmail.com \
/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.