From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8274 invoked from network); 30 May 2001 08:04:06 -0000 Received: from sunsite.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 30 May 2001 08:04:06 -0000 Received: (qmail 6604 invoked by alias); 30 May 2001 08:03:45 -0000 Mailing-List: contact zsh-workers-help@sunsite.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 14561 Received: (qmail 6593 invoked from network); 30 May 2001 08:03:45 -0000 X-Envelope-Sender-Is: Andrej.Borsenkow@mow.siemens.ru (at relayer goliath.siemens.de) From: "Andrej Borsenkow" To: "ZSH Workers Mailing List" Subject: RE: termcap bug on Linux Date: Wed, 30 May 2001 12:03:41 +0400 Message-ID: <000901c0e8df$0a34d700$21c9ca95@mow.siemens.ru> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) In-Reply-To: <1010530074102.ZM1290@candle.brasslantern.com> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 > > } I am not sure how useful $termcap is at all, given that there is no > } way to associate returned values with capabilities. > > I don't think I understand what you mean. I mean ${termcap} as opposed to ${termcap[some-cap]}. Plain $termcap returns array of values but you have no (easy) way to associate them with capabilities. OTOH ${(kv)termcap} could be used to scan all available values. That was what I meant. -andrej