Path: utzoo!attcan!uunet!lll-winken!lll-tis!ames!mailrus!tut.cis.ohio-state.edu!bloom-beacon!bu-cs!purdue!decwrl!labrea!polya!weening@Gang-of-Four.Stanford.EDU
From: weening@Gang-of-Four.Stanford.EDU (Joe Weening)
Newsgroups: comp.windows.x
Subject: Re: Bug in xterm option parsing?
Message-ID: <5667@polya.Stanford.EDU>
Date: 14 Dec 88 19:13:51 GMT
References: <5644@polya.Stanford.EDU>
Sender: news@polya.Stanford.EDU
Reply-To: weening@Gang-of-Four.Stanford.EDU (Joe Weening)
Organization: Stanford University
Lines: 10
In-reply-to: weening@Gang-of-Four.Stanford.EDU (Joe Weening)

In article <5644@polya.Stanford.EDU>, I described a situation where
jump scrolling was turned on if I ran "xterm -ls", even though it was
specified to be off in the resources database.

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.

Joe Weening                                Computer Science Dept.
weening@Gang-of-Four.Stanford.EDU          Stanford University