Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!bloom-beacon!ROVER.UMD.EDU!jonnyg
From: jonnyg@ROVER.UMD.EDU (Jon Greenblatt)
Newsgroups: comp.windows.x
Subject: Re: Does xterm -t normally work?
Message-ID: <8903291850.AA00784@rover.UMD.EDU>
Date: 29 Mar 89 18:50:57 GMT
Sender: daemon@bloom-beacon.MIT.EDU
Organization: The Internet
Lines: 27

> Thanks, changing my geometry specification solved the problem.  I'm surprised
> I hadn't heard talk of this before...maybe it's the case that TeK mode is
> used very seldom.  Time to renew talk of a smaller and less functional
> version of xterm with TeK mode?  It sure would be nice to not have my
                                   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> swap space filled up with xterm code that I never use.
  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>
>                                               --Peter

        I too feel that the amount of swap taken by multiple Xterms is a
crime :-) I do not feel the solution is to make Xterm smaller however.
Xterm should set a hint the first time it's executed stating a Xterm has
been started for that host-display.  All furthur calls to Xterm should cause
the original xterm to pop up a new window and do a select on additional
ttys/ptys.  Following accurances of xterm will parse the command line and
pass information to the server Xterm to set up new windows.  This is not at
all necessary if the operating system supports code sharing but
unfortionatly most don't.  In a true object oriented environment this would
be easy to do.  Since there realy is not a Xterm widget, the problem becomes
more complex.  This leads to another solution which is to add a xterm widget
to a window manager that will allow you to bring up multiple instances of
xterm from a window manager with out loading a new xterm each time.  Any
volunteers?


                                                JonnyG.