zsh-workers
 help / color / mirror / code / Atom feed
From: Zefram <zefram@fysh.org>
To: Bart Schaefer <schaefer@candle.brasslantern.com>
Cc: zsh-workers@sunsite.dk
Subject: Re: History Up key
Date: Thu, 15 Mar 2001 19:27:44 +0000 (GMT)	[thread overview]
Message-ID: <E14ddPV-0002Jq-00@crucigera.fysh.org> (raw)
In-Reply-To: <010313135746.ZM638@candle.brasslantern.com> from Bart Schaefer at "Mar 13, 2001 01:57:46 pm"

Bart Schaefer wrote:
>Obviously, though, users want it, or all those vi clones wouldn't have put
>in hacks to make it work.

Yes, we should make it easy to get the arrow key bindings.
It should be easy to have either behaviour, whatever the default is.
We should be aiming for a situation where the interested user only
needs to add a single command, either "create_arrow_key_bindings" or
"remove_arrow_key_bindings", in their .zshrc -- the command should be
a zsh function in the distribution.

>>     With that heuristic in
>>     place, the only problem with adaption is the issue of programmatically
>>     knowing where those bindings are.
>
>Which should be easier with the termcap and terminfo modules ...

Easier, but putting in heuristics such that arrow key sequences from
terminfo may or may not be bound makes it more difficult.  If arrow keys
are bound by default, then the shell code to turn them off is going to
have to exactly duplicate the logic of the C code that turns them on.
Btw, what happens to these bindings if $TERM gets changed?

This difficulty with turning off the bindings is why I suggest that the
bindings should be off by default -- it's easier to have only one copy
of the logic, in some shell code that creates the bindings.

>Should I commit my zkbd script?  If so, where -- under Misc/ ?

It looks useful.  Misc makes some kind of sense, but I'd put it under
Functions.

-zefram


  parent reply	other threads:[~2001-03-15 19:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E14cvJO-00084f-00@crucigera.fysh.org>
2001-03-13 21:57 ` Bart Schaefer
2001-03-14 11:28   ` Peter Stephenson
2001-03-15 19:15     ` Zefram
2001-03-15 19:27   ` Zefram [this message]
2001-03-17 22:31     ` Bart Schaefer

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=E14ddPV-0002Jq-00@crucigera.fysh.org \
    --to=zefram@fysh.org \
    --cc=schaefer@candle.brasslantern.com \
    --cc=zsh-workers@sunsite.dk \
    /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).