[comp.windows.x] Bug in xterm option parsing?

weening@Gang-of-Four.Stanford.EDU (Joe Weening) (12/14/88)

I wanted to disable jump scrolling in xterm, so I put the following in
my ~/.Xres file.

xterm*jumpScroll:   off

This file is loaded by an xrdb command when I start the server.  Now,
what happens is that xterm starts with jump scrolling off unless it is
started with the "-ls" option in the command line, in which case jump
scrolling is turned on.  Any idea what causes this?
Joe Weening                                Computer Science Dept.
weening@Gang-of-Four.Stanford.EDU          Stanford University

weening@Gang-of-Four.Stanford.EDU (Joe Weening) (12/15/88)

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

eirik@tekcrl.TEK.COM (Eirik Fuller) (12/18/88)

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.