Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!caip!seismo!styx!CSNET-RELAY.ARPA!HELLER%cs.umass.edu
From: HELLER%cs.umass.edu@CSNET-RELAY.ARPA (Stride 440 User)
Newsgroups: mod.computers.68k
Subject: CP/M-68K command history mechanisms
Message-ID: <8607012134.AA05887@ucbvax.Berkeley.EDU>
Date: Mon, 30-Jun-86 09:29:00 EDT
Article-I.D.: ucbvax.8607012134.AA05887
Posted: Mon Jun 30 09:29:00 1986
Date-Received: Wed, 2-Jul-86 06:14:08 EDT
Sender: daemon@styx.UUCP
Organization: The ARPA Internet
Lines: 17
Approved: info-68k@ucbvax.berkeley.edu

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