zsh-workers
 help / color / mirror / code / Atom feed
From: Zefram <zefram@dcs.warwick.ac.uk>
To: sinclair@dis.strath.ac.uk (Duncan Sinclair)
Cc: zefram@dcs.warwick.ac.uk, zsh-workers@math.gatech.edu
Subject: Re: big key binding patch
Date: Tue, 26 Nov 1996 12:10:02 +0000 (GMT)	[thread overview]
Message-ID: <15840.199611261210@stone.dcs.warwick.ac.uk> (raw)
In-Reply-To: <10360.849009784@dis.strath.ac.uk> from "Duncan Sinclair" at Nov 26, 96 12:03:04 pm

>>Just to reiterate what I said yesterday, we should *not* use the patch
>>to bind the ANSI arrow key sequences in vi insert mode.  It is completely
>>the wrong thing to do, and actually causes more problems.
>
>I'm curious.... why?

Because vi doesn't bind them, and because <ESC> already has a meaning
that its use as a prefix would interfere with.

>                      And what happens if you bind them using bindkey?

It'll work as expected.

>Can we use other ESC-prefixed bindings in vi-insert mode?

Yes, just bind them using bindkey.

>My version of vi ("nvi 1.34") allows me to use the cursor keys during
>insert mode - with the obvious bindings: (output of :map!)

I also use nvi, and those bindings really piss me off.  Especially
because I can't disable them (except by hacking the source).

>  ^[OA  ^[ka  cursor up

Have you tried using this binding after you gave i a count?  Look at
what that binding does; it's a disgusting kludge.  In ZLE it wouldn't
be kludged, but it would still be wrong.

-zefram


  reply	other threads:[~1996-11-26 12:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1996-11-26 12:03 Duncan Sinclair
1996-11-26 12:10 ` Zefram [this message]
  -- strict thread matches above, loose matches on Subject: below --
1996-11-24 15:30 Zefram
1996-11-25 13:22 ` Peter Stephenson
1996-11-25 16:02   ` Zefram
1996-11-25 18:57     ` Thorsten Meinecke
1996-11-25 22:05       ` Zefram
1996-11-26  8:46         ` Zefram

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=15840.199611261210@stone.dcs.warwick.ac.uk \
    --to=zefram@dcs.warwick.ac.uk \
    --cc=sinclair@dis.strath.ac.uk \
    --cc=zsh-workers@math.gatech.edu \
    /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).