From: a normal guy <ee_in_co@yahoo.com>
To: zsh-users@sunsite.dk
Subject: HP-UX 11.00 tgetenv dilemma
Date: Fri, 1 Jun 2001 17:40:09 -0700 (PDT) [thread overview]
Message-ID: <20010602004009.8849.qmail@web12507.mail.yahoo.com> (raw)
Hello:
I have been championing zsh here at my lab at HP and love this
shell. Up until recently we were using HP-UX 10.20 with zsh
3.1.9 with no problems. However, when we upgraded to HP-UX
11.00, the termcap compatibility was broken. I finally
figured out the problem.
HP-UX 11.00 has two man pages discussing tgetent. 'man termcap'
says:
=======================================================(quote)
:
tgetent() ...tgetent() returns -1 if it cannot
access the terminfo directory, 0 if there is no
capability file for name, and 1 if all goes
well.
:
=======================================================(unquote)
but 'man tgetent' says
=======================================================(quote)
:
RETURN VALUE
Upon successful completion, functions that return an
integer return OK(0). Otherwise, they return ERR(-1).
Functions that return pointers return a null pointer on
error.
:
=======================================================(unquote)
The code in init.c, init_term() requires the man termcap
functionality. HP claims that the man tgetent functionality is
the true X-Open Standard. (I have not confirmed this.)
We can solve the problem in two ways.
1. If we link with -lHcurses, we get tgetent to return the
expected 1 with success. I suppose this would be done in the
configure script. This library may not be around for the
future.
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.
If possible, I would appreciate a fix in the next release
(either 3.1.x or 4.0.x).
Thanks
Scott
__________________________________________________
Do You Yahoo!?
Get personalized email addresses from Yahoo! Mail - only $35
a year! http://personal.mail.yahoo.com/
reply other threads:[~2001-06-02 0:40 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20010602004009.8849.qmail@web12507.mail.yahoo.com \
--to=ee_in_co@yahoo.com \
--cc=zsh-users@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).