[Coco] Is there a good, runs on a coco but from a terminal like /t2 editor?

[gene heskett]

On Sunday, November 21, 2010 12:24:42 pm Michael Furman did opine:

> Oh.  That's PVIC.
> 
> I'm not sure if I got the code from RTSI or somewhere else, but I have
> PVIC compiled for the coco using the ported version of Microware CC on
> my Mac.  Problem is that the resulting binary even after going through
> the optimizer is 63k.  I have no idea if it works or not.  I never got
> around to removing features from it to make it smaller.  Maybe it's
> time I get back to this one.
> 
Yikes!  considering the tsedit->vi conversion is:
  0  2008/05/13 21:00  --e-rewr    6B08      1B01 ed
That is 6,913 bytes decimal.
(I had to rename it from vi because nitros9 thinks vi is a device 
descriptor)

Now if I could just find the sources for tsedit and the patch, I could fix 
this.  Or if I could establish a translation in the minicom screen 
interface between what it does to the screen so that it worked the same on 
my screen as it does on the coco screen.  One or the other.  The only thing 
I'm doing now is the eof conversions so that a dir listing looks the same.

Unforch, I haven't a clue how to go about that.  minicom has onl;y two 
modes, VT-102 and ANSI.  But while that works for displaying a dir listing, 
or launching a session of sz, that conversion of eof's doesn't work for 
editing as the files text is displayed on one long line that minicom doesn't 
even line wrap.

Maybe there's a better linux terminal program?  putty maybe? No, its a 
bust, as is 'terminal'...  Repeat for ETerm...   Looks like minicom is the 
only REAL terminal, everything else appears to be locked to the xwindow 
system for its I/O.

Time for more studying of options I guess.


-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
"I'd love to go out with you, but I have to floss my cat."