🚀 go-pugleaf

I think there is an easier way to handle the command recall issue: do it in
BIOSland/CCPland. This is what VMS sort of does (under VMS the terminal
driver itself keeps the last command line entered. DCL keeps a longer
"history", but does so thru the use the terminal driver).  What really needs
to be done is to re-write the CCP for CP/M-68K, and replace DRI's CCP.  The
next step is to invent a couple of new BIOS functions, to setup the key(s)
to invoke command line recall and editing.  Also, a function is needed to
enable/disable command line recall/editing.  The CCP (and application
programs that wish to) need a way to provide a history list mechanism.

The first step, however, is to write the alternitive CCP and get that
working. There is a technical note around (put out by DRI) about writing a
CCP for CP/M-68K. I have a copy around somewhere - I got it from Dave Gray
(dgray@uky.csnet). At some point (when I get motivated enought), I'll be
writting my own CCP.  

					Robert Heller