Zsh Mailing List Archive Messages sorted by: Reverse Date, Date, Thread, Author

Re: echotc

X-seq: zsh-workers 1025
From: Zoltan Hidvegi <hzoli@xxxxxxxxxx>
To: A.Main@xxxxxxxxxxxxxxxxx (Zefram)
Subject: Re: echotc
Date: Thu, 9 May 1996 02:21:57 +0200 (MET DST)
Cc: zsh-workers@xxxxxxxxxxxxxxx
In-reply-to: <28623.199605082113@xxxxxxxxxxxxxxxxxxxxxxx> from Zefram at "May 8, 96 10:13:30 pm"
Organization: Dept. of Comp. Sci., Eotvos University, Budapest, Hungary
Phone: (36 1)2669833 ext: 2667, home phone: (36 1) 2752368

> In 2.6-beta17, echotc doesn't work properly on string properties.  It
> outputs "no", as if the property didn't exist.  Numeric and boolean
> properties work correctly, and the strings are used correctly in prompt
> sequences such as %s.  beta16 works correctly.  This is on SunOS 4.

This can only happen if NCURSES_VERSION but you do not link zsh with
ncurses or if your ncurses behaves differently than mine.  I use 1.9.8a
and it the tgetflags function there returns 1 if a boolean capability is
on, 0 if it is off and -1 if there is no boolean capability with that
name.  We can add checks for older ncurses'es if necessary.

Zoltan

Follow-Ups:
- Re: echotc
  - From: Zefram

References:
- echotc
  - From: Zefram

Messages sorted by: Reverse Date, Date, Thread, Author