Debian bug report logs -
#1677, boring messages
Message sent to debian-devel@pixar.com:
Subject: Bug#1677: tgetent() returns unexpected error return codes
Reply-To: Bill Mitchell <mitchell@mdd.comm.mot.com>, debian-bugs@pixar.com
Resent-From: Bill Mitchell <mitchell@mdd.comm.mot.com>
Resent-To: debian-devel@pixar.com
Resent-Date: Sat, 14 Oct 1995 17:48:02 GMT
Resent-Message-ID: <debian-bugs-handler.1677.B10141745370@pixar.com>
Resent-Sender: iwj10@cus.cam.ac.uk
X-Debian-PR-Package: ncurses-developer, git
X-Debian-PR-Keywords:
Received: via spool for debian-bugs; Sat, 14 Oct 1995 17:48:02 GMT
Received: with rfc822 via encapsulated-mail; Sat, 14 Oct 1995 17:45:37 GMT
Received: from pixar.com by mongo.pixar.com with smtp
(Smail3.1.28.1 #15) id m0t4AdL-000ETRC; Sat, 14 Oct 95 10:44 PDT
Received: from motgate.mot.com by pixar.com with SMTP id AA04192
(5.67b/IDA-1.5 for debian-bugs-pipe@mongo.pixar.com); Sat, 14 Oct 1995 10:38:13 -0700
Received: from pobox.mot.com (pobox.mot.com [129.188.137.100]) by motgate.mot.com (8.6.11/8.6.10/MOT-3.8) with ESMTP id LAA18032 for <debian-bugs@pixar.com>; Sat, 14 Oct 1995 11:09:06 -0500
Received: from mdd.comm.mot.com (mdisea.mdd.comm.mot.com [138.242.64.201]) by pobox.mot.com (8.6.11/8.6.10/MOT-3.8) with SMTP id LAA19116 for <debian-bugs@pixar.com>; Sat, 14 Oct 1995 11:09:05 -0500
Received: from bb29c.mdd.comm.mot.com by mdd.comm.mot.com (4.1/SMI-4.1)
id AA22957; Sat, 14 Oct 95 09:09:02 PDT
Received: by bb29c.mdd.comm.mot.com (4.1/SMI-4.1)
id AA03278; Sat, 14 Oct 95 09:09:00 PDT
Date: Sat, 14 Oct 1995 09:08:59 -0700 (PDT)
From: Bill Mitchell <mitchell@mdd.comm.mot.com>
X-Sender: mitchell@bb29c
To: debian-bugs@pixar.com
Message-Id: <Pine.SUN.3.91.951014085057.3266A@bb29c>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
PACKAGE: ncurses-developer, git
VERSION: 1.9.4-0, 2.3.7-3
I'm not a curses programmer, but I maintain the git package,
which uses libncurses. I see that the termcap(3ncurses)
man page says:
RETURN VALUE
Routines that return an integer return ERR upon failure
and OK (SVr4 only specifies "an integer value other than
ERR") upon successful completion.
However, I also see that the SunOS curses(3X) man page says:
tgetent() extracts the entry for terminal name into the bp
buffer, with the current size of the tty (usually a window).
This allows pre-SunWindows programs to run in a window of
arbitrary size. bp should be a character buffer of size
1024 and must be retained through all subsequent calls to
tgetnum(), tgetflag(), and tgetstr(). tgetent() returns -1
if it cannot open the termcap() file, 0 if the terminal name
given does not have an entry, and 1 if all goes well. It
will look in the environment for a TERMCAP variable. If
found, and the value does not begin with a slash, and the
terminal type name is the same as the environment string
TERM, the TERMCAP string is used instead of reading the
termcap file. If it does begin with a slash, the string is
used as a path name rather than /etc/termcap. This can
speed up entry into programs that call tgetent, as well as
to help debug new terminal descriptions or to make one for
your terminal if you cannot write the file /etc/termcap.
Note: if the window size changes, the ``lines'' and
``columns'' entries in bp are no longer correct. See the
SunView 1 Programmer's Guide for details regarding [how to
handle] this.
and this SunOS-style (BSD?) behavior is what is expected by the
git(1) code. This results in a misleading error message from git(1)
if a terminal is specified which cannot be found in the database.
I imagine that other software probably expects this behavior as
well.
Is there any chance of ncurses being enhanced to return SunOS-style
return values, or should I modify the git package for compatability
with the current, less informative, SVr4-style return values and
submit the change to the git author?
mitchell@mdd.comm.mot.com (Bill Mitchell)
Message sent:
From: iwj10@thor.cam.ac.uk (Ian Jackson)
To: Bill Mitchell <mitchell@mdd.comm.mot.com>
Subject: Bug#1677: Acknowledgement (was: tgetent() returns unexpected error return codes)
In-Reply-To: <Pine.SUN.3.91.951014085057.3266A@bb29c>
References: <Pine.SUN.3.91.951014085057.3266A@bb29c>
Thank you for the problem report you have sent regarding Debian GNU/Linux.
This is an automatically generated reply, to let you know your message has
been received. It is being forwarded to the developers' mailing list for
their attention; they will reply in due course.
If you wish to submit further information on your problem, please send
it to debian-bugs@pixar.com, but please ensure that the Subject
line of your message starts with "Bug#1677" or "Re: Bug#1677" so that
we can identify it as relating to the same problem.
Please do not reply to the address at the top of this message,
unless you wish to report a problem with the bug-tracking system.
Ian Jackson
(maintainer, debian-bugs)
Ian Jackson /
iwj10@thor.cam.ac.uk,
with the debian-bugs tracking mechanism