From: Eli Zaretskii <eliz@gnu.org>
To: Mark Seeto <markseeto@gmail.com>
Cc: 42350@debbugs.gnu.org
Subject: bug#42350: 26.3; C-c C-c in R console buffer causes Control key to get "stuck"
Date: Tue, 14 Jul 2020 17:49:23 +0300 [thread overview]
Message-ID: <83h7uam9sc.fsf@gnu.org> (raw)
In-Reply-To: <CAK2mLtNtxQ6T4gDhBn3GOTDejQmdir856ZWDniccvy-zfVBJ8A@mail.gmail.com> (message from Mark Seeto on Tue, 14 Jul 2020 12:26:26 +1000)
> From: Mark Seeto <markseeto@gmail.com>
> Date: Tue, 14 Jul 2020 12:26:26 +1000
>
> I'm running R using the ESS package (version 18.10.2, installed using package-list-packages) in Emacs
> 26.3 in MS Windows 10.
>
> When I'm in an R console window (Emacs buffer named "*R*" where R is running) and I press C-c C-c
> using the right (not left) Control key, Emacs starts acting as though the Control key is being held down. For
> example, if I press C-c C-c <return> in the R console buffer using the right Control key, I get the message
> "<C-return> is undefined", and it keeps happening with further key presses (e.g. pressing p moves to the
> previous line). The problem doesn't happen if I press C-c C-c in the R console buffer using the left Control
> key. Even other programs (e.g. Notepad, Firefox) start acting as though Control is being pressed.
>
> The "stuck" Control key can be "released" by pressing the left Control key.
I suspect this is something specific to your Windows system setup,
perhaps in combination with what R does. Because I tried to reproduce
what you say on a Windows 10 system without R, and couldn't. It
sounds like some "sticky key" feature or something similar.
I very much doubt this is an Emacs problem.
next prev parent reply other threads:[~2020-07-14 14:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-14 2:26 bug#42350: 26.3; C-c C-c in R console buffer causes Control key to get "stuck" Mark Seeto
2020-07-14 14:49 ` Eli Zaretskii [this message]
2020-07-15 1:39 ` Mark Seeto
2020-07-15 15:03 ` Eli Zaretskii
2020-07-16 6:48 ` Mark Seeto
2020-07-16 8:30 ` Eli Zaretskii
2020-07-16 9:45 ` Mark Seeto
2020-07-16 16:53 ` Eli Zaretskii
2020-07-16 19:41 ` Mark Seeto
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=83h7uam9sc.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=42350@debbugs.gnu.org \
--cc=markseeto@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.