Newsgroups: comp.lang.lisp
Path: cantaloupe.srv.cs.cmu.edu!das-news.harvard.edu!news2.near.net!MathWorks.Com!europa.eng.gtefsd.com!howland.reston.ans.net!xlink.net!news.ppp.de!news.Hanse.DE!lutzifer.hanse.de!wavehh.hanse.de!cracauer
From: cracauer@wavehh.hanse.de (Martin Cracauer)
Subject: Re: history mechanism (kbd) ??
Message-ID: <1994Sep26.100115.2562@wavehh.hanse.de>
Organization: The Internet
References: <35vc52$262k@yuma.ACNS.ColoState.EDU>
Date: Mon, 26 Sep 94 10:01:15 GMT
Lines: 33

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.

There are emacs interfaces. The simplest one is supplied with both
FSF-emacs-19.2x and Xemacs-19.1x.

Just type M-x run-lisp and emacs opens a window where 'lisp' lives
(run-lisp just uses the program that is called 'lisp' and is first in
you path). You can then use the usual emacs cursor movement keys to go
to previous statements and edit them. When you hit RETURN, the edited
statement is evaluated. There are special movement keys like 'C-c
C-p', but M-x describe-mode will tell you.

The emacs interface have other advantages as well. For example, you
can cut/yank between this buffer and others and you can save the
output of the whole session simply by C-x C-s.

clisp has a GNU readline-interface. It should not be that hard to add
this to gcl as well, athough nobody did this (I suggest, they found
emacs-interfaces to be superiour and didn't want to bloat their lisp
enviroment).

The listener in Harlequin Lispworks has emacs-like editing as well,
but that works only inside the graphical environment, not when running
the lisp process in a terminal. Don't know about Allegro.
-- 
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
Martin.Cracauer@wavehh.hanse.de, Fax. +49 40 5228536, German language accepted
 No guarantee for anything. Anyway, this posting is probably produced by one 
 of my cats stepping on the keys. No, I don't have an infinite number of cats.
