From: "João Távora" <joaotavora@gmail.com>
To: Alan Third <alan@idiocy.org>
Cc: Radon Rosborough <radon.neon@gmail.com>, 31692@debbugs.gnu.org
Subject: bug#31692: Emacs sometimes drops key events
Date: Mon, 4 Jun 2018 11:41:13 +0100 [thread overview]
Message-ID: <CALDnm53+jeqSogOMN6uVBzpTeoEpEupz-himTDJ1EgmvUpJURA@mail.gmail.com> (raw)
In-Reply-To: <20180603192310.GA8167@breton.holly.idiocy.org>
[-- Attachment #1: Type: text/plain, Size: 972 bytes --]
I'd just like to add a data point here.
I'm on Debian GNU/Linux and have experienced the same thing (though not
very often).
I lose a key, and there's a "Quit" in my *Messages*, too.
More importantly perhaps, I'm also using aggressive-indent-mode.
João
On Sun, Jun 3, 2018 at 8:23 PM, Alan Third <alan@idiocy.org> wrote:
> On Sun, Jun 03, 2018 at 06:05:36PM +0300, Eli Zaretskii wrote:
> > > From: Radon Rosborough <radon.neon@gmail.com>
> > > Date: Sat, 2 Jun 2018 22:54:11 -0600
> > > Cc: 31692@debbugs.gnu.org
> > >
> > > > Is this in a text-mode frame or a GUI frame?
> > >
> > > It has happened in both.
> >
> > Then it's probably something specific to NS event handling.
>
> It could be worth redefining NS_KEYLOG to 1 in nsterm.m. This prints a
> whole bunch of stuff to the terminal and should let us find out where
> the key presses are being lost if it is in the NS code.
> --
> Alan Third
>
>
>
>
--
João Távora
[-- Attachment #2: Type: text/html, Size: 1740 bytes --]
next prev parent reply other threads:[~2018-06-04 10:41 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 [this message]
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
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
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=CALDnm53+jeqSogOMN6uVBzpTeoEpEupz-himTDJ1EgmvUpJURA@mail.gmail.com \
--to=joaotavora@gmail.com \
--cc=31692@debbugs.gnu.org \
--cc=alan@idiocy.org \
--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 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).