Re: microemacs with gno

[nathan@cco.caltech.edu (Nathan Mates)]

In article <nandu.173.000FFCB9@anest4.anest.ufl.edu>,
Nandu S. Shah <nandu@anest4.anest.ufl.edu> wrote:
>>devernay@sophia.inria.fr (Frederic Devernay) writes:
>>>is anybody using microemacs 3.12 under GNO?
>>  To get it to work okay, just do:

>>chtyp -a \$DC00 emacs

>This is how I currently have my microEMACS set up, but the result is I can't 
>^z out of it.  Do I just have to settle, or is there another solution (anyone 
>who tells me to learn to use vi will be slapped :) ?

   Changing the auxtype to $DC00 forces GNO to relinquish its
interception of certain characters (^Z, ^C, everything else) before
programs get ahold of them. This is a side effect of GNO's turning
off all of its other things, such as the GNO cursor. This is necessary,
becasue before GNO came around, the TextTools were rather slow and
inefficient compared to self-written i/o routines. (For example, the
routines for my CDAs can slam a full 80x24 screen at about 30-60 fps
on my 9/32. Using TextTools, it takes .5 second to do the same job)

   Therefore, programs like Edit-16, MicroEMACS, and others that go
directly to the hardware need to have the GNO i/o to the hardware turned
off, or they'll slug it out on your screen. There's no real easy way
to reliably intercept all keys and parse them (say ^Z), suspend some
app, then resume it later with the screen exactly as before. [I'm
thinking of a few ways in which it might be done, but it'd be a real
hack.] This auxtype method is a simple and direct solution, even
though not everyone likes the results.

>I mainly want a text editor for writing Lisp programs, and what I
>really like to do is have my editor & XLisp running concurrently &
>switch between them.  My best solution so far (which really isn't all
>that bad, come to think of it) is to use ShadowWrite under drwm & do
>my Lisping in a TMTerm window...

   (Hint: 70 columns. Not 79). That's as good as you can do without
something suspendable, like vi. If anyone has the full source to
MicroEmacs, how hard would it be to undo the hardware i/o hacks and
make it fully gno compliant? This would also let it be run on
things like dumb terminals (You wanna do direct hardware access to
the 386/16 on my desk connected via serial? Hahahah :), and all.

   Followups to c.s.a2.gno; this is getting rather gno-specific,
and not relevant to everyone.

Nathan Mates



-- 
* Nathan Mates   http://www.ugcs.caltech.edu/~nathan/               *
* Ftp humor archiver: ftp to cco.caltech.edu, look in pub/humor     *
* "Always listen to experts. They'll tell what can't be done, and   *
*  why. Then do it."  -- Robert A. Heinlein, Lazarus Long           *