From: Ray Andrews <rayandrews@eastlink.ca>
To: zsh-users@zsh.org
Subject: Re: key binding not working [SOLVED]
Date: Mon, 26 Sep 2022 11:04:51 -0700 [thread overview]
Message-ID: <9b958586-ce5c-55c6-c835-d8bdc45848f6@eastlink.ca> (raw)
In-Reply-To: <727dcb31-3ead-03fb-db9b-e0b8e7c59a00@eastlink.ca>
On 2022-09-26 06:59, Ray Andrews wrote:
> Hey, supposing we concluded solved threads with some indication, like
> I'm experimenting with in my subject line?
>
A wee bit more trouble but at least I figgered it out myself. HOME and
END stopped working.
Used to work:
bindkey "\eOH" beginning-of-line
bindkey "\eOF" end-of-line
... but now:
# 2022-09-26: These are the new values for HOME and END:
bindkey "\e[H" beginning-of-line
bindkey "\e[F" end-of-line
Why does this happen? Who does this, and why do they do it? Is this
something built into the keyboard or does Debian do this? IIRC the
actual hardware signals to the computer are not what '^v' shows us,
there's a few levels of interpretation involved, so could be the
keyboard itself, or Debian or Linux. But why bother? Why do they hate us?
next prev parent reply other threads:[~2022-09-26 18:05 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-25 21:14 key binding not working Ray Andrews
2022-09-25 22:31 ` Bart Schaefer
2022-09-25 22:46 ` Ray Andrews
2022-09-25 23:14 ` Ray Andrews
2022-09-26 3:48 ` Marc Chantreux
2022-09-27 0:30 ` zkbd (was Re: key binding not working) Bart Schaefer
2022-09-27 1:39 ` Ray Andrews
2022-09-26 1:16 ` key binding not working Ray Andrews
2022-09-26 1:58 ` Lawrence Velázquez
2022-09-26 3:15 ` Ray Andrews
2022-09-26 4:01 ` Lawrence Velázquez
2022-09-26 6:28 ` Roman Perepelitsa
2022-09-26 13:59 ` key binding not working [SOLVED] Ray Andrews
2022-09-26 18:04 ` Ray Andrews [this message]
2022-09-26 18:13 ` Roman Perepelitsa
2022-09-26 19:12 ` Peter Stephenson
2022-09-26 19:43 ` Mikael Magnusson
2022-09-26 21:31 ` Ray Andrews
2022-09-26 22:27 ` Vin Shelton
2022-09-26 22:35 ` Ray Andrews
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=9b958586-ce5c-55c6-c835-d8bdc45848f6@eastlink.ca \
--to=rayandrews@eastlink.ca \
--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).