🚀 go-pugleaf

In article <1993Jan21.121423.10420@ac.dal.ca> cordes@ac.dal.ca (John Cordes) writes:
-> In article <3_800_842_fidonet2b57bb25@Kralizec.fido.zeta.org.au>, michael.smith@f842.n800.z3.fido.zeta.org.au (michael smith) writes:
-> > Original to: ken@isgtec.com
-> > In a message of <10 Jan 93 05:43:54>, ken@isgtec.com (3:713/602) writes:
-> > 
->    <material deleted>
-> 
-> > If you only have an ST, use Uniterm, you don't have the speed or need for
-> > anything more.
-> > 
-> > If you have a Mega STe, an accelerated ST, or a TT, use either STalker
-> > (whose VT100 is pretty good when you set it up right, particularly if you
-> > disable it's default behaviour of clearing the history buffer on a
-> > clear-home) or CoNnect, which is as close to flawless as I have ever seen a
-> > terminal emulator get.
-> > 
->   I like STalker very much, but I do find the occasional clearing of the 
-> history buffer to be a nuisance. It seems to me that Eric R./Gribnif 
-> claimed that it would be too hard to detect the control sequences that do 
-> that, when running in VT100 mode; do you know of a way to overcome the 
-> problem? Thanks.
-> 
-> John

	Both of those are good for some circumstances.  If you dial in
to a Unix system on a regular basis, use the ST Unix Windows client.
It lets you open several terminals at one time and takes better
advantage of the Unix system.  The only problem is if you have a low
bandwidth modem, one window producing a lot of output will make the
others really slow.  The client and server side of Unix Windows is
available through anonymous ftp, but I don't remember what sites right
now.  I've only run this on my 1040, so I have no idea if it works on
newer Atari machines.

--
Jason C. Austin
j.c.austin@larc.nasa.gov