From: Mikael Magnusson <mikachu@gmail.com>
To: Pier Paolo Grassi <pierpaolog@gmail.com>
Cc: Zsh-Users List <zsh-users@zsh.org>
Subject: Re: control caracters
Date: Fri, 21 Oct 2022 17:53:58 +0200 [thread overview]
Message-ID: <CAHYJk3RK=KHP+OzJPRoKd4aCAiq4OJNML8=gEYLrumvQA3SKtw@mail.gmail.com> (raw)
In-Reply-To: <CAP+y1xDo5P8dA=4Go0npA2cgfhF8cdGGTKPdZorxH0mt=S09CA@mail.gmail.com>
On 10/21/22, Pier Paolo Grassi <pierpaolog@gmail.com> wrote:
> Hello, I was wondering if there is a way for the shell to bind capitalized
> ctrl-keys to different widgets then the non-capitalized counterpart. it
> seems to me that this is not possible from testing and by using ctrl-v that
> produces the same output for the capitalized and non-capitalized version of
> the same letter. I have the understanding that this can be due to
> historical reasons, being that the ctrl version of the keys corresponds to
> the first 31 bytes of the ascii standard (NUL to @, SOH to A etc, taken
> from man ascii). I would like to understand this better, if someone has a
> link to offer with details on the internals of how this works, and why the
> shell are (if this assumption holds true) still bound to work with this
> constraints.
This would be up to the terminal, in urxvt in particular you can do
this in your x resources (for each key):
URxvt.keysym.C-S-A: \001
but with another output than ^A, I leave that up to your imagination.
(note that ctrl-shift-[0-9a-f] in urxvt can also be configured to
input characters via iso14755, but this configuration will override
that).
--
Mikael Magnusson
prev parent reply other threads:[~2022-10-21 15:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-21 14:57 Pier Paolo Grassi
2022-10-21 15:02 ` Eric Cook
2022-10-21 15:06 ` Matthew Martin
2022-10-21 15:53 ` Mikael Magnusson [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAHYJk3RK=KHP+OzJPRoKd4aCAiq4OJNML8=gEYLrumvQA3SKtw@mail.gmail.com' \
--to=mikachu@gmail.com \
--cc=pierpaolog@gmail.com \
--cc=zsh-users@zsh.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.vuxu.org/mirror/zsh/
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 NNTP newsgroup(s).