From: "Michal Maru¹ka" <mmc@maruska.dyndns.org>
To: Pierpaolo.Righini@roma1.infn.it
Cc: zsh-workers@sunsite.dk
Subject: Re: bindkey
Date: Fri, 22 Jun 2001 14:14:14 +0200 [thread overview]
Message-ID: <200106221214.f5MCEEl16908@linux3.maruska.tin.it> (raw)
In-Reply-To: <Pine.OSF.4.21.0106221258590.18413-100000@ax0rm1.roma1.infn.it> (message from Pierpaolo Righini on Fri, 22 Jun 2001 13:59:18 +0200 (MET DST))
Pierpaolo Righini writes:
>computer too!! Thanks a lot! Indeed what I really needed is the way to
>obtain the code of the various keys.
Bart Schaefer writes>
> Hmm, this is a bit of a thorny problem: describe-key-briefly only works
> correctly for keys which are bound to something. For keys that are not
> bound, the search through the key tables stops as soon as it finds that
> the prefix is not bound, without consuming the remaining characters of
> the multi-key sequence.
Given this situation, I think the way to know the sequence (sent by a key) is to
look at the configuration of the terminal (emulator), In case your problem is with Xterm,
see the file (in XFree 4.0.2):
/etc/X11/app-defaults/XTerm
mine contains:
*VT100*translations: #override \
....(lines skipped)
<KeyPress> Home: string("^[[1~") \n\
<KeyPress> End: string("^[[4~") \n\
Ctrl <KeyPress> Home: string("^[[88~") \n\
Ctrl <KeyPress> End: string("^[[87~") \n\
Shift <KeyPress> Right: string("^[r") \n\
Ctrl <KeyPress> Right: string("^[[`3") \n\
Ctrl <Key> Left: string("^[[`2") \n\
IIRC in XFree 3.xx it was:
/usr/X11/lib/X11/app-defaults/XTerm
next prev parent reply other threads:[~2001-06-22 12:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-21 16:26 bindkey Pierpaolo Righini
2001-06-21 17:15 ` bindkey Michal Maru¹ka
2001-06-21 18:40 ` bindkey Bart Schaefer
2001-06-22 11:59 ` bindkey Pierpaolo Righini
2001-06-22 12:14 ` Michal Maru¹ka [this message]
2001-06-22 13:09 ` bindkey Sven Wischnowsky
2001-06-21 18:33 ` bindkey 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=200106221214.f5MCEEl16908@linux3.maruska.tin.it \
--to=mmc@maruska.dyndns.org \
--cc=Pierpaolo.Righini@roma1.infn.it \
--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).