From: Oliver Kiddle <okiddle@yahoo.co.uk>
To: Bart Schaefer <schaefer@brasslantern.com>
Cc: Roman Perepelitsa <roman.perepelitsa@gmail.com>,
dana <dana@dana.is>, Daniel Shahaf <d.s@daniel.shahaf.name>,
Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: Official plugin manager?
Date: Sun, 05 Jan 2020 11:40:41 +0100 [thread overview]
Message-ID: <21934-1578220841.002431@fxKo.0EhO.MMU2> (raw)
In-Reply-To: <CAH+w=7bPD-i1Pk-YeiP0xo3HFmQ0XFMQZ0x3VNder864wM1eQA@mail.gmail.com>
Bart wrote:
> > If keys such as arrows, home, end and delete just worked, this would be perfect!
>
> I tried to solve this a long time ago with Functions/Misc/zkbd, which
> allows one to interactively create a terminal profile. The problem is
> with knowing how to save/select the correct profile once it has been
My own approach generally consists of binding all the common sequences
without regard for whether they are right for the exact terminal in use.
Zsh's C code is binding both raw and application mode sequences for the
cursor keys which is similar.
Clashes are fairly rare and where I have come across them, it has only
been for terminals that set $TERM to something unique. To matter, the
clash has to be between two keys we want to bind which is rare. Del
producing ^? (which other terminals have for Backspace) is one case.
In my view, we should add bindings as best we can in the C code. It may
not be perfect but will work for the vast majority of users and likely
be harmless for the rest.
Oliver
next prev parent reply other threads:[~2020-01-05 10:41 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-02 3:17 Sebastian Gniazdowski
2020-01-02 4:28 ` Eric Cook
2020-01-02 11:03 ` Daniel Shahaf
2020-01-02 11:37 ` Sebastian Gniazdowski
2020-01-02 11:55 ` Sebastian Gniazdowski
2020-01-02 21:30 ` dana
2020-01-03 0:25 ` Sebastian Gniazdowski
2020-01-03 1:36 ` dana
2020-01-03 2:43 ` Sebastian Gniazdowski
2020-01-03 2:45 ` Bart Schaefer
2020-01-03 3:26 ` dana
2020-01-03 5:13 ` Sebastian Gniazdowski
2020-01-03 15:00 ` Peter Stephenson
2020-01-03 20:48 ` Daniel Shahaf
2020-01-03 21:51 ` Roman Perepelitsa
2020-01-03 22:06 ` Daniel Shahaf
2020-01-03 22:26 ` Bart Schaefer
2020-01-03 22:37 ` Roman Perepelitsa
2020-01-04 0:42 ` dana
2020-01-04 1:06 ` Daniel Shahaf
2020-01-04 15:46 ` Roman Perepelitsa
2020-01-04 16:27 ` Daniel Shahaf
2020-01-04 16:41 ` Roman Perepelitsa
2020-01-04 17:35 ` Daniel Shahaf
2020-01-04 17:42 ` Roman Perepelitsa
2020-01-04 17:11 ` Bart Schaefer
2020-01-05 10:40 ` Oliver Kiddle [this message]
2020-01-06 17:47 ` Leah Neukirchen
2020-01-03 11:15 ` Oliver Kiddle
2020-01-04 5:16 ` Sebastian Gniazdowski
2020-01-04 6:00 ` Sebastian Gniazdowski
2020-01-02 12:00 ` Roman Perepelitsa
2020-01-02 12:21 ` Sebastian Gniazdowski
2020-01-02 12:27 ` Roman Perepelitsa
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=21934-1578220841.002431@fxKo.0EhO.MMU2 \
--to=okiddle@yahoo.co.uk \
--cc=d.s@daniel.shahaf.name \
--cc=dana@dana.is \
--cc=roman.perepelitsa@gmail.com \
--cc=schaefer@brasslantern.com \
--cc=zsh-workers@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).