jsdy@hadron.UUCP (Joseph S. D. Yao) (03/02/88)
On a heterogenous (System V / Ultrix) TCP/IP network, several people
use 'rlogin' from windows, and are surprised when the computer on the
far side believes that they have the full complement of lines and
columns. My suggested solution was to add to the third rlogin
protocol setup line (for which I can find no definition) a third
field, so it would look like:
<$TERM>/<baud-rate>/<lines>x<columns>
Since the System V terminfo uses environment variables $LINES and
$COLUMNS, we could use those on the System V machines; and we'd have
to get the Berkeley machines somehow to modify $TERMCAP based on
$LINES and $COLUMNS.
But, first, I thought I'd turn to the net and see whether anyone else
had any solutions. Has anyone else had to address this problem?
Thanks muchly. Please reply by E-mail, as I am sufficiently swamped
as not to get to these newsgroups very often.
Joe Yao jsdy@hadron.COM (not yet domainised)
hadron!jsdy@{uunet.UU.NET,dtix.ARPA,decuac.DEC.COM}
arinc,att,avatar,blkcat,cos,decuac,dtix,\
ecogong,empire,gong,grebyn,inco,insight, \!hadron!jsdy
kcwc,lepton,netex,netxcom,phw5,rlgvax, /
seismo,sms,smsdpg,sundc,uunet /wcs@ho95e.ATT.COM (Bill.Stewart.<ho95c>) (03/05/88)
In article <707@hadron.UUCP> jsdy@hadron.UUCP (Joseph S. D. Yao) writes:
:On a heterogenous (System V / Ultrix) TCP/IP network, several people
:use 'rlogin' from windows, and are surprised when the computer on the
:far side believes that they have the full complement of lines and
:columns. My suggested solution was to add to the third rlogin
[....]
:Since the System V terminfo uses environment variables $LINES and
:$COLUMNS, we could use those on the System V machines; and we'd have
:to get the Berkeley machines somehow to modify $TERMCAP based on
:$LINES and $COLUMNS.
I run into this problem with my AT&T Datakit network and 5620 window terminal.
Datakit has two separate remote login equivalents, plus "live" remote exec.
For machines with a "real" hardware interface, there's a variable called
"DKEXPORT", which is a list of the environment variables you want passed
to the remote machine on remote login and remote execution. So I set
DKEXPORT="TERM,LINES,COLUMNS,WHATEVER"
and the current value of those variables is set in the remote environment.
For machines that only have RS-232 connections, you get a "cu" equivalent,
with no special support. When I'm talking to one of them, my .profile
prints an escape sequence that the terminal program responds to with
LINES=xx; COLUMNS=yy; export LINES COLUMNS
which is boring but almost always enough, and offeres a csh-variant.
Neither of these programs tells the remote system to set the various
ioctl modes associated with the windowing terminal, but the most
applications look for the environment variables first.
--
# Thanks;
# Bill Stewart, AT&T Bell Labs 2G218, Holmdel NJ 1-201-949-0705 ihnp4!ho95c!wcsron@TOPAZ.RUTGERS.EDU (Ron Natalie) (03/06/88)
4.3 already has a way to deal with this. Why don't you look there. -Ron
peter@nuchat.UUCP (Peter da Silva) (03/07/88)
The right thing to do for this one is to have the terminal program send a NEWSIZE escape sequence to the application when you resize the window. Something like "\E[%d;%dZ". After the application has sent a newsize-on sequence to the terminal program, of course. The terminal should probably send one newsize message immediately upon receiving that message to get things synched up right in the first place. Flames always welcome :->. -- -- a clone of Peter (have you hugged your wolf today) da Silva `-_-' -- normally ...!hoptoad!academ!uhnix1!sugar!peter U -- Disclaimer: These aren't mere opinions... these are *values*.