Newsgroups: comp.sources.d
Path: utzoo!telly!eci386!woods
From: woods@eci386.uucp (Greg A. Woods)
Subject: Re: Screen 2.0 change
Message-ID: <1991Mar19.164204.21361@eci386.uucp>
Reply-To: woods@eci386.UUCP (Greg A. Woods)
Organization: Elegant Communications Inc.
References: <1991Mar14.203404.21113@jato.jpl.nasa.gov>
Date: Tue, 19 Mar 91 16:42:04 GMT

In article <1991Mar14.203404.21113@jato.jpl.nasa.gov> hyc@hanauma.jpl.nasa.gov (Howard Chu) writes:
> It's not as flexible to use now that SunOS has gone to terminfo for their
> curses implementation. Mebbe someone can add code to compile terminfo
> definitions on the fly, the way this constructs termcap entries?

I don't mean to flame Oliver (or Howard), but I suspect someone has
mis-interpreted how curses and/or terminfo/termcap should be used.

Why do you say screen is less flexible when using terminfo?  Why
change the terminal definition on the fly?  If all it's changing are
the lines/cols, why not set up environment variables (LINES/COLUMNS
are recognized by most sane termcap/termlib implementations) (in
addition to setting the lines/cols in the driver)?

The layers terminal I'm on works fine with different sized windows.
There's magic in termlib that knows about the JWIN ioctl(), and
termlib also knows about LINES/COLUMNS.  The only problem is that SYSV
doesn't have a SIGWINCHG and terminfo curses can't change the window
size on the fly (without doing an endwin();initscr() sequence).
Actually, what I'd really like is for wrefresh() to notice the changed
size (i.e. do a JWIN or TCIOGWINSZ(?)) and automatically "do the right
thing".
-- 
							Greg A. Woods
woods@{eci386,gate,robohack,ontmoh,tmsoft}.UUCP		ECI and UniForum Canada
+1-416-443-1734 [h]  +1-416-595-5425 [w]  VE3TCP	Toronto, Ontario CANADA
Political speech and writing are largely the defense of the indefensible-ORWELL