From: "Bart Schaefer" <schaefer@brasslantern.com>
To: zsh-users@math.gatech.edu
Subject: Re: HPUX (was Re: vi command line editing)
Date: Wed, 25 Mar 1998 08:45:38 -0800 [thread overview]
Message-ID: <980325084538.ZM11726@candle.brasslantern.com> (raw)
In-Reply-To: <199803251022.KAA30301@taos.demon.co.uk>
On Mar 25, 10:22am, Andrew Main wrote:
} Subject: Re: HPUX (was Re: vi command line editing)
}
} Shawn Leas wrote:
} >bindkey -s "^[OA" "^[ka"
} >bindkey -s "^[OB" "^[ja"
} >bindkey -s "^[OD" "^[ha"
} >bindkey -s "^[OC" "^[la"
}
} That's a terminal issue. Some terminals send "^[OA" instead of "^[[A".
Actually, it's a keypad transmit mode issue, I think. vt100s and their
emulators in keypad mode send the '\eO' sequences, and in standard mode
send the '\e[' sequences. You can often see this by typing ctrl-V up
in the shell, then starting vi and typing ctrl-V up in insert mode.
Some versions of the vt100 and xterm termcap/terminfo entries always put
the terminal in keypad mode, others switch into it in the ti/te ("Begin
program that uses cursor motion") capabilities, still others never leave
standard mode. It's really annoying, especially on e.g. Linux where the
Num Lock key controls whether the -keyboard- really is in keypad mode.
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
prev parent reply other threads:[~1998-03-25 16:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-03-24 15:14 vi command line editing Stephen Marley
1998-03-24 15:46 ` Andrew Main
1998-03-24 16:26 ` Stephen Marley
1998-03-24 17:06 ` Andrew Main
1998-03-24 18:04 ` Stephen Marley
1998-03-24 18:35 ` Andrew Main
1998-03-24 18:57 ` Thomas Koehler
1998-03-24 19:38 ` Andrew Main
1998-03-24 20:30 ` Thomas Koehler
1998-03-24 22:05 ` HPUX (was Re: vi command line editing) Shawn Leas
1998-03-24 23:22 ` Shawn Leas
1998-03-25 10:22 ` Andrew Main
1998-03-25 16:01 ` Dan Nelson
1998-03-25 16:45 ` Bart Schaefer [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=980325084538.ZM11726@candle.brasslantern.com \
--to=schaefer@brasslantern.com \
--cc=zsh-users@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).