You should do like this:
(ql:quickload '(:lem-ncurses :swank))in SBCL REPL
(swank:create-server)in SBCL REPL
(lem:lem)in SBCL REPL, then lem will be started
after this, you can see lem's symbols via Emacs slime!
ros install lemand then
caught 1 fatal ERROR conditionvince/bacasable/asdf-sphinx-test/asdf.asd" and have an older version of ASDF (and older than 2.27 at that)
asdf-sphinx-test directory does NOT exist O_o
I tried a
(BTW this error and the backtrace are displayed in the ncurses window, unusable then. I expected it to be on stdout)
SLIME is a client-server protocol, CL library (called SWANK) and Emacs extension to communicate with CL process.
Lem is Emacs reimplemented in Common Lisp. You can play with REPL connected to the Lem itself, or connect to a separate CL process, running SLIME server.
There is also SLIME's fork called SLY (https://github.com/joaotavora/sly) which has cool features. I prefer SLY, but Lem is unable to connect to the CL process running SLYNK server (analog of SLIME's SWANK).
Well done for the new release, Lem developers!
I will party with you, even though I'll remark that there is no release notes in the Github release and that the Changelog was last changed 9 months ago ;)
(you added a shell mode? Nice. What does it do?)
A point on documentation I wanted to raise earlier: what about saying in the README that Lem supports other programming languages? I'd send a PR but I don't know enough their support status, and I'd send a big PR which may not be of the taste of Lem developers :p
While I'm at it. I'd love to see more self-documenting features in Lem, à la Emacs. If there are some, they are not documented, so it slows Lem adoption down. Would it help to sponsor this specific issue on OpenCollective?
I'd like to support @vinderl here.
Yet, I think it might be useful to set up a separate quicklisp distribution for Lem plugins. I easily create such distribution at Ultralisp.org (recently I already did the same for LispWorks extensions (https://ultralisp.org/dists/lispworks).
This way people will have a place to share Lem plugins. And it will be easy to make a
(setf documentation)to switch the docstring language when called?
sbcl --core mycore, is it possible to tell Roswell to use a custom core image inside a script, somewhere in
exec ros -Q -- $0 "$@"? The idea would be that one can build a core image with several libraries already loaded, so the script starts faster. Now how would Roswell know how to build the image, so that the script is still portable? That's something else… (maybe it could be installed separately with
ros install mycore) I answered that
ros buildis here to speed scripts up by building an executable (but consequently, we loose a little bit of ease of use a script offers).