From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: "ZSH Workers Mailing List" <zsh-workers@sunsite.dk>
Subject: Re: HP-UX 11.00 tgetenv dilemma
Date: Fri, 8 Jun 2001 16:10:57 +0000 [thread overview]
Message-ID: <1010608161058.ZM2114@candle.brasslantern.com> (raw)
In-Reply-To: <000201c0efdb$80bf9790$21c9ca95@mow.siemens.ru>
On Jun 8, 9:26am, Andrej Borsenkow wrote:
}
} [Moved to zsh-workers]
}
} > 2. If the X-Open Standard is truely as HP claims, we can add
} > another #ifdef block to the existing TGETENT_ACCEPTS_NULL to
} > work with this situation. Then we link with -lcurses as the
} > current configure script does.
}
} Pretty hard to figure out automatically.
It actually shouldn't be all that difficult. (The TGETENT_ACCEPTS_NULL
configure test is already going to be wrong for this case, BTW.) If we
accept that "vt100" is sufficiently universal that it's guaranteed to
exist, which the accepts-null test seems to imply, then we just have to
do three tests:
r1 = tgetent(buffer, "vt100")
r2 = tgetent(buffer, "!@#$%^&*")
r3 = tgetent(NULL, "vt100")
If (r1 == -1) we can't access the terminfo directory and we should give
up (bail out of configure with an error?).
If (r2 == -1) then we have the wierd HP-UX-11-style tgetent(), because
otherwise it ought to be == 0 (no cap file).
If (r3 == r1) then TGETENT_ACCEPTS_NULL.
} 3. Use setupterm if compiled with curses (or just if available) and tgetent
} otherwise. The above problem should happen only on systems with terminfo and
} setupterm must be there.
Please refer to zsh-workers/14061 for my concerns about setupterm(). I
still think it may be wrong even to call it from the terminfo module, and
I don't know what we should do about use_env().
--
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-06-08 16:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20010602004009.8849.qmail@web12507.mail.yahoo.com>
2001-06-08 5:26 ` Andrej Borsenkow
2001-06-08 16:10 ` Bart Schaefer [this message]
[not found] <20010611165637.24436.qmail@web12503.mail.yahoo.com>
2001-06-11 18:24 ` Andrej Borsenkow
2001-06-11 22:52 ` Bart Schaefer
2001-06-12 10:25 ` Peter Stephenson
2001-06-12 14:25 ` Bart Schaefer
2001-06-12 16:04 ` Peter Stephenson
2001-06-13 5:00 ` Bart Schaefer
2001-06-13 5:35 ` Andrej Borsenkow
2001-06-13 13:04 ` 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=1010608161058.ZM2114@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).