From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18740 invoked from network); 22 Jun 2001 13:10:54 -0000 Received: from sunsite.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 22 Jun 2001 13:10:54 -0000 Received: (qmail 416 invoked by alias); 22 Jun 2001 13:10:12 -0000 Mailing-List: contact zsh-workers-help@sunsite.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 15046 Received: (qmail 388 invoked from network); 22 Jun 2001 13:10:11 -0000 From: Sven Wischnowsky Date: Fri, 22 Jun 2001 15:09:01 +0200 (MET DST) Message-Id: <200106221309.PAA18510@beta.informatik.hu-berlin.de> To: zsh-workers@sunsite.dk Subject: Re: bindkey In-Reply-To: <200106221214.f5MCEEl16908@linux3.maruska.tin.it> 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