Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: bindkey
- X-seq: zsh-workers 15034
- From: "Bart Schaefer" <schaefer@xxxxxxxxxxxxxxxxxxxxxxx>
- To: "Michal Maru¹ka" <mmc@xxxxxxxxxxxxxxxxxx>, Pierpaolo.Righini@xxxxxxxxxxxxx
- Subject: Re: bindkey
- Date: Thu, 21 Jun 2001 18:40:50 +0000
- Cc: zsh-workers@xxxxxxxxxx
- In-reply-to: <200106211715.f5LHFdD29417@xxxxxxxxxxxxxxxxxxxxx>Comments: In reply to "Michal Maru¹ka" <mmc@xxxxxxxxxxxxxxxxxx> "Re: bindkey" (Jun 21, 7:15pm)
- Mailing-list: contact zsh-workers-help@xxxxxxxxxx; run by ezmlm
- References: <Pine.OSF.4.21.0106211824170.8008-100000@xxxxxxxxxxxxxxxxxxxx> <200106211715.f5LHFdD29417@xxxxxxxxxxxxxxxxxxxxx>
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
Messages sorted by:
Reverse Date,
Date,
Thread,
Author