Delivery-Date: Tue, 20 Jul 1999 17:03:43 +0200
Sender: vroonhof(a)math.ethz.ch
Cc: ilisp(a)naggum.no, xemacs-beta(a)xemacs.org
From: Jan Vroonhof <vroonhof(a)math.ethz.ch>
Date: 20 Jul 1999 11:36:18 +0200
User-Agent: Gnus/5.070083 (Pterodactyl Gnus v0.83) XEmacs/21.1 (Acadia)
Content-Type: text/plain; charset=us-ascii
content-length: 1683
Marco Antoniotti <marcoxa(a)copernico.parades.rm.cnr.it> writes:
> > Having installed the inferior lisp package with xemacs 21.1-p3, I cannot get
> > ilisp to work with CLISP.
>
> If anybody has any clue about what is happening with XEmacs/ILISP,
> please let me know or write to ILISP mailing list. (for the time
> being, but not much longer, <ilisp(a)naggum.no>).
Well. I am not sure whose problem this is exactly, but for me the
problem seems to be with something (i.e. either XEmacs or Clisp[1]) not
flushing pipe buffers correctly. The patch below "fixes" the problem
for me. I can run Clisp now and evaluate "(+ 1 2)", define a function
and have it complete the function name in a call.
Thanks. I will put it in with a conditional.
I have no idea where the concat problems come from, I did not see
them.
Ok.
Jan
P.S. I have the feeling ilisp could do with a few '(defstruct's.
You are *RIGHT*! Most Elisp packages could use more DEFSTRUCTs. And
ILISP is no exception. As you may noticed I slipped in a "(require 'cl)"
in the package :) Apart from that, a rewriting of a lot of ILISP
is quite an undertaking and I do not have that much time to tackle it.
Here is one thing that I'd like to see. Actually, let's have a
REQUEST FOR IMPLEMENTATION for it. :) Next message.
Footnotes:
[1] My guess would be XEmacs. It seems suspiciously like the process
bug on NT that makes it fail to recognize the end of ftp transfers
under efs.
I wouldn't be surprised.
Marco
--
Marco Antoniotti ===========================================
PARADES, Via San Pantaleo 66, I-00186 Rome, ITALY
tel. +39 - 06 68 10 03 17, fax. +39 - 06 68 80 79 26
http://www.parades.rm.cnr.it/~marcoxa