unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Richard Copley <rcopley@gmail.com>
Cc: 28348-done@debbugs.gnu.org
Subject: bug#28348: 26.0.50; keyboard state is wrong after typing C-c C-k in compilation mode
Date: Wed, 06 Sep 2017 05:32:27 +0300	[thread overview]
Message-ID: <83shg01rr8.fsf@gnu.org> (raw)
In-Reply-To: <CAPM58oi-JmZC8i9LFL8=XV+5PfeGPPyy7b21LScXjbpTuPd7Zw@mail.gmail.com> (message from Richard Copley on Wed, 6 Sep 2017 00:06:30 +0100)

> From: Richard Copley <rcopley@gmail.com>
> Date: Wed, 6 Sep 2017 00:06:30 +0100
> Cc: 28348@debbugs.gnu.org
> 
> On 5 September 2017 at 18:35, Eli Zaretskii <eliz@gnu.org> wrote:
> >> Date: Tue, 05 Sep 2017 18:40:19 +0300
> >> From: Eli Zaretskii <eliz@gnu.org>
> >> Cc: 28348@debbugs.gnu.org
> >>
> >> > From: Richard Copley <rcopley@gmail.com>
> >> > Date: Mon, 4 Sep 2017 20:10:46 +0100
> >> >
> >> > In compilation mode, while the inferior process is running, type C-c,
> >> > C-k and do not release the control key after hitting k.  With the
> >> > control key still held down, hit c again.
> >> >
> >> > Expected: Emacs reads C-c (and after a delay displays it in
> >> > the minibuffer because it is a prefix key).
> >> >
> >> > Actual: Emacs reads c (and reports an error, "c is undefined").
> >>
> >> Seems to be specific to MS-Windows, and very old (I see it in Emacs
> >> 23).
> >
> > Should be fixed now.
> 
> Wonderful, thank you. Works for me.

Thanks, closing.





      reply	other threads:[~2017-09-06  2:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-04 19:10 bug#28348: 26.0.50; keyboard state is wrong after typing C-c C-k in compilation mode Richard Copley
2017-09-05 15:40 ` Eli Zaretskii
2017-09-05 17:35   ` Eli Zaretskii
2017-09-05 23:06     ` Richard Copley
2017-09-06  2:32       ` Eli Zaretskii [this message]

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=83shg01rr8.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=28348-done@debbugs.gnu.org \
    --cc=rcopley@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).