Path: utzoo!utgpu!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!mailrus!purdue!decwrl!decvax!tektronix!tekcrl!eirik
From: eirik@tekcrl.TEK.COM (Eirik Fuller)
Newsgroups: comp.windows.x
Subject: Re: Bug in xterm option parsing?
Summary: termcap shouldn't inflict preferences
Message-ID: <3400@tekcrl.CRL.TEK.COM>
Date: 18 Dec 88 10:24:41 GMT
References: <5644@polya.Stanford.EDU> <5667@polya.Stanford.EDU>
Sender: news@tekcrl.CRL.TEK.COM
Organization: Tektronix, Inc., Beaverton,  OR.
Lines: 22

In article <5667@polya.Stanford.EDU> weening@Gang-of-Four.Stanford.EDU (Joe Weening) writes:
) ...
) I've figured out what was happening: the -ls flag causes my .login
) file to be run, and it contains a "tset" command, which sends the
) initialization string to the terminal.  This apparently includes a
) command to turn on jump scrolling.
) ...

Why is it that all of the xterm termcap entries I've seen (except the
one I wrote :-) set jump scrolling?  It seems silly to me, especially
since the correctness of the rest of the termcap depends in no way on
the setting of that option.  Some options have to be set in the
initialization string for the rest of the termcap entry to make sense,
but jump scroll isn't one of them.

Wait, let me guess, termcaps are a thing of the past anyway, so
there's no point in thinking carefully about doing them right.
Never mind ...

Actually, the last isn't as wrong as it might seem.  Most of my
.login files scattered around the network skip tset for xterm, since
resize is really what I want in that case.