Path: utzoo!mnetor!uunet!husc6!cmcl2!brl-adm!umd5!purdue!i.cc.purdue.edu!j.cc.purdue.edu!pur-ee!uiucdcs!uxc.cso.uiuc.edu!kline
From: kline@uxc.cso.uiuc.edu
Newsgroups: comp.windows.x
Subject: Re: termcap entry for xterm
Message-ID: <194900003@uxc.cso.uiuc.edu>
Date: 17 Feb 88 02:41:00 GMT
References: <638@sandino.quintus.UUCP>
Lines: 30
Nf-ID: #R:sandino.quintus.UUCP:638:uxc.cso.uiuc.edu:194900003:000:1277
Nf-From: uxc.cso.uiuc.edu!kline    Feb 16 20:41:00 1988


/* Written  9:14 am  Feb 14, 1988 by bob@triceratops.cis.ohio-state.edu */
>In article <638@sandino.quintus.UUCP> pds@quintus.UUCP (Peter Schachte) writes:
>
>>...It would be nice if I could resize the xterm window after it was
>>created, too, if possible.
>
>Look at resize, which can be used to change the physical size of the
>xterm window and make corresponding changes to TERMCAP all in one
>swell foop.  The manual page suggests a couple of csh aliases for
>commands to use to resize xterm windows.  I use things like "xrs 37
>92" with no problem at all.

If you have a 4.3-compatible tty driver and at least xterm 2.2, xterm
set the tty driver's row and column attributes on a resize. Vi and more
and several other programs look at those attributes when figuring out
the terminal size. Some, however, don't. Also, xterm will send a SIGWINCH
signal to the controlling process. If the controlling process is vi, it
will understand this signal and change its own notion of screen size,
repainting the window in the process. It's pretty slick, actually.


> Bob Sutterfield, Department of Computer and Information Science


-----
Charley Kline, University of Illinois Computing Services
kline@tuna.cso.uiuc.edu
kline@uiucvmd.bitnet
{ihnp4,uunet,pur-ee,convex}!uiucuxc!kline