[16620] in Athena Bugs
Re: listmaint needs curses?
daemon@ATHENA.MIT.EDU (Aaron M. Ucko)
Tue Jan 19 00:19:21 1999
To: Dan Winship <danw@MIT.EDU>
Cc: John Hawkinson <jhawk@MIT.EDU>, bugs@MIT.EDU, bug-moira@MIT.EDU
From: amu@MIT.EDU (Aaron M. Ucko)
Date: 19 Jan 1999 00:19:14 -0500
In-Reply-To: Dan Winship's message of "Mon, 18 Jan 1999 16:32:37 EST"
<danw@MIT.EDU> (Dan Winship) writes:
> This appears to be caused by an "undocumented feature" of System V.
> The moira client has code to fall back to -nomenu if curses
> initialization fails, but SysV initscr() calls exit() if it doesn't
> like your TERM setting. Have A Nice Day.
Uh, it looks documented to me:
screen. If errors occur, initscr() writes an appropriate
error message to standard error and exits; otherwise, a
pointer is returned to stdscr(). If the program needs an
indication of error conditions, newterm() should be used
instead of initscr(); initscr() should only be called once
per application.
A program that outputs to more than one terminal should
use the newterm() routine for each terminal instead of
initscr(). A program that needs an indication of error
conditions, so it can continue to run in a line-oriented
mode if the terminal cannot support a screen-oriented pro=AD
gram, would also use this routine.
--
Aaron M. Ucko, KB1CJC <amu@mit.edu> (finger amu@monk.mit.edu)
