>
> > Another thing that does not work is "sage -
> > lisp" which gave the clisp prompt. I found this rather convenient
> > since I could just use the clisp within sage. Is there any plan/
> > interest to switch the this lisp interface to ecl? Does ecl use
> > readline?
>
> For now you can at least start sage then type
>
> sage: !ecl
>
> to start ecl. It appears to not make any use of ecl. I don't know if
> this is just
> a compilation problem or an ecl limitation.
>
Thanks, I forgot about that way to do it. The lack of readline makes
it rather unfriendly though. I am just a beginner with lisp myself.
> The Sage <--> lisp interface already works fine:
>
> sage: lisp.eval('(+ 2 3)')
> '5'
>
Using 4.0 and 4.0.1 I get a long traceback that ends with:
RuntimeError: Unable to start Lisp because the command 'clisp-
noreadline --silent -on-error abort' failed.
Sage was compiled from source on Scientific Linux 5.1. I don't have a
global clisp available though.
I figured that it was something that had just not been looked at yet
in the transition to ecl.
Adam
> I'm not sure why %gap works but not %lisp:
>
> sage: %lisp
> ERROR: Magic function `lisp` not found.
> sage: %gap
> --> Switching to Gap <--
> gap:
>
> That should be consider a bug.
>
> OK, two tickets:
>
> (1) make "sage -lisp" run ecl:
> http://trac.sagemath.org/sage_trac/ticket/6287
>
> (2) make %lisp work and run ecl + readline
> mode:http://trac.sagemath.org/sage_trac/ticket/6288
>
> -- William
--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~----------~----~----~----~------~----~------~--~---
