From: <firstname.lastname@example.org> To: email@example.com Subject: Re: Second Ctl in keychord not detected Date: Wed, 19 Jan 2022 15:04:29 +0100 [thread overview] Message-ID: <YegabQui5c/9kUev@tuxteam.de> (raw) In-Reply-To: <firstname.lastname@example.org> [-- Attachment #1: Type: text/plain, Size: 730 bytes --] On Wed, Jan 19, 2022 at 01:08:10PM +0100, Loris Bennett wrote: > Hi, > > This is not really an Org question but an Emacs or possibly tmux > problem. However, the problem manifests itself in an Org context. I guess this is tmux. It behaves more or less like an oldskool terminal, where C-<key> is transferred as the ASCII code with bit 7 masked out. This would mean only C-@ (mapped to ASCII 0, which might have its own... interesting issues) through a few chars after CTRL-Z do make sense in this context. This "protocol" can't even express things like CTRL-. or CTRL-, -- that luxury is reserved to more GUI-ish environments :-) (NOTE: just a guess, I haven't direct experience with tmux). Cheers -- t [-- Attachment #2: signature.asc --] [-- Type: application/pgp-signature, Size: 195 bytes --]
prev parent reply other threads:[~2022-01-19 15:06 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-01-19 12:08 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 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 [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.orgmode.org/ * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=YegabQui5c/9kUev@tuxteam.de \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: Second Ctl in keychord not detected' \ /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
Code repositories for project(s) associated with this 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).