From: Ken Brown <kbrown@cornell.edu>
To: cygwin@cygwin.com
Subject: Re: Ctrl+Space not working under Windows Terminal
Date: Sun, 4 Sep 2022 11:48:05 -0400 [thread overview]
Message-ID: <048cb992-3c96-80a9-6503-259feda2a387@cornell.edu> (raw)
In-Reply-To: <CAKhdrT55TQGgOevyGXpcrw8RijzOaNbZqRouU2PcZXxYF-1Pdw@mail.gmail.com>
On 9/2/2022 9:33 PM, Ricardo Urbina wrote:
> Hi, I'm trying out Cygwin's Zsh within Windows Terminal because WT
> integrates better with WSL, but Cygwin beats it for working on the Windows
> side.
>
> However, I launched emacs and eventually noticed that Ctrl+Space doesn't
> work when running under Windows Terminal.
It works on my system. Here's what I did:
1. Start Windows Terminal and run
/path/to/cygwin/bin/zsh -l
2. Launch emacs:
emacs-basic -Q
3. Within emacs, type
C-h k C-SPC
I then see "C-@" echoed in the minibuffer, and the resulting *Help* buffer says
C-@ runs the command set-mark-command (found in global-map), which
is an interactive compiled Lisp function in ‘simple.el’.
It is bound to C-@, C-SPC.
And typing C-SPC does indeed set the mark.
I'm not sure what's different on your system. Could there some be some setting
that's causing C-SPC to be eaten by Windows Terminal instead of being sent to
emacs as C-@?
By the way, if I run emacs-w32 instead of emacs-basic, everything is the same
except that in the first line of the *Help* buffer "C-@" is replaced by "C-SPC".
So emacs-w32 is actually seeing the C-SPC keypress.
Have you tried emacs-w32 to see if that works better for you?
Ken
next prev parent reply other threads:[~2022-09-04 15:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-03 1:33 Ricardo Urbina
2022-09-04 15:48 ` Ken Brown [this message]
2022-09-06 14:26 Lavrentiev, Anton (NIH/NLM/NCBI) [C]
2022-09-06 14:48 ` Christian Franke
2022-09-06 15:28 Lavrentiev, Anton (NIH/NLM/NCBI) [C]
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=048cb992-3c96-80a9-6503-259feda2a387@cornell.edu \
--to=kbrown@cornell.edu \
--cc=cygwin@cygwin.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.
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).