From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6977 invoked from network); 30 May 2001 06:24:57 -0000 Received: from sunsite.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 30 May 2001 06:24:57 -0000 Received: (qmail 19673 invoked by alias); 30 May 2001 06:24:42 -0000 Mailing-List: contact zsh-workers-help@sunsite.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 14556 Received: (qmail 19662 invoked from network); 30 May 2001 06:24:41 -0000 X-Envelope-Sender-Is: Andrej.Borsenkow@mow.siemens.ru (at relayer david.siemens.de) From: "Andrej Borsenkow" To: "ZSH Workers Mailing List" Subject: RE: termcap bug on Linux Date: Wed, 30 May 2001 10:24:37 +0400 Message-ID: <000001c0e8d1$33b431b0$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: <1010529160507.ZM13557@candle.brasslantern.com> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 > > On May 28, 10:25pm, Bart Schaefer wrote: > } > } Does the following patch help? > } > } Does something similar need to go into scantermcap() ? > > Should I commit the patch? > Yes. About scantermcap - I am not sure. Currently it returns "no" for both unexisting and unset flags; if we change this as well, it will return nothing for unexisting flags. I am not sure how useful $termcap is at all, given that there is no way to associate returned values with capabilities. Two possible valid usages are ${(k)termcap} or ${(kv)termcap}. For consistency, I'd suggest to change scantermcap as well but I do not insist.Clint? -andrej