Re: CLISP EMACS SWANK remote connection crash

On Wed, 4 Sep 2019 at 04:07, Vladimir Sedach <[email protected]> wrote:

>
> > * If any one reading can provide me with a link/instructions to obtain
> the
> > latest 'bleeding edge'  version for CLISP, I will attempt using that and
> > see if anything might fix ? *
>
> The CLISP source code repository is at:
>
> https://gitlab.com/gnu-clisp/clisp
>
> I built mine with these configure options (--with-module=asdf seems
> to be important to get ASDF3 to load properly later):
>
> ./configure --with-module=asdf --with-module=rawsock
>
> > If adding in the following to .emacs (at the bottom of the above listing)
> > ie. just following instructions, then the unexpected disconnection
> happens
> > again if a form is entered producing an error.  The REPL however now does
> > have all the code completion functions and ring buffer working:
> >
> > (setq slime-contribs '(slime-repl))
>
> The error you posted (SOCKET:SOCKET-STATUS on #<INPUT
> STRING-INPUT-STREAM> is illegal) seems like it might be coming from
> SLIME, particularly the debugger part of SWANK.
>

Just to check accuracy, was it was someone else and not me, that posted
finding an error.


> I have slime-20190724.1352 from ELPA, and CLISP built from source
> (master at commit dd4036936 from 2019-07-01) on Debian, and the
> debugger works without error.
>
> One of the things you can try is getting the latest SLIME from ELPA,
> or from the source code repository: https://github.com/slime/slime
>
> Vladimir
>

I thought that I had mentioned having tried ELPA  etc.; I tried both
quicklisp and [M]ELPA configs for hooking up CLISP/EMACS/SLIME.

I have downloaded CLISP from the 'gitlab' link you supplied and tried it,
but the same issue persists. Perhaps it is something to do with using the
SlackBuild on Slackware and something not building correctly. That build
pulls in  a, libffcall-2.1.tar.lz package  (libffcall v2.1) and seems to
use a patch elsewhere too, so could anything in that have an effect in
unexpected disconnections during REPL error handling I wonder.

What I do see, as mentioned previously, is that if I remove , (setq
slime-contribs '(slime-repl)) or (add-to-list 'slime-contribs 'slime-repl)
, from, .emacs , then the error handling disconnections do not happen.
Putting either of those slime-contribs back in (which seems to deliver more
features to the  ring-buffer functions) does cause the disconnection when
error handling [for an incorrect form].  That is not  major thing to not
have - the ring buffer works for the session but history is lost between
sessions without those forms in, .emacs - and perhaps the 'solution' for
now is to do without.

I do have something working, therefore not now so important. I feel I didnt
have this with previous versions of CLISP/EMACS/SLIME, but cannot say for
sure now after various package changes etc.

Thank you again. Best wishes.

_______________________________________________
clisp-list mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/clisp-list