[Coco] Good full screen editor for NitrOS9

[Stephen H. Fischer]

Part of the problem is Nitr-/OS-9's keyboard reading and mapping.

When I was working on Colorful Sled I investigated:

Can all the ASCII characters be generated? NO

What do the keys actually produce?

Some duplicated characters, 
sometimes two or more characters are produced with one keystroke,
One key must be held down for a while to produce the NUL character and actually it repeats until the key is released. Running out of good keys I actually used that.

Solution is to do a keyboard rewrite and break oh so many programs. ;(

I think that I have the results for OS-9 ~ 1990 should someone be interested.

NOT GOOD!

There is a solution, translate the RED program that was in Dr. Dobbs about that time. 

If I was going to spend and more time on an editor RED was to be the one. 

The magazine copies are somewhere but it would take 5+ years to find them unless I was very Lucky.

SHF
 
----- Original Message ----- 
From: "Dave Philipsen" <dave at davebiz.com>
To: "CoCoList for Color Computer Enthusiasts" <coco at maltedmedia.com>
Sent: Thursday, March 23, 2017 3:53 PM
Subject: Re: [Coco] Good full screen editor for NitrOS9


>I want to do the editing right on the CoCo(3FPGA) and I don't want to 
> deal with the hassle of moving the files back and forth.  I've already 
> done that with some stuff I've worked on and it's just a pain.  I did 
> play around with a copy of MicroEMACS once on the CoCo but there were 
> some problems with key bindings or something like that as I recall.   To 
> be honest, one of my favorite editors for text files is Norton Editor 
> for DOS from a long time ago.  It's very fast and I've memorized the 
> keystrokes for common operations.  I've been using it since the early 
> 90s.  Just wish something comparable was available under NitrOS9.
> 
> Dave
> 
> 
> On 3/23/2017 4:55 PM, Bill Gunshannon wrote:
>>
>> I'll probably upset the purist here, but I find the best way is to use Drivewire to
>> move them to a PC and do any serious editing there before moving them back
>> to the COCO.  Don't get me wrong, I plan to get MicroEMACS onto my COCO
>> but I think anything is going to be size limited.
>>
>> bill
>>