From: Eli Zaretskii <eliz@gnu.org>
To: Nikolay Kudryavtsev <nikolay.kudryavtsev@gmail.com>
Cc: r.stocker@mnet-mail.de, 68914@debbugs.gnu.org
Subject: bug#68914: Windows makes Emacs choke on and swallow the WIN keys
Date: Sun, 04 Feb 2024 15:56:31 +0200 [thread overview]
Message-ID: <867cjk2v00.fsf@gnu.org> (raw)
In-Reply-To: <08fd4dda-576f-48a7-aa04-5c24135d21ba@gmail.com> (message from Nikolay Kudryavtsev on Sun, 4 Feb 2024 16:32:48 +0300)
> From: Nikolay Kudryavtsev <nikolay.kudryavtsev@gmail.com>
> Date: Sun, 4 Feb 2024 16:32:48 +0300
>
> But there's something else. I'm not sure if it's the same bug, but
> something's been iffy about Emacs keyboard input handling on Windows for
> the last few major versions.
I don't think it's the same issue. I suggest submitting a separate
bug report with the details.
> Unfortunately I've yet to find a simple reproduction recipe and hence
> why I haven't filled that one the tracker. The problem is as follows.
>
> I use a certain piece of software that switches between keyboard layouts
> by CAPS LOCK. So CAPS LOCK, the feature, is normally mostly inactive on
> my machine and requires a certain other combination to activate. Emacs
> normally respects that. Except when it's under a load running lisp code.
> During that time there are time intervals during which pressing CAPS
> LOCK would incorrectly set it on for me.
>
> One way I can reliably reproduce this is by doing M-x list-packages and
> then tapping CAPS LOCK. At some point it would light up.
In the bug report I suggest to submit, please describe in more detail
how to reproduce this using list-packages. How to "tap CAPS LOCK" and
what to look for while doing that. I just tried naïvely to reproduce
that and didn't see any problems, probably because I didn't know where
to look.
> Thus I believe that the input handling intermittently breaks during the
> high load(lisp evaluation).
>
> My testing had shown that the last version that does not suffer from
> this is Emacs 25.
Emacs 26 introduced the low-level keyboard hook.
next prev parent reply other threads:[~2024-02-04 13:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-03 20:45 bug#68914: Windows makes Emacs choke on and swallow the WIN keys Raffael Stocker
2024-02-04 6:31 ` Eli Zaretskii
2024-02-04 13:02 ` Raffael Stocker
2024-02-04 14:14 ` Eli Zaretskii
2024-02-12 20:13 ` Raffael Stocker
2024-02-04 13:32 ` Nikolay Kudryavtsev
2024-02-04 13:56 ` Eli Zaretskii [this message]
2024-09-13 13:26 ` Raffael Stocker
2024-09-13 14:45 ` Eli Zaretskii
2024-09-21 9:48 ` Eli Zaretskii
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=867cjk2v00.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=68914@debbugs.gnu.org \
--cc=nikolay.kudryavtsev@gmail.com \
--cc=r.stocker@mnet-mail.de \
/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.