From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: "\"Michal Maru¹ka\"" <mmc@maruska.dyndns.org>,
Pierpaolo.Righini@roma1.infn.it
Cc: zsh-workers@sunsite.dk
Subject: Re: bindkey
Date: Thu, 21 Jun 2001 18:40:50 +0000 [thread overview]
Message-ID: <1010621184051.ZM10798@candle.brasslantern.com> (raw)
In-Reply-To: =?iso-8859-1?Q?=3C200106211715=2Ef5LHFdD29417=40linux3=2Emaru?= =?iso-8859-1?Q?ska=2Etin=2Eit=3E?= =?iso-8859-1?Q?Comments=3A_In_reply_to_=22Michal_Maru=B9ka=22_=3Cmmc=40ma?= =?iso-8859-1?Q?ruska=2Edyndns=2Eorg=3E?= =?iso-8859-1?Q?________=22Re=3A_bindkey=22_=28Jun_21=2C__7=3A15pm=29?=
On Jun 21, 7:15pm, Michal Maru¹ka wrote:
}
} Ask the zsh what coded these keys produce:
} you> type: M-x (M- stands for meta or alt key -x means contemporary press the letter x)
} zsh> says: execute:_
} you> type: describe-key-briefly
} zsh> says: Describ key briefly: _
} you> press the key which bothers you. e.g Home
} zsh> says: "^[[1" is undefined-key
}
} describe-key-briefly did not report all the key sequence.
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.
Of course zsh has no way of knowing that it should treat \e[1~ as all one
sequence before it is bound to something; it can't tell how many keys you
pressed to cause that to appear.
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
Zsh: http://www.zsh.org | PHPerl Project: http://phperl.sourceforge.net
next prev parent reply other threads:[~2001-06-21 18:43 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 ` Bart Schaefer [this message]
2001-06-22 11:59 ` bindkey Pierpaolo Righini
2001-06-22 12:14 ` bindkey Michal Maru¹ka
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=1010621184051.ZM10798@candle.brasslantern.com \
--to=schaefer@candle.brasslantern.com \
--cc=Pierpaolo.Righini@roma1.infn.it \
--cc=mmc@maruska.dyndns.org \
--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).