Re: slime + clisp + emacs: server disconnects
Stuart Little <[email protected]> Tue, 23 Jul 2019 13:28:05 -0400
| Newsgroups | gmane.lisp.slime.devel |
|---|---|
| Message-ID | <20190723172805.GF9426@chirva-void> |
On Tue, Jul 23, 2019 at 06:49:50PM +0200, Pascal Bourguignon wrote: > > > On 23 Jul 2019, at 15:29, Stuart Little <[email protected]> wrote: > > > > Running M-x slime in emacs with 'inferior-lisp-program' set to 'clisp' starts slime fine. I can usually run one evaluation (like say (+ 2 3)), whereupon any other action (pressing 'enter', say) will result in a disconnect: > > > > Lisp connection closed unexpectedly: connection broken by remote peer > > > > > Add a ~/.swank.lisp file with a line such as: > > #+clisp (defparameter swank:*use-dedicated-output-stream* nil) > This did not change anything in the slime+clisp behavior I described. > > > > > (a) rlwrap clisp > > rlwrap shouldn’t be needed with clisp, since it can be compiled with readline. This is the reason why clisp is GPL! > > > (b) (load "~/quicklisp/dists/quicklisp/software/slime-v2.24/swank-loader.lisp") > > (c) (swank-loader::init :reload t) > > (d) (swank:create-server :port 7000) > > (e) from within emacs: M-x slime-connect with localhost and port 7000 > > > > Same behavior as before: I get connected, get to make a few evaluations, get disconnected. > > > > This time around rlwrap tells me (in the terminal where I started clisp): > > > > rlwrap: warning: clisp crashed, killed by SIGSEGV > > This should not occur. > > > > Since you don’t seem to have readline compiled in, perhaps you don’t have libsigsegv compiled in either? > I would advise you to recompile clisp with those essential libraries! > > Have a look at the script I currently use to compile and install clisp from sources: > https://github.com/informatimago/install/blob/master/install-pjb-environment#L399 > Don’t use this script indiscriminately, it installs a lot of things!!! Instead, copy and paste what you need. > > > > -- > __Pascal J. Bourguignon__ > > > >