From: "Loris Bennett" <loris.bennett@fu-berlin.de>
To: Org Mode Mailing List <emacs-orgmode@gnu.org>
Subject: Re: Second Ctl in keychord not detected
Date: Wed, 19 Jan 2022 15:49:42 +0100 [thread overview]
Message-ID: <87sftj6ard.fsf@hornfels.zedat.fu-berlin.de> (raw)
In-Reply-To: <874k5zlsd2.fsf@localhost> (Ihor Radchenko's message of "Wed, 19 Jan 2022 22:20:25 +0800")
Ihor Radchenko <yantar92@gmail.com> writes:
> "Loris Bennett" <loris.bennett@fu-berlin.de> writes:
>
>>>> Does anyone know what is happening to the second Ctl and how the problem
>>>> can be fixed?
>>>
>>> Try to run M-x describe-key <RET> C-c C-, and look at the output.
>>
>> The second C- disappears.
>>
>> I also get
>>
>> C-c C-. -> C-c .
>
> Then, it is terminal input problem. See
> https://stackoverflow.com/questions/11110801/why-does-ctrl-not-work-when-i-bind-it-to-a-command-in-emacs/11118511#11118511
You're right, the problem also happens locally when I start Emacs with
'-nw'. Thanks for the link - I'll have a look at the various solutions,
although it might just be easier to rebind the command ;-)
Cheers,
Loris
--
This signature is currently under construction.
next prev parent reply other threads:[~2022-01-19 15:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-19 12:08 Second Ctl in keychord not detected Loris Bennett
2022-01-19 12:48 ` Ihor Radchenko
2022-01-19 13:42 ` Loris Bennett
2022-01-19 14:20 ` Ihor Radchenko
2022-01-19 14:49 ` Loris Bennett [this message]
2022-01-20 2:11 ` Extend the existing alternative set of key bindings for terminals (was: Second Ctl in keychord not detected) Ihor Radchenko
2022-01-21 5:26 ` Tim Cross
2022-01-24 14:16 ` Ihor Radchenko
2022-01-25 8:51 ` Tim Cross
2022-01-21 8:03 ` Extend the existing alternative set of key bindings for terminals Loris Bennett
2022-01-23 6:58 ` Ihor Radchenko
2022-01-19 13:51 ` Second Ctl in keychord not detected Anssi Saari
2022-01-19 14:04 ` tomas
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87sftj6ard.fsf@hornfels.zedat.fu-berlin.de \
--to=loris.bennett@fu-berlin.de \
--cc=emacs-orgmode@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 public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.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).