From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: ZSH Workers Mailing List <zsh-workers@sunsite.dk>
Subject: Re: termcap bug on Linux
Date: Wed, 30 May 2001 15:29:58 +0000 [thread overview]
Message-ID: <1010530152958.ZM1164@candle.brasslantern.com> (raw)
In-Reply-To: <20010530100001.A27922@dman.com>
On May 30, 10:00am, Clint Adams wrote:
} Subject: Re: termcap bug on Linux
}
} I'm fine with the consistency. I just think that an unconditional
} reliance on NCURSES_VERSION being set is going to lead to trouble.
Back in 13987 you wrote:
} ncurses 4.2's tgetflag() will return ERR (-1) if called with an
} argument not found in boolcodes. ncurses 5.2's tgetflag() will return
} 0, a la Solaris.
The test in termcap.c is
#if !defined(NCURSES_VERSION) || !defined(COLOR_PAIR)
COLOR_PAIR is defined in ncurses 4.2, so apparently this behavior has
bounced back and forth with different versions of ncurses. So it looks
as if a configure test may be the safest approach, but it might be OK
to test (NCURSES_MAJOR_VERSION < 5).
I'm going to commit 14516 as it is, and then look at this a bit more.
--
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
next prev parent reply other threads:[~2001-05-30 15:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-27 13:09 Andrej Borsenkow
2001-05-28 22:25 ` Bart Schaefer
2001-05-29 16:05 ` Bart Schaefer
2001-05-29 18:56 ` Clint Adams
2001-05-30 6:24 ` Andrej Borsenkow
2001-05-30 7:41 ` Bart Schaefer
2001-05-30 8:03 ` Andrej Borsenkow
2001-05-30 14:00 ` Clint Adams
2001-05-30 15:29 ` Bart Schaefer [this message]
2001-05-30 19:54 ` PATCH (again) " Bart Schaefer
2001-05-29 18:06 ` Andrej Borsenkow
2001-05-29 20:12 ` Clint Adams
2001-05-29 18:48 ` Clint Adams
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1010530152958.ZM1164@candle.brasslantern.com \
--to=schaefer@candle.brasslantern.com \
--cc=zsh-workers@sunsite.dk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).