-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Lisp kernel request for Allegro Common Lisp #17
Comments
I am sorry but I do not have access to ACL, hence it's difficult for me to address this issue. |
djinnome Not knowing how familiar with CL and quicklisp I'll go step by step Make sure ipython3 is installed if it isn't then you can install for Ubuntu as shown below Install quicklisp Clone the cl-jupyter repo in to the directory cd into cl-jupyter and run install script Start Allegro lisp and load cl-jupyter and exit Start ipython3 and make sure it works and so it creates the Make a directory to hold the config file for the Allegro lisp kernel Create a file called
Finally start ipython and test it out by creating a new notebook and selecting the Let me know how it goes. If you have problems I'll run down the 32 bit libs I need, or if you can get the folks at Pathway to give me a copy of their app and I will see what I can do. |
I tried the suggested procedure from @mmaul using Allegro Common Lisp's mlisp. There were, of course, issues due to mlisp being case-sensitive, which I resolved by converting a few variable names to lower case. But I got stuck trying to get the kernel to reply. There appears to be an issue with the utf-8 decoding. Here is the output I got: cl-jupyter: an enhanced interactive Common Lisp REPL [Hearbeat] starting... |
Now that allegro common lisp is 64 bit, is it more feasible to get cl-jupyter to support allegro? |
Hi Folks,
I use Pathway-tools, which uses Allegro common lisp underneath. On the other hand, if the kernel just needs to connect to a REPL through a socket, Pathway-tools already provides a Unix socket.
Sincerely,
The text was updated successfully, but these errors were encountered: