Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.1 6/24/83; site oakhill.UUCP
Path: utzoo!linus!philabs!cmcl2!seismo!umcp-cs!gymble!lll-crg!dual!mordor!ut-sally!oakhill!don
From: don@oakhill.UUCP (Don Weiss)
Newsgroups: net.micro.trs-80
Subject: Re: TSEDIT (Info wanted)
Message-ID: <423@oakhill.UUCP>
Date: Thu, 16-May-85 03:54:49 EDT
Article-I.D.: oakhill.423
Posted: Thu May 16 03:54:49 1985
Date-Received: Fri, 17-May-85 06:19:49 EDT
References: <2005@topaz.ARPA>
Reply-To: don@oakhill.UUCP (Don Weiss)
Organization: Motorola Inc. Austin, Tx
Lines: 29

[]

TSEdit is a lot like Un*x's 'vi', at least the basic features thereof.
Since I'm used to using vi, that makes TSEdit the most natural editor
for me to use on the Coco, at least for straightforward text generation.

TSEdit is actually sold as two disks: one is for the raw (I use the term
intentionally) RadShack DOS, and the other for OS-9.  Both for the single
package price.  Not bad--especially if, like me, you have some CoCos 
running OS-9 and others running RS DOS.

TSEdit supports true lower case, at a variety of characters per line, all
the way up to 85--that's not really readable, even on my Gorilla monitor,
but it allows you to create/get a look at the form of the line to be
printed.

It creates the characters by going into the maximum resolution graphics mode
and then painting the chars. black on white or black on green (another 
option).

My only problem with it at present is that I've built up a file to just under
3500 characters, and now it gives me a warning about being out of memory
space when I load that file to do more work on it. This occurs in the OS-9
version, which I have hacked (using SDISK) to run double-sided 40T drives.
The folks in Fort Worth don't have any clues for me on this one yet; I
really have to go back and set up the same conditions for TSEdit on a
showroom-stock CoCo OS9 to see if it gives me the same problem.

Anyway, enjoy!