Newsgroups: comp.lang.lisp
Path: cantaloupe.srv.cs.cmu.edu!nntp.club.cc.cmu.edu!godot.cc.duq.edu!news.duke.edu!news-feed-1.peachnet.edu!emory!nntp.msstate.edu!olivea!news.bu.edu!gw1.att.com!nntpa!nntpa.cb.att.com!lgm
From: lgm@polaris.ih.att.com (Lawrence G. Mayka)
Subject: Re: history mechanism (kbd) ??
In-Reply-To: barmar@nic.near.net's message of 23 Sep 1994 16:47:29 -0400
Message-ID: <LGM.94Sep25114205@polaris.ih.att.com>
Sender: news@nntpa.cb.att.com (Netnews Administration)
Nntp-Posting-Host: polaris.ih.att.com
Organization: AT&T Bell Laboratories, Naperville, Illinois, USA
References: <35vc52$262k@yuma.ACNS.ColoState.EDU> <35vet1$52j@tools.near.net>
Date: Sun, 25 Sep 1994 16:42:05 GMT
Lines: 31

In article <35vet1$52j@tools.near.net> barmar@nic.near.net (Barry Margolin) writes:

   From: barmar@nic.near.net (Barry Margolin)
   Newsgroups: comp.lang.lisp
   Date: 23 Sep 1994 16:47:29 -0400
   Organization: NEARnet, Cambridge, MA

   In article <35vc52$262k@yuma.ACNS.ColoState.EDU> petersod@carter.cs.colostate.edu ( david peterson) writes:

   >Is there some form of a history mechanism for the different 
   >implementations of Common Lisp?  I'm currently using AKCL but will
   >be using Allegro in the near future as well - so I'm interested 
   >in this capability for both.

   Except for Lisp Machines, I don't know of any Lisp systems that have a
   built-in, Emacs- or vi-style history mechanism.  In general, Lisp vendors
   have been implementing this by running Lisp from Emacs buffers and
   providing Emacs enhancements to interface with the Lisp process.

Harlequin LispWorks has :HIS, :REDO, and :USE commands that view,
reapply, and modify previous entries in the command history, but I
never use them because the LispWorks Listener provides a far more
hospitable environment for top-level interaction.  Even those who
occasionally don't use the full LispWorks environment use the GNU
Emacs interface instead of raw TTY-style interaction.
--
        Lawrence G. Mayka
        AT&T Bell Laboratories
        lgm@ieain.att.com

Standard disclaimer.
