From: Mark Seeto <markseeto@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
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: Thu, 16 Jul 2020 16:48:29 +1000 [thread overview]
Message-ID: <CAK2mLtMGLcRp8hsXvQ80H6ixT=QYgThhEiGR2cPQrQEvrCZtjw@mail.gmail.com> (raw)
In-Reply-To: <83pn8wlt1p.fsf@gnu.org>
On Thu, Jul 16, 2020 at 1:03 AM Eli Zaretskii <eliz@gnu.org> wrote:
> Emacs 26 changed the way it reads keyboard input on MS-Windows, but
> this is the first time I hear a complaint about such "sticky"
> behavior, so it must be somehow related to R.
>
> Did you try asking on R forums about this problem?
Thanks for your reply.
I haven't asked on R forums but I asked on the Emacs Speaks Statistics
help mailing list because my first thought was that the problem was
probably caused by a change in a recent version of the ESS package.
After I sent an update with some results suggesting that it wasn't
caused by a change in ESS, someone replied to me saying that he had
the same problem, and he suggested that I send an Emacs bug report.
I've turned off all the Windows "sticky keys" and similar options I
could find (they were already turned off).
I just tried C-c C-c in a Python (Jupyter) console buffer (elpy
package), and the same problem happened in Emacs 26.3 but not in Emacs
25.2.
next prev parent reply other threads:[~2020-07-16 6:48 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
2020-07-15 1:39 ` Mark Seeto
2020-07-15 15:03 ` Eli Zaretskii
2020-07-16 6:48 ` Mark Seeto [this message]
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='CAK2mLtMGLcRp8hsXvQ80H6ixT=QYgThhEiGR2cPQrQEvrCZtjw@mail.gmail.com' \
--to=markseeto@gmail.com \
--cc=42350@debbugs.gnu.org \
--cc=eliz@gnu.org \
/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.