Re: Problem w/ ILISP 5.8 + XEmacs 20.4 + Allegro 4.3.1
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.
I have no idea where the concat problems come from, I did not see
them.
Jan
P.S. I have the feeling ilisp could do with a few '(defstruct's.
diff -u /scratch/vroonhof/cvs/xemacs-20/xemacs-packages/lisp/ilisp/ilisp-mod.el~
/scratch/vroonhof/cvs/xemacs-20/xemacs-packages/lisp/ilisp/ilisp-mod.el
--- /scratch/vroonhof/cvs/xemacs-20/xemacs-packages/lisp/ilisp/ilisp-mod.el~ Tue Jul 20
11:31:11 1999
+++ /scratch/vroonhof/cvs/xemacs-20/xemacs-packages/lisp/ilisp/ilisp-mod.el Tue Jul 20
11:31:11 1999
＠＠ -110,7 +110,7 ＠＠
(program ilisp-program)
(args (lisp-command-args program))
;; Use pipes so that strings can be long
- (process-connection-type nil)
+ ;; (process-connection-type nil)
(names (format "%s" name))
start)
(apply 'make-comint name (car args) nil (cdr args))
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.