From: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>
To: zsh-workers@sunsite.dk
Subject: Re: bindkey
Date: Fri, 22 Jun 2001 15:09:01 +0200 (MET DST) [thread overview]
Message-ID: <200106221309.PAA18510@beta.informatik.hu-berlin.de> (raw)
In-Reply-To: <200106221214.f5MCEEl16908@linux3.maruska.tin.it>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 939 bytes --]
Michal Maru¹ka wrote:
> 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):
Or just invoke `cat -v' without arguments and you should be able to see
the sequences on the terminal.
Bye
Sven
--
Sven Wischnowsky wischnow@informatik.hu-berlin.de
next prev parent reply other threads:[~2001-06-22 13:10 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 ` bindkey Michal Maru¹ka
2001-06-22 13:09 ` Sven Wischnowsky [this message]
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=200106221309.PAA18510@beta.informatik.hu-berlin.de \
--to=wischnow@informatik.hu-berlin.de \
--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).