Path: utzoo!attcan!uunet!lll-winken!csd4.milw.wisc.edu!uxc!iuvax!emo
From: emo@iuvax.cs.indiana.edu (Eric Ost)
Newsgroups: comp.windows.x
Subject: Re: Does xterm -t normally work?
Message-ID: <18991@iuvax.cs.indiana.edu>
Date: 28 Mar 89 19:03:55 GMT
References: <34700008@primerd> <8903271533.AA04533@EXPIRE.LCS.MIT.EDU> <54940@yale-celray.yale.UUCP>
Reply-To: emo@iuvax.cs.indiana.edu (Eric Ost)
Organization: Indiana University, Bloomington
Lines: 24

If you check your .Xdefaults you will find you are specifying a binding
for the xterm ``geometry'' object/resource.  It will probably look something
like:

xterm*geometry:	  80x24+5+5

You will get the same behavior if you were to fire up xterm and then 
select Tek mode from the menu or via the appropriate character control 
sequence.  This bug is inherent in "xterm".  What I think is happening
is because the geometry specification is general, i.e. a very "weak"
binding, xterm will try to open the Tek window with that geometry and
fail for some reason.  I have not tracked the bug down and fixed it yet.
If someone else has done this, please let us all know.

The ``fix'' is to remove the specification of the xterm geometry from your
.Xdefaults file.  Or, else make it more specific.  You probably are using
it to specify the default geometry of the xterm VT window, so use:

xterm*VT*geometry: 80x24+5+5

which will no longer match with the default geometry for the Tek window.
After installing this syntax, you will be able to "xterm -t".

eric