From: Mike (I'll think of something yet) Meyer
Subject: Re: LISPMs and UNIX
Date:
Message-ID: <24937@agate.BERKELEY.EDU>
In article <····················@pawl24.pawl.rpi.edu> ······@pawl.rpi.edu (Rodney Peck) writes:
<Well, oz, it's really hard to explain to someone why a lispm is so
<nice to program on. It's not the lisp really. It's more the
<completely integrated environment and the availability of
<documentation and source code in the editor via a keystroke. It makes
<for really fast code writing when you can say "Hey, the inspector does
<what I want to do here. I wonder how THEY did it." and then procede
<to snarf the source code and re-write parts of it for your
<application.
You mean you can't do this on your Unix systems? Documentation and
source code in a few keystrokes (well, a few words, anyway). I'd save
you've got a broken unix system.
When doing work on Unix or similar systems, I miss some of the LISP
tools. When working with LISP, I miss unix utilities. Usually when I
need to do something in one that I would normally choose to do on the
other.
My personal suspicion as to why the Unix LISP environments are
developing slowly: They realize that just pasting a LISPM
environmenton top of Unix isn't the right way to go. Since the Unix
system is there, you really want your LISP system to be able to use it
when it's a more appropriate to do so. So they're trying to produce
something where the two worlds work with instead of against each
other. This requires developing soemthing new, not just rewriting that
which already exists.
<mike
--
And then up spoke his own dear wife, Mike Meyer
Never heard to speak so free. ···@berkeley.edu
"I'd rather a kiss from dead Matty's lips, ucbvax!mwm
Than you or your finery." ···@ucbjade.BITNET