slime-devel

slime-devel@common-lisp.net

4231 discussions

Start a nNew thread

how to show return values of function in minibuffer?
by Travis Zhang 26 Oct '20

26 Oct '20

Is it possible to let SLIME deduce the return type of a function and show it in the minibuffer?

1 0

Slime not loading in Aquamacs
by Jan＠ziggo 14 Aug '20

14 Aug '20

I installed Clozure CL, Aquamacs 3.5 and Slime (through Melpa), made installation settings, but after M-x slime get following message: (progn (load "/Users/jvdsmacbook/Library/Preferences/Aquamacs Emacs/Packages/elpa/slime-20200721.1604/swank-loader.lisp" :verbose t) (funcall (read-from-string "swank-loader:init") :from-emacs t) (funcall (read-from-string "swank:start-server") "/var/folders/96/cxqfcbbx0n38n20x9hss8yxr0000gn/T/slime.27376")) Clozure Common Lisp Version 1.11.5/v1.11.5 (DarwinX8664) For more information about CCL, please see http://ccl.clozure.com. CCL is free software. It is distributed under the terms of the Apache Licence, Version 2.0. ? ;Loading #P"/Users/jvdsmacbook/Library/Preferences/Aquamacs Emacs/Packages/elpa/slime-20200721.1604/swank-loader.lisp"...sigreturn returned ? for help [27385] Clozure CL kernel debugger: I do not see SLIME and REPL in the topbar of Aquamacs. Any idea what may be wrong?

2 1

make-network-process timing out when connecting swank server
by Mirko Vukovic 20 Apr '20

20 Apr '20

Hello, This is a follow-up to a thread that I started a few weeks back (What are port requirements for remote lisp?). I run Msys2's Emacs on a corporate laptop running windows 10, and I don't have administrator privileges. I am using Sly and Spacemacs. My problem is that sly-connect times out when trying to connect to the swank server. With Martin's help, I was able to establish a tunnel, start swank, and with a telnet session on the laptop verify that I can send commands to swank (see that other thread for details). Nevertheless, sly-connect still fails. Stepping through the code, I came to a call to make-network-process, which is a C function. The error message is "make client process failed", "Connection timed out", :name, "sly-4", :buffer, nil, :host, "hal9000.us.tel.com", :service, 4005, :nowait, nil, :tls-parameters, nil I need help in figuring out the cause of the problem so that I can ask our IT department for specific help. My emacs can connect to the internet - for instance, org-ref (orgmode+bibtex) can fetch journal article citations using DOI's. So, why is make-network-process failing in this instance? I am looking for some simple tests of make-network proces that can narrow down the cause of failure when connecting to swank. I was going to ask on the emacs mailing list, but I thought it best to start here first. Thank you, Mirko

4 8

Re: What are port requirements for remote lisp?
by Mirko Vukovic 19 Apr '20

19 Apr '20

I have moved from Sly/Slynk to Slime/Swank and I still have the same problem: the connection times out. >From now on, I will focus exclusively on Slime. I have traced the issue to Emacs' make-network-process. I started a separate thread on that topic in this forum. Thanks On Sat, Apr 18, 2020 at 8:28 PM Tobias Rittweiler <trittweiler(a)gmail.com> wrote: > Mirko, > > You are starting the "slynk" server and not "swank". Slynk relates to a > different Emacs mode that derives from Slime but is not 100 protocol > compatible as it seems. > > Hth, > > T > > > On Sun, 19 Apr 2020, 01:51 Mirko Vukovic, <mirko.vukovic(a)gmail.com> wrote: > >> >> On Fri, Apr 3, 2020 at 1:37 PM Martin Simmons <martin(a)lispworks.com> >> wrote: >> >>> >>>>> On Thu, 2 Apr 2020 14:16:55 -0400, Mirko Vukovic said: >>> > >>> > On Thu, Apr 2, 2020 at 9:09 AM Martin Simmons <martin(a)lispworks.com> >>> wrote: >>> > >>> > > >>>>> On Thu, 2 Apr 2020 08:33:42 -0400, Mirko Vukovic said: >>> > > > >>> > > > On Thu, Apr 2, 2020 at 7:55 AM Martin Simmons < >>> martin(a)lispworks.com> >>> > > wrote: >>> > > > >>> > > > > >>>>> On Wed, 1 Apr 2020 08:59:30 -0400, Mirko Vukovic said: >>> > > > > > >>> > > > > > On Tue, Mar 31, 2020 at 11:51 AM Martin Simmons < >>> > > martin(a)lispworks.com> >>> > > > > > wrote: >>> > > > > > >>> > > > > > > >>>>> On Mon, 30 Mar 2020 21:16:00 -0400, Mirko Vukovic said: >>> > > > > > > > >>> > > > > > > > Hello, >>> > > > > > > > >>> > > > > > > > My setup is Sly on Spacemacs with Windows 10 running >>> remote lisp >>> > > on >>> > > > > Linux >>> > > > > > > > over a corporate network. I have not found a Sly mailing >>> list, >>> > > and I >>> > > > > > > hope I >>> > > > > > > > can get an answer here. >>> > > > > > > > >>> > > > > > > > Emacs is running Sly on Spacemacs on Windows 10. Lisp is >>> running >>> > > on a >>> > > > > > > Linux >>> > > > > > > > server. But Sly does not connect to the listening Lisp. >>> Corporate >>> > > > > network >>> > > > > > > > security policies have changed. I can ask for IT to >>> accommodate >>> > > me, >>> > > > > but >>> > > > > > > > first I need to know what to ask for. >>> > > > > > > > >>> > > > > > > > So far, I have opened a tunnel, and started a listening >>> lisp >>> > > (details >>> > > > > > > > below). >>> > > > > > > > >>> > > > > > > > In Emacs I get: >>> > > > > > > > >>> > > > > > > > sly-connect RET RET RET >>> > > > > > > > [sly] Connecting to Slynk on port 4005.. >>> > > > > > > > helm-M-x-execute-command: make client process failed: >>> Connection >>> > > > > timed >>> > > > > > > out, >>> > > > > > > > :name, sly-9, :buffer, nil, :host, hal9000, :service, 4005, >>> > > :nowait, >>> > > > > nil, >>> > > > > > > > :tls-parameters, nil >>> > > > > > > > >>> > > > > > > > The session transcript: >>> > > > > > > > > ssh -L4005:localhost:4005 mirko@hal9000 >>> > > > > > > > >>> > > > > > > > [mirko@hal9000 .roswell]$ ros -L ccl-bin run --load >>> > > > > > > start-slynk-server.lisp >>> > > > > > > > >>> > > > > > > > Added SLYNK path to ASDF:*CENTRAL-REGISTRY* >>> > > > > > > > SLYNK's ASDF loader finished. >>> > > > > > > > Loaded ASDF system >>> > > > > > > > ;; Slynk started at port: 4005. >>> > > > > > > > >>> > > > > > > > Created SLYNK server on port 4005 >>> > > > > > > > Set *USE-DEDICATED-OUTPUT-STREAM* to NIL >>> > > > > > > > Clozure Common Lisp Version 1.11.5/v1.11.5 (LinuxX8664) >>> > > > > > > > >>> > > > > > > > For more information about CCL, please see >>> > > http://ccl.clozure.com. >>> > > > > > > > >>> > > > > > > > CCL is free software. It is distributed under the terms >>> of the >>> > > > > Apache >>> > > > > > > > Licence, Version 2.0. >>> > > > > > > > ? >>> > > > > > > > >>> > > > > > > > My question is as follows: >>> > > > > > > > >>> > > > > > > > 1. Do I need bi-directional traffic on 4005? >>> > > > > > > >>> > > > > > > Assuming you are using the ssh tunnel above, then you don't >>> need >>> > > port >>> > > > > 4005 >>> > > > > > > traffic on the LAN (it is all hidden in the tunnel). >>> > > > > > > >>> > > > > > > The most likely problem is that some firewall on the Windows >>> > > machine is >>> > > > > > > blocking port 4005. You may need to configure that firewall >>> to >>> > > allow >>> > > > > ssh >>> > > > > > > to >>> > > > > > > listen on localhost:4005 and/or to accept connections to it >>> from >>> > > > > Spacemacs. >>> > > > > > > In theory you might have similar localhost firewall issues on >>> > > hal9000, >>> > > > > but >>> > > > > > > that is less likely. >>> > > > > > > >>> > > > > > > >>> > > > > > > > 2. Do I need bi-directional traffic on 22? (after recent >>> > > changes I >>> > > > > > > > cannot ssh or scp into my Windows machine) >>> > > > > > > >>> > > > > > > I'm assuming that you ran the ssh command on the Windows 10 >>> machine >>> > > > > and it >>> > > > > > > gave you a working login to hal9000. If so, then it looks >>> like you >>> > > > > already >>> > > > > > > have what you need for port 22. >>> > > > > > > >>> > > > > > >>> > > > > > Yes, I can log in to hal9000 with the -L switch: >>> > > > > > >>> > > > > > > ssh -L4005:localhost:4005 mirko@hal9000 >>> > > > > > Last login: Thu Mar 19 14:33:17 2020 from 172.27.236.189 >>> > > > > > [mirko@hal9000 ~]$ >>> > > > > > >>> > > > > > >>> > > > > > > >>> > > > > > > Note that bi-directional traffic on a connected socket is >>> different >>> > > > > from >>> > > > > > > whether you can make a connection in both directions. >>> > > > > > > >>> > > > > > > >>> > > > > > > > 3. What tools can I use to try to narrow down the cause >>> of the >>> > > > > > > problem? >>> > > > > > > > For instance, can I send a command to the lisp image, >>> and see >>> > > its >>> > > > > > > effects >>> > > > > > > > on the lisp side? >>> > > > > > > >>> > > > > > > Firstly, run "netstat -antp" on hal9000 to see if Lisp is >>> > > listening on >>> > > > > port >>> > > > > > > 4005. >>> > > > > > > >>> > > > > > >>> > > > > > It looks that ccl-bin is listening: >>> > > > > > $ sudo netstat -antp | grep :4005 >>> > > > > > tcp 0 0 127.0.0.1:4005 0.0.0.0:* >>> > > > > LISTEN >>> > > > > > 104461/lx86cl64 >>> > > > > > >>> > > > > > >>> > > > > > > >>> > > > > > > Secondly, run "netstat -anop tcp" on the Windows 10 machine >>> to see >>> > > if >>> > > > > ssh >>> > > > > > > is >>> > > > > > > listening on port 4005. >>> > > > > > > >>> > > > > > > >>> > > > > > I have Msys2's netstat. On the laptop: >>> > > > > > > which netstat >>> > > > > > /c/WINDOWS/system32/netstat >>> > > > > > /c/Users/mirko/Downloads >>> > > > > > > netstat -anop tcp | grep :4005 >>> > > > > > TCP 127.0.0.1:4005 0.0.0.0:0 >>> LISTENING >>> > > > > 12052 >>> > > > > >>> > > > > Yes, both netstat outputs look good at that point. >>> > > > > >>> > > > > >>> > > > > > > Thirdly, run "ssh -p 4005 localhost" on the Windows 10 >>> machine. >>> > > This >>> > > > > use a >>> > > > > > > ssh is very bogus, but it should at least give an error >>> message >>> > > with >>> > > > > some >>> > > > > > > diagnostics. (Normally I would use telnet for this, but it >>> is not >>> > > > > > > installed >>> > > > > > > on Windows 10 by default.) >>> > > > > > > >>> > > > > > >>> > > > > > Outputs of both ssh and telnet on the laptop: >>> > > > > > > which telnet >>> > > > > > /usr/bin/telnet >>> > > > > > /c/Users/mirko/Downloads >>> > > > > > > telnet localhost 4005 >>> > > > > > Trying ::1... >>> > > > > > Connected to localhost. >>> > > > > > Escape character is '^]'. >>> > > > > > Connection closed by foreign host. >>> > > > > >>> > > > > OK, so it is connected to the Windows side at least. >>> > > > > >>> > > > > Check that the Slynk server was created with :dont-close t (or >>> set >>> > > > > slynk:*dont-close* to t before creating it). If dont-close is >>> nil, it >>> > > will >>> > > > > only accept one connection, which makes debugging difficult. >>> > > > > >>> > > > > Then restart the log in to hal9000 with -v option to ssh to make >>> it >>> > > print >>> > > > > debug >>> > > > > information: >>> > > > > >>> > > > > ssh -v -L4005:localhost:4005 mirko@hal9000 >>> > > > > >>> > > > > and try the telnet again to see what is happening at the Linux >>> end. >>> > > > > >>> > > > > __Martin >>> > > > > >>> > > > Here is the test log. Telnet and ssh debug are at the bottom. >>> > > > 1 Start slynk with :dont-close t >>> > > > >>> > > > Modified startup script: >>> > > > >>> > > > (let ((port 4005)) >>> > > > (slynk:create-server :port port :dont-close t) >>> > > > (format t "~% Created SLYNK server on port ~a" port)) >>> > > > (setf slynk:*use-dedicated-output-stream* nil) >>> > > > >>> > > > 2 Started tunnel with verbose option, -v switch >>> > > > >>> > > > $ ssh -v -L4005:hal9000:4005 mirko@hal9000 >>> > > > >>> > > > 3 Telnet on laptop side to laptop port 4005 >>> > > > >>> > > > @laptop> telnet localhost 4005 >>> > > > Trying ::1... >>> > > > Connected to localhost. >>> > > > Escape character is '^]'. >>> > > > Connection closed by foreign host. >>> > > > >>> > > > 4 SSH debug output >>> > > > >>> > > > @hal9000> debug1: Connection to port 4005 forwarding to hal9000 >>> port >>> > > > 4005 requested. >>> > > > debug1: channel 3: new [direct-tcpip] >>> > > > channel 3: open failed: connect failed: Connection refused >>> > > > debug1: channel 3: free: direct-tcpip: listening port 4005 for >>> hal9000 >>> > > > port 4005, connect from ::1 port 64100 to ::1 port 4005, nchannels >>> 4 >>> > > >>> > > It looks like hal9000 is resolving to the IPv6 localhost address ::1 >>> on >>> > > hal9000, but the Lisp is probably only listening on IPv4. >>> > > >>> > > Try restarting the tunnel with -L4005:127.0.0.1:4005 to force IPv4. >>> > > >>> > > __Martin >>> > > >>> > >>> > I restarted tunnel with IPv4: Now when I type something in the telnet >>> > session, I get Lisp to respond (with debugger in this case). Sly is >>> still >>> > not connecting - maybe I need to restart emacs. >>> > >>> > Log: >>> > 1 Start slynk with :dont-close t as before >>> > 2 Start tunnel with verbose option, -v switch and IPv4 >>> > >>> > $ ssh -v -L4005:127.0.0.1:4005 977315@hal9000 >>> > >>> > 3 Telnet on laptop side to laptop port 4005 >>> > >>> > @laptop> telnet localhost 4005 >>> > Trying ::1... >>> > Connected to localhost. >>> > Escape character is '^]'. >>> > >>> > 3.1 SSH debug output to telnet start >>> > >>> > debug1: Connection to port 4005 forwarding to 127.0.0.1 port 4005 >>> requested. >>> > debug1: channel 3: new [direct-tcpip] >>> > >>> > 4 Send command via telnet session >>> > >>> > Using telnet session send command: >>> > >>> > *features* >>> > Connection closed by foreign host. >>> > >>> > 4.1 Results in an error in lisp due to syntax error >>> > >>> > ;; slynk:close-connection: Not an integer string: "*featu" >>> > ;; closing 0 channels >>> > ;; closing 0 listeners >>> > ;; Event history start: >>> > decode-message >>> > close-connection: Not an integer string: >>> "\x00FF\x00F4\x00FF\x00FD\x00FF" ... >>> > close-connection Not an integer string: >>> > "\x00FF\x00F4\x00FF\x00FD\x00FF" ... done. >>> >>> This \x00FF\x00F4\x00FF\x00FD\x00FF string is unexpected to me. Did that >>> happen when you tried to connect from emacs? Restarting emacs is >>> probably a >>> good idea to rule out any issue with its state. >>> >>> >>> > decode-message >>> > close-connection: Not an integer string: "*featu" ... >>> > ;; Event history end. >>> > ;; Backtrace: >>> > 0: (NIL #<Unknown Arguments>) >>> > 1: (NIL #<Unknown Arguments>) >>> > 2: (SLYNK-BACKEND:CALL-WITH-DEBUGGING-ENVIRONMENT #<Compiled-function >>> > (:INTERNAL SLYNK::SAFE-BACKTRACE) (Non-Global) #x302000A0BFFF>) >>> > 3: (SLYNK::SAFE-BACKTRACE) >>> > 4: (SLYNK::SIGNAL-SLYNK-ERROR #<CCL::PARSE-INTEGER-NOT-INTEGER-STRING >>> > #x302000C1F32D> NIL) >>> > 5: (SIGNAL #<CCL::PARSE-INTEGER-NOT-INTEGER-STRING #x302000C1F32D>) >>> > 6: (CCL::%ERROR #<CCL::PARSE-INTEGER-NOT-INTEGER-STRING >>> > #x302000C1F32D> (:STRING "*featu") 5975725205395) >>> > 7: (PARSE-INTEGER "*featu" :START 0 :END 6 :RADIX 16 :JUNK-ALLOWED NIL) >>> > 8: (SLYNK-RPC:READ-PACKET #<BASIC-TCP-STREAM ISO-8859-1 (SOCKET/4) >>> > #x302000BDFD9D>) >>> > 9: (SLYNK-RPC:READ-MESSAGE #<BASIC-TCP-STREAM ISO-8859-1 (SOCKET/4) >>> > #x302000BDFD9D> #<Package "SLYNK-IO-PACKAGE">) >>> > 10: (SLYNK::DECODE-MESSAGE #<BASIC-TCP-STREAM ISO-8859-1 (SOCKET/4) >>> > #x302000BDFD9D>) >>> > 11: (SLYNK::READ-LOOP #<MULTITHREADED-CONNECTION #x302000BDEFCD>) >>> > 12: (CCL::RUN-PROCESS-INITIAL-FORM #<PROCESS reader-thread(9) [Active] >>> > #x302000BFEFBD> (#<COMPILED-LEXICAL-CLOSURE (:INTERNAL >>> > CCL::%PROCESS-RUN-FUNCTION) #x302000BFED2F>)) >>> > 13: ((:INTERNAL (CCL::%PROCESS-PRESET-INTERNAL (PROCESS))) #<PROCESS >>> > reader-thread(9) [Active] #x302000BFEFBD> (#<COMPILED-LEXICAL-CLOSURE >>> > (:INTERNAL CCL::%PROCESS-RUN-FUNCTION) #x302000BFED2F>)) >>> > 14: ((:INTERNAL CCL::THREAD-MAKE-STARTUP-FUNCTION)) >>> > ;; Connection to Emacs lost. [ >>> > ;; condition: Not an integer string: "*featu" >>> > ;; type: CCL::PARSE-INTEGER-NOT-INTEGER-STRING >>> > ;; style: :SPAWN] >>> >>> This is working as expected -- the slynk/swank server is not a REPL so >>> you >>> can't just send *features* to it. >>> >>> __Martin >>> >> >> Apologies for the long silence on this topic - I had other pressing >> matters to deal with. I still cannot connect to the swank server from >> Emacs. >> >> To summarize: Based on my tests (which are detailed below), I can connect >> to the swank server as tested via telnet. But emacs is still failing to >> connect to swank. I did some debugging and identified that >> make-network-process is timing out. >> >> I will start another thread on the topic of figuring out why >> make-network-process is timing out. >> >> Martin, many thanks for helping me out so far. >> >> Here is my test procedure: >> >> 1 Establish tunnel >> >> > ssh -v -L4005:127.0.0.1:4005 mirko@hal9000 >> >> 2 Start Swank server >> >> [mirko@laptop] > ssh mirko@hal9000 >> [mirko@hal9000 .roswell]$ ros -L ccl-bin run --load start-slynk-server.lisp >> >> Added SLYNK path to ASDF:*CENTRAL-REGISTRY* >> SLYNK's ASDF loader finished. >> Loaded ASDF system >> ;; Slynk started at port: 4005. >> >> Created SLYNK server on port 4005 >> Set *USE-DEDICATED-OUTPUT-STREAM* to NIL >> Clozure Common Lisp Version 1.11.5/v1.11.5 (LinuxX8664) >> >> For more information about CCL, please see http://ccl.clozure.com. >> >> CCL is free software. It is distributed under the terms of the Apache >> Licence, Version 2.0. >> ? >> >> 3 Test laptop is listening on port 4005 with Telnet >> >> > telnet localhost 4005 >> Trying ::1... >> Connected to localhost. >> Escape character is '^]'. >> >> 4 Test tunnel to lisp >> >> Typing stuff into telnet session >> >> "foo" >> Connection closed by foreign host. >> >> makes CCL react. In this case it drops into debugger because of invalid >> input (I do not know what is valid input): >> >> ? >> "; slynk:close-connection: Not an integer string: "\"foo\" >> ;; closing 0 channels >> ;; closing 0 listeners >> ;; Event history start: >> ... >> >> >> *5 Try slime-connect* >> slime-connect times out >> >> Created: 2020-04-18 Sat 19:41 >> >

1 0

What are port requirements for remote lisp?
by Mirko Vukovic 18 Apr '20

18 Apr '20

Hello, My setup is Sly on Spacemacs with Windows 10 running remote lisp on Linux over a corporate network. I have not found a Sly mailing list, and I hope I can get an answer here. Emacs is running Sly on Spacemacs on Windows 10. Lisp is running on a Linux server. But Sly does not connect to the listening Lisp. Corporate network security policies have changed. I can ask for IT to accommodate me, but first I need to know what to ask for. So far, I have opened a tunnel, and started a listening lisp (details below). In Emacs I get: sly-connect RET RET RET [sly] Connecting to Slynk on port 4005.. helm-M-x-execute-command: make client process failed: Connection timed out, :name, sly-9, :buffer, nil, :host, hal9000, :service, 4005, :nowait, nil, :tls-parameters, nil The session transcript: > ssh -L4005:localhost:4005 mirko@hal9000 [mirko@hal9000 .roswell]$ ros -L ccl-bin run --load start-slynk-server.lisp Added SLYNK path to ASDF:*CENTRAL-REGISTRY* SLYNK's ASDF loader finished. Loaded ASDF system ;; Slynk started at port: 4005. Created SLYNK server on port 4005 Set *USE-DEDICATED-OUTPUT-STREAM* to NIL Clozure Common Lisp Version 1.11.5/v1.11.5 (LinuxX8664) For more information about CCL, please see http://ccl.clozure.com. CCL is free software. It is distributed under the terms of the Apache Licence, Version 2.0. ? My question is as follows: 1. Do I need bi-directional traffic on 4005? 2. Do I need bi-directional traffic on 22? (after recent changes I cannot ssh or scp into my Windows machine) 3. What tools can I use to try to narrow down the cause of the problem? For instance, can I send a command to the lisp image, and see its effects on the lisp side? Thank you, Mirko

3 9

The hyperspec keyboard shortcut started launching my email client instead of my browser?
by Jeffrey Cunningham 22 Mar '20

22 Mar '20

For years I've been using Slime's keyboard shortcut to bring up my browser on a local copy of the hyperspec using the standard Ctrl-c d h shortcut. Now its started launching a new email window in Thunderbird, my email client, instead. I'm running Ubuntu 18.04, Emacs 25.2.2, and Slime 2.24. Anyone run into this? Any idea how to fix it? Thanks. --Jeff

3 4

Slime + SBCL warnings, expected?
by Nicholas Papadonis 21 Mar '20

21 Mar '20

I'm using Slime-20200319, Emacs 26 and SBCL 1.4.16 on Debian 10. Are the following warnings, which I saw invoking M-x slime, expected? Thanks (progn (load "/home/np/.emacs.d/elpa/slime-20200319.1939/swank-loader.lisp" :verbose t) (funcall (read-from-string "swank-loader:init") :from-emacs t) (funcall (read-from-string "swank:start-server") "/tmp/slime.8323")) This is SBCL 1.4.16.debian, an implementation of ANSI Common Lisp. More information about SBCL is available at <http://www.sbcl.org/>. SBCL is free software, provided as is, with absolutely no warranty. It is mostly in the public domain; some portions are provided under BSD-style licenses. See the CREDITS and COPYING files in the distribution for more information. * ; loading #P"/home/np/.emacs.d/elpa/slime-20200319.1939/swank-loader.lisp" WARNING: redefining EMACS-INSPECT (#<SB-PCL:SYSTEM-CLASS COMMON-LISP:T>) in DEFMETHOD ; file: /home/np/.emacs.d/elpa/slime-20200319.1939/swank/sbcl.lisp ; in: DEFUN SWANK/SBCL::MAKE-SOCKET-IO-STREAM ; (EQ :FD-HANDLER SWANK:*COMMUNICATION-STYLE*) ; ; caught WARNING: ; undefined variable: SWANK:*COMMUNICATION-STYLE* ; file: /home/np/.emacs.d/elpa/slime-20200319.1939/swank/backend.lisp ; in: SWANK/BACKEND::DEFINTERFACE SWANK/BACKEND:WAIT-FOR-INPUT ; (ERROR ; "~s not implemented. Check if ~s = ~s is supported by the implementation." ; 'SWANK/BACKEND:WAIT-FOR-INPUT 'SWANK:*COMMUNICATION-STYLE* ; SWANK:*COMMUNICATION-STYLE*) ; ; caught WARNING: ; undefined variable: SWANK:*COMMUNICATION-STYLE* ; file: /home/np/.emacs.d/elpa/slime-20200319.1939/swank/sbcl.lisp ; in: DEFUN SWANK/SBCL::LISP-SOURCE-LOCATION ; (LET ((SWANK/SBCL::SOURCE ; (PRIN1-TO-STRING ; (SB-DEBUG::CODE-LOCATION-SOURCE-FORM SWANK/SBCL::CODE-LOCATION 100))) ; (CONDITION SWANK:*SWANK-DEBUGGER-CONDITION*)) ; (IF (AND (TYPEP CONDITION 'STEP-FORM-CONDITION) ; (SEARCH "SB-IMPL::WITH-STEPPING-ENABLED" SWANK/SBCL::SOURCE :TEST ; #'CHAR-EQUAL) ; (SEARCH "SB-IMPL::STEP-FINISHED" SWANK/SBCL::SOURCE :TEST ; #'CHAR-EQUAL)) ; (SWANK/BACKEND:MAKE-ERROR-LOCATION "Stepping...") ; (SWANK/BACKEND:MAKE-LOCATION `(:SOURCE-FORM ,SWANK/SBCL::SOURCE) ; '(:POSITION 1)))) ; ; caught WARNING: ; undefined variable: SWANK:*SWANK-DEBUGGER-CONDITION* ; ; compilation unit finished ; Undefined variables: ; SWANK:*COMMUNICATION-STYLE* SWANK:*SWANK-DEBUGGER-CONDITION* ; caught 3 WARNING conditions ; compiling file "/home/np/.emacs.d/elpa/slime-20200319.1939/contrib/swank-util.lisp" (written 20 MAR 2020 05:18:17 PM): ; wrote /home/np/.slime/fasl/2.24/sbcl-1.4.16.debian-linux-x86-64/contrib/swank-util.fasl ; compilation finished in 0:00:00.344 ; compiling file "/home/np/.emacs.d/elpa/slime-20200319.1939/contrib/swank-repl.lisp" (written 20 MAR 2020 05:18:17 PM): ; wrote /home/np/.slime/fasl/2.24/sbcl-1.4.16.debian-linux-x86-64/contrib/swank-repl.fasl ; compilation finished in 0:00:00.955 ; compiling file "/home/np/.emacs.d/elpa/slime-20200319.1939/contrib/swank-c-p-c.lisp" (written 20 MAR 2020 05:18:17 PM): ; wrote /home/np/.slime/fasl/2.24/sbcl-1.4.16.debian-linux-x86-64/contrib/swank-c-p-c.fasl ; compilation finished in 0:00:00.736 ; compiling file "/home/np/.emacs.d/elpa/slime-20200319.1939/contrib/swank-arglists.lisp" (written 20 MAR 2020 05:18:17 PM): ; file: /home/np/.emacs.d/elpa/slime-20200319.1939/contrib/swank-arglists.lisp ; in: DEFSTRUCT KEYWORD-ARG ; (DEFSTRUCT ; (SWANK::KEYWORD-ARG (:CONC-NAME SWANK::KEYWORD-ARG.) ; (:CONSTRUCTOR SWANK::%MAKE-KEYWORD-ARG)) ; KEYWORD ; SWANK::ARG-NAME ; SWANK::DEFAULT-ARG) ; --> PROGN EVAL-WHEN ; ==> ; (SB-KERNEL::%COMPILER-DEFSTRUCT ; '#<SB-KERNEL:DEFSTRUCT-DESCRIPTION SWANK::KEYWORD-ARG {1005155953}> ; '#(#<SB-KERNEL:LAYOUT for T {50300003}> ; #<SB-KERNEL:LAYOUT for STRUCTURE-OBJECT {50300083}>)) ; ; caught STYLE-WARNING: ; Previously compiled calls to SWANK::KEYWORD-ARG.KEYWORD, ; SWANK::KEYWORD-ARG.ARG-NAME and SWANK::KEYWORD-ARG.DEFAULT-ARG could not be ; inlined because the structure definition for SWANK::KEYWORD-ARG was not yet ; seen. To avoid this warning, DEFSTRUCT should precede references to the ; affected functions, or they must be declared locally notinline at each call ; site. ; in: DEFSTRUCT OPTIONAL-ARG ; (DEFSTRUCT ; (SWANK::OPTIONAL-ARG (:CONC-NAME SWANK::OPTIONAL-ARG.) ; (:CONSTRUCTOR SWANK::%MAKE-OPTIONAL-ARG)) ; SWANK::ARG-NAME ; SWANK::DEFAULT-ARG) ; --> PROGN EVAL-WHEN ; ==> ; (SB-KERNEL::%COMPILER-DEFSTRUCT ; '#<SB-KERNEL:DEFSTRUCT-DESCRIPTION SWANK::OPTIONAL-ARG {100557EFD3}> ; '#(#<SB-KERNEL:LAYOUT for T {50300003}> ; #<SB-KERNEL:LAYOUT for STRUCTURE-OBJECT {50300083}>)) ; ; caught STYLE-WARNING: ; Previously compiled calls to SWANK::OPTIONAL-ARG.ARG-NAME and ; SWANK::OPTIONAL-ARG.DEFAULT-ARG could not be inlined because the structure ; definition for SWANK::OPTIONAL-ARG was not yet seen. To avoid this warning, ; DEFSTRUCT should precede references to the affected functions, or they must be ; declared locally notinline at each call site. ; in: DEFGENERIC EXTRACT-LOCAL-OP-ARGLISTS => DEF.BODY (CDDR CURRENT-DEF) ; (CDDR SWANK::CURRENT-DEF) ; --> CDR CDR ; ==> ; SWANK::CURRENT-DEF ; ; note: deleting unreachable code ; in: DEFGENERIC EXTRACT-LOCAL-OP-ARGLISTS ; (SWANK::%COLLECT-OP/ARGL-ALIST SWANK::DEFS) ; ==> ; SWANK::DEFS ; ; note: deleting unreachable code ; ; compilation unit finished ; caught 2 STYLE-WARNING conditions ; printed 2 notes ; wrote /home/np/.slime/fasl/2.24/sbcl-1.4.16.debian-linux-x86-64/contrib/swank-arglists.fasl ; compilation finished in 0:00:11.448 ; compiling file "/home/np/.emacs.d/elpa/slime-20200319.1939/contrib/swank-fuzzy.lisp" (written 20 MAR 2020 05:18:18 PM): ; file: /home/np/.emacs.d/elpa/slime-20200319.1939/contrib/swank-fuzzy.lisp ; in: DEFUN RECURSIVELY-COMPUTE-MOST-COMPLETIONS ; (INCF SWANK::SHORT-INDEX) ; ==> ; (SETQ SWANK::SHORT-INDEX (+ 1 SWANK::SHORT-INDEX)) ; ; note: doing signed word to integer coercion (cost 20) to SHORT-INDEX ; ; compilation unit finished ; printed 1 note ; wrote /home/np/.slime/fasl/2.24/sbcl-1.4.16.debian-linux-x86-64/contrib/swank-fuzzy.fasl ; compilation finished in 0:00:01.915 ; compiling file "/home/np/.emacs.d/elpa/slime-20200319.1939/contrib/swank-fancy-inspector.lisp" (written 20 MAR 2020 05:18:17 PM): ; wrote /home/np/.slime/fasl/2.24/sbcl-1.4.16.debian-linux-x86-64/contrib/swank-fancy-inspector.fasl ; compilation finished in 0:00:06.231 ; compiling file "/home/np/.emacs.d/elpa/slime-20200319.1939/contrib/swank-presentations.lisp" (written 20 MAR 2020 05:18:17 PM): ; file: /home/np/.emacs.d/elpa/slime-20200319.1939/contrib/swank-presentations.lisp ; in: EVAL-WHEN (:COMPILE-TOPLEVEL :LOAD-TOPLEVEL :EXECUTE) ; (SWANK:SWANK-REQUIRE :SWANK-REPL) ; ; caught WARNING: ; SWANK-REPL also exports the following symbols: ; (SWANK-REPL:CREATE-REPL SWANK-REPL:LISTENER-GET-VALUE ; SWANK-REPL:CLEAR-REPL-VARIABLES SWANK-REPL:LISTENER-SAVE-VALUE ; SWANK-REPL:LISTENER-EVAL SWANK-REPL:REDIRECT-TRACE-OUTPUT) ; See also: ; The ANSI Standard, Macro DEFPACKAGE ; The SBCL Manual, Variable SB-EXT:*ON-PACKAGE-VARIANCE* ; ; caught STYLE-WARNING: ; redefining THREAD-FOR-EVALUATION (#<STRUCTURE-CLASS SWANK::MULTITHREADED-CONNECTION> ; #<SB-MOP:EQL-SPECIALIZER :FIND-EXISTING>) in DEFMETHOD ; ; compilation unit finished ; caught 1 WARNING condition ; caught 1 STYLE-WARNING condition ; wrote /home/np/.slime/fasl/2.24/sbcl-1.4.16.debian-linux-x86-64/contrib/swank-presentations.fasl ; compilation finished in 0:00:00.636 ; compiling file "/home/np/.emacs.d/elpa/slime-20200319.1939/contrib/swank-presentation-streams.lisp" (written 20 MAR 2020 05:18:17 PM): ; file: /home/np/.emacs.d/elpa/slime-20200319.1939/contrib/swank-presentation-streams.lisp ; in: DEFUN PRESENTING-OBJECT-1 ; (SWANK::SLIME-STREAM-P STREAM) ; ; caught STYLE-WARNING: ; undefined function: SWANK::SLIME-STREAM-P ; ; compilation unit finished ; Undefined function: ; SLIME-STREAM-P ; caught 1 STYLE-WARNING condition ; wrote /home/np/.slime/fasl/2.24/sbcl-1.4.16.debian-linux-x86-64/contrib/swank-presentation-streams.fasl ; compilation finished in 0:00:00.548 ; compiling file "/home/np/.emacs.d/elpa/slime-20200319.1939/contrib/swank-asdf.lisp" (written 20 MAR 2020 05:18:17 PM): ; file: /home/np/.emacs.d/elpa/slime-20200319.1939/contrib/swank-asdf.lisp ; in: ASDEFS "2.26.149" ; (SWANK::ASDEFS "2.26.149" ; (DEFMETHOD SWANK::COMPONENT-RELATIVE-PATHNAME ; ((SWANK::SYSTEM ASDF/SYSTEM:SYSTEM)) ; (UIOP/BACKWARD-DRIVER:COERCE-PATHNAME ; (AND ; (SLOT-BOUNDP SWANK::SYSTEM ; 'ASDF/COMPONENT:RELATIVE-PATHNAME) ; (SLOT-VALUE SWANK::SYSTEM ; 'ASDF/COMPONENT:RELATIVE-PATHNAME)) ; :TYPE :DIRECTORY :DEFAULTS ; (SWANK::SYSTEM-SOURCE-DIRECTORY SWANK::SYSTEM))) ; (DEFUN SWANK::LOAD-ASD ; (PATHNAME &KEY SWANK::NAME &ALLOW-OTHER-KEYS) ; (ASDF/BACKWARD-INTERNALS:LOAD-SYSDEF ; (OR SWANK::NAME (STRING-DOWNCASE #)) PATHNAME))) ; --> PROGN UNLESS IF IF DEFMETHOD PROGN EVAL-WHEN SB-PCL::%DEFMETHOD-EXPANDER ; --> SB-PCL::LOAD-DEFMETHOD LIST* LET* SB-INT:NAMED-LAMBDA FUNCTION ; --> SYMBOL-MACROLET SB-PCL::FAST-LEXICAL-METHOD-FUNCTIONS ; --> SB-PCL::BIND-FAST-LEXICAL-METHOD-FUNCTIONS FLET SB-PCL::BIND-ARGS LET* ; --> LOCALLY SYMBOL-MACROLET SB-PCL::PV-BINDING SB-PCL::PV-BINDING1 ; --> SB-PCL::PV-ENV LOCALLY LET BLOCK ; ==> ; (UIOP/BACKWARD-DRIVER:COERCE-PATHNAME ; (IF (SB-PCL::OPTIMIZED-SLOT-BOUNDP ; (SLOT-BOUNDP SWANK::SYSTEM 'ASDF/COMPONENT:RELATIVE-PATHNAME) ; SWANK::SYSTEM ; (SB-PCL::INSTANCE-BOUNDP (SB-PCL::PV-OFFSET 0) SWANK::SYSTEM 0 ; 'ASDF/COMPONENT:RELATIVE-PATHNAME ; '#<STANDARD-CLASS ASDF/SYSTEM:SYSTEM>)) ; (SB-PCL::OPTIMIZED-SLOT-VALUE ; (SLOT-VALUE SWANK::SYSTEM 'ASDF/COMPONENT:RELATIVE-PATHNAME) ; SWANK::SYSTEM ; (SB-PCL::INSTANCE-READ (SB-PCL::PV-OFFSET 0) SWANK::SYSTEM 0 ; 'ASDF/COMPONENT:RELATIVE-PATHNAME ; '#<STANDARD-CLASS ASDF/SYSTEM:SYSTEM>))) ; :TYPE :DIRECTORY :DEFAULTS (SWANK::SYSTEM-SOURCE-DIRECTORY SWANK::SYSTEM)) ; ; caught STYLE-WARNING: ; DEPRECATED-FUNCTION-STYLE-WARNING: Using deprecated function UIOP/BACKWARD-DRIVER:COERCE-PATHNAME -- please update your code to use a newer API. ; The docstring for this function says: ; DEPRECATED. Please use UIOP:PARSE-UNIX-NAMESTRING instead. ; ; in: DEFUN LOAD-ASD ; (ASDF/BACKWARD-INTERNALS:LOAD-SYSDEF ; (OR SWANK::NAME (STRING-DOWNCASE (PATHNAME-NAME PATHNAME))) PATHNAME) ; ; caught STYLE-WARNING: ; DEPRECATED-FUNCTION-STYLE-WARNING: Using deprecated function ASDF/BACKWARD-INTERNALS:LOAD-SYSDEF -- please update your code to use a newer API. ; in: DEFMETHOD XREF-DOIT ((EQL :DEPENDS-ON) T) ; (ASDF/BACKWARD-INTERFACE:SYSTEM-DEFINITION-PATHNAME SWANK::DEPENDENCY) ; ; caught STYLE-WARNING: ; DEPRECATED-FUNCTION-STYLE-WARNING: Using deprecated function ASDF/BACKWARD-INTERFACE:SYSTEM-DEFINITION-PATHNAME -- please update your code to use a newer API. ; The docstring for this function says: ; DEPRECATED. This function used to expose ASDF internals with subtle ; differences with respect to user expectations, that have been refactored ; away since. We recommend you use ASDF:SYSTEM-SOURCE-FILE instead for a ; mostly compatible replacement that we're supporting, or even ; ASDF:SYSTEM-SOURCE-DIRECTORY or ASDF:SYSTEM-RELATIVE-PATHNAME ; if that's whay you mean. ; ; in: DEFSLIMEFUN ASDF-SYSTEM-FILES ; (ASDF/BACKWARD-INTERFACE:SYSTEM-DEFINITION-PATHNAME SWANK::SYSTEM) ; ; caught STYLE-WARNING: ; DEPRECATED-FUNCTION-STYLE-WARNING: Using deprecated function ASDF/BACKWARD-INTERFACE:SYSTEM-DEFINITION-PATHNAME -- please update your code to use a newer API. ; The docstring for this function says: ; DEPRECATED. This function used to expose ASDF internals with subtle ; differences with respect to user expectations, that have been refactored ; away since. We recommend you use ASDF:SYSTEM-SOURCE-FILE instead for a ; mostly compatible replacement that we're supporting, or even ; ASDF:SYSTEM-SOURCE-DIRECTORY or ASDF:SYSTEM-RELATIVE-PATHNAME ; if that's whay you mean. ; ; file: /home/np/.emacs.d/elpa/slime-20200319.1939/contrib/swank-asdf.lisp ; in: DEFUN LOAD-SYSDEF ; (ASDF/INTERFACE::MAKE-TEMPORARY-PACKAGE) ; ; caught STYLE-WARNING: ; undefined function: ASDF/INTERFACE::MAKE-TEMPORARY-PACKAGE ; ; compilation unit finished ; Undefined function: ; ASDF/INTERFACE::MAKE-TEMPORARY-PACKAGE ; caught 5 STYLE-WARNING conditions ; wrote /home/np/.slime/fasl/2.24/sbcl-1.4.16.debian-linux-x86-64/contrib/swank-asdf.fasl ; compilation finished in 0:00:06.484 ; compiling file "/home/np/.emacs.d/elpa/slime-20200319.1939/contrib/swank-package-fu.lisp" (written 20 MAR 2020 05:18:17 PM): ; wrote /home/np/.slime/fasl/2.24/sbcl-1.4.16.debian-linux-x86-64/contrib/swank-package-fu.fasl ; compilation finished in 0:00:00.141 ; compiling file "/home/np/.emacs.d/elpa/slime-20200319.1939/contrib/swank-hyperdoc.lisp" (written 20 MAR 2020 05:18:18 PM): ; wrote /home/np/.slime/fasl/2.24/sbcl-1.4.16.debian-linux-x86-64/contrib/swank-hyperdoc.fasl ; compilation finished in 0:00:00.061 ; compiling file "/home/np/.emacs.d/elpa/slime-20200319.1939/contrib/swank-sbcl-exts.lisp" (written 20 MAR 2020 05:18:18 PM): ; wrote /home/np/.slime/fasl/2.24/sbcl-1.4.16.debian-linux-x86-64/contrib/swank-sbcl-exts.fasl ; compilation finished in 0:00:00.307 ; compiling file "/home/np/.emacs.d/elpa/slime-20200319.1939/contrib/swank-mrepl.lisp" (written 20 MAR 2020 05:18:17 PM): ; wrote /home/np/.slime/fasl/2.24/sbcl-1.4.16.debian-linux-x86-64/contrib/swank-mrepl.fasl ; compilation finished in 0:00:00.536 ; compiling file "/home/np/.emacs.d/elpa/slime-20200319.1939/contrib/swank-trace-dialog.lisp" (written 20 MAR 2020 05:18:17 PM): ; wrote /home/np/.slime/fasl/2.24/sbcl-1.4.16.debian-linux-x86-64/contrib/swank-trace-dialog.fasl ; compilation finished in 0:00:00.610 ; compiling file "/home/np/.emacs.d/elpa/slime-20200319.1939/contrib/swank-macrostep.lisp" (written 20 MAR 2020 05:18:18 PM): ; wrote /home/np/.slime/fasl/2.24/sbcl-1.4.16.debian-linux-x86-64/contrib/swank-macrostep.fasl ; compilation finished in 0:00:00.912 ; compiling file "/home/np/.emacs.d/elpa/slime-20200319.1939/contrib/swank-quicklisp.lisp" (written 20 MAR 2020 05:18:18 PM): ; wrote /home/np/.slime/fasl/2.24/sbcl-1.4.16.debian-linux-x86-64/contrib/swank-quicklisp.fasl ; compilation finished in 0:00:00.025 ;; Swank started at port: 43191. 43191 *

2 1

Using MIT Scheme with Slime?
by Nicholas Papadonis 20 Mar '20

20 Mar '20

Hi, I appreciate any guidance on how to accomplish this. I'm using MIT Scheme 9.1.1. I followed the README here: https://github.com/ecraven/mit-scheme-swank https://github.com/slime/slime/blob/master/contrib/swank-mit-scheme.scm I added the following to ~/.scheme.init (load-option 'format) (load "~/.emacs.d/lisp/swank.scm" (->environment '(runtime swank))) and added relevant portions of swank.scm and swank-mit-scheme.scm to .emacs suggested by : There is an abort issue when starting MIT REPL: M-x run-mit Image saved on Saturday December 3, 2016 at 9:44:07 AM Release 9.1.1 || Microcode 15.3 || Runtime 15.7 || SF 4.41 || LIAR/x86-64 4.118 || Edwin 3.116 ;Loading "/home/np/.scheme.init"... ; Loading "format.com"... done ; Loading "swank.scm"... aborted I also see the following error when *inferior-lisp* buffer starts with MIT Scheme: ;Unbound variable: create-package-from-description Which is called in swank-mit-scheme.scm elisp code for (mit-scheme-init). Under the mode line keep saying Polling /tmp/slime, which I assume is due a non working connection. Appreciate any guidance. Thanks

3 3

slime + clisp + emacs: server disconnects
by Stuart Little 25 Jul '19

25 Jul '19

I am running - emacs 26.2 - slime 2.24 - clisp 2.49 on Linux. 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 The inferior-lisp buffer reads as follows after the disconnect: --- buffer starts --- (progn (load "/home/chirvasitua/quicklisp/dists/quicklisp/software/slime-v2.24/swank-loader.lisp" :verbose t) (funcall (read-from-string "swank-loader:init") :from-emacs t) (funcall (read-from-string "swank:start-server") "/tmp/slime.19223")) i i i i i i i ooooo o ooooooo ooooo ooooo I I I I I I I 8 8 8 8 8 o 8 8 I \ `+' / I 8 8 8 8 8 8 \ `-+-' / 8 8 8 ooooo 8oooo `-__|__-' 8 8 8 8 8 | 8 o 8 8 o 8 8 ------+------ ooooo 8oooooo ooo8ooo ooooo 8 Welcome to GNU CLISP 2.49 (2010-07-07) <http://clisp.cons.org/> Copyright (c) Bruno Haible, Michael Stoll 1992, 1993 Copyright (c) Bruno Haible, Marcus Daniels 1994-1997 Copyright (c) Bruno Haible, Pierpaolo Bernardi, Sam Steingold 1998 Copyright (c) Bruno Haible, Sam Steingold 1999-2000 Copyright (c) Sam Steingold, Bruno Haible 2001-2010 Type :h and hit Enter for context help. [1]> ;; Loading file /home/chirvasitua/quicklisp/dists/quicklisp/software/slime-v2.24/swank-loader.lisp ... ;; Loaded file /home/chirvasitua/quicklisp/dists/quicklisp/software/slime-v2.24/swank-loader.lisp ;; Loading file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/packages.fas ... ;; Loaded file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/packages.fas ;; Loading file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/backend.fas ... ;; Loaded file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/backend.fas ;; Loading file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/xref.fas ... ;; Loaded file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/xref.fas ;; Loading file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/metering.fas ... ;; Loaded file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/metering.fas ;; Loading file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/clisp.fas ... WARNING: DEFUN/DEFMACRO: redefining function BREAK in /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/clisp.fas, was defined in /builddir/clisp-2.49/src/condition.fas WARNING: Replacing method #<STANDARD-METHOD (#<BUILT-IN-CLASS T>)> in #<STANDARD-GENERIC-FUNCTION EMACS-INSPECT> ;; Loaded file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/clisp.fas ;; Loading file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/gray.fas ... WARNING: The generic function #<STANDARD-GENERIC-FUNCTION STREAM-LINE-COLUMN> is being modified, but has already been called. WARNING: The generic function #<STANDARD-GENERIC-FUNCTION STREAM-FORCE-OUTPUT> is being modified, but has already been called. WARNING: The generic function #<STANDARD-GENERIC-FUNCTION STREAM-LINE-COLUMN> is being modified, but has already been called. ;; Loaded file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/gray.fas ;; Loading file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/match.fas ... ;; Loaded file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/match.fas ;; Loading file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/rpc.fas ... ;; Loaded file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/rpc.fas ;; Loading file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/swank.fas ... ;; Loaded file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/swank.fas 0 errors, 5 warnings ;; Swank started at port: 41975. CL-USER> ;; Loading file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-trace-dialog.fas ... ;; Loaded file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-trace-dialog.fas ;; Loading file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-package-fu.fas ... ;; Loaded file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-package-fu.fas ;; Loading file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-presentations.fas ... ;; Loading file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-repl.fas ... WARNING: The generic function #<STANDARD-GENERIC-FUNCTION THREAD-FOR-EVALUATION> is being modified, but has already been called. WARNING: Replacing method #<STANDARD-METHOD (#<STRUCTURE-CLASS MULTITHREADED-CONNECTION> (EQL :FIND-EXISTING))> in #<STANDARD-GENERIC-FUNCTION THREAD-FOR-EVALUATION> ;; Loaded file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-repl.fas ;; Loaded file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-presentations.fas ;; Loading file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-macrostep.fas ... ;; Loaded file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-macrostep.fas ;; Loading file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-fuzzy.fas ... ;; Loading file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-util.fas ... ;; Loaded file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-util.fas ;; Loading file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-c-p-c.fas ... ;; Loaded file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-c-p-c.fas ;; Loaded file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-fuzzy.fas ;; Loading file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-fancy-inspector.fas ... ;; Loaded file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-fancy-inspector.fas ;; Loading file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-arglists.fas ... WARNING: Test failed: (&KEY #'#'+) => "(&key (function #'+))" Expected: One of: "(&key (function #'+))", "(&key (function (function +)))" ;; Loaded file /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-arglists.fas Process inferior-lisp segmentation fault --- buffer ends --- More information: - starting clisp in a terminal all on its own seems to work fine; I haven't had segmentation faults using it in isolation from slime. - I tried to start the server from within clisp and connect to it: (a) rlwrap clisp (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

7 16

Re: slime + clisp + emacs: server disconnects
by A.C. 23 Jul '19

23 Jul '19

I have sbcl too (switched to it after the clisp shenanigans started upon upgrading to v2.24): It does *not* crash, and I'm perfectly happy using sbcl. I was just impelled by curiosity to try and figure out what's wrong on the clisp side. On July 23, 2019 6:58:55 PM GMT+03:00, Michael Rice <limitcase(a)gmail.com> wrote: >Have you considered switching to Steel Bank Common Lisp (SBCL) to see >if it >also crashes? > >On Tue, Jul 23, 2019 at 10:51 AM Stuart Little <achirvasub(a)gmail.com> >wrote: > >> On Tue, Jul 23, 2019 at 05:03:19PM +0300, Stas Boukarev wrote: >> > Well, your clisp just happens to crash on that. >> > >> >> I understand that :), but the purpose was to gain some insight into >how or >> why it's happening. >> >> Perhaps I can hack the swank loading procedure to avoid this, for >> instance.But I'd need to understand the situation beyond the simple >> observation that there's a crash, hence the mailing list message. >> >> > On Tue, Jul 23, 2019 at 4:59 PM Stuart Little ><achirvasub(a)gmail.com> >> wrote: >> > > >> > > On Tue, Jul 23, 2019 at 04:52:00PM +0300, Stas Boukarev wrote: >> > > > It says that Clisp crashes with a segfault, nothing to do with >slime. >> > > > >> > > >> > > It does say that, but a follow-up: >> > > >> > > If I run through the procedure described at the end, of starting >swank >> from within clisp, there are no crashes with swank-v2.20 (rather than >2.24). >> > > >> > > I do get a warning in emacs to the effect that swank (2.20) and >slime >> (2.24) versions don't match, but once I confirm that the crashes go >away. >> > > >> > > So this same clisp installation works fine with swank 2.20 and >not >> swank 2.24, meaning that some change in the latter is what's causing >this. >> > > >> > > > On Tue, Jul 23, 2019 at 4:30 PM Stuart Little ><achirvasub(a)gmail.com> >> wrote: >> > > > > >> > > > > I am running >> > > > > >> > > > > - emacs 26.2 >> > > > > - slime 2.24 >> > > > > - clisp 2.49 >> > > > > >> > > > > on Linux. >> > > > > >> > > > > 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 >> > > > > >> > > > > The inferior-lisp buffer reads as follows after the >disconnect: >> > > > > >> > > > > --- buffer starts --- >> > > > > >> > > > > (progn (load >> >"/home/chirvasitua/quicklisp/dists/quicklisp/software/slime-v2.24/swank-loader.lisp" >> :verbose t) (funcall (read-from-string "swank-loader:init") >:from-emacs t) >> (funcall (read-from-string "swank:start-server") "/tmp/slime.19223")) >> > > > > >> > > > > i i i i i i i ooooo o ooooooo ooooo >ooooo >> > > > > I I I I I I I 8 8 8 8 8 o 8 > 8 >> > > > > I \ `+' / I 8 8 8 8 8 > 8 >> > > > > \ `-+-' / 8 8 8 ooooo >8oooo >> > > > > `-__|__-' 8 8 8 8 8 >> > > > > | 8 o 8 8 o 8 8 >> > > > > ------+------ ooooo 8oooooo ooo8ooo ooooo 8 >> > > > > >> > > > > Welcome to GNU CLISP 2.49 (2010-07-07) ><http://clisp.cons.org/> >> > > > > >> > > > > Copyright (c) Bruno Haible, Michael Stoll 1992, 1993 >> > > > > Copyright (c) Bruno Haible, Marcus Daniels 1994-1997 >> > > > > Copyright (c) Bruno Haible, Pierpaolo Bernardi, Sam Steingold >1998 >> > > > > Copyright (c) Bruno Haible, Sam Steingold 1999-2000 >> > > > > Copyright (c) Sam Steingold, Bruno Haible 2001-2010 >> > > > > >> > > > > Type :h and hit Enter for context help. >> > > > > >> > > > > [1]> >> > > > > ;; Loading file >> >/home/chirvasitua/quicklisp/dists/quicklisp/software/slime-v2.24/swank-loader.lisp >> ... >> > > > > ;; Loaded file >> >/home/chirvasitua/quicklisp/dists/quicklisp/software/slime-v2.24/swank-loader.lisp >> > > > > ;; Loading file >> /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/packages.fas >... >> > > > > ;; Loaded file >> /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/packages.fas >> > > > > ;; Loading file >> /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/backend.fas >... >> > > > > ;; Loaded file >> /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/backend.fas >> > > > > ;; Loading file >> /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/xref.fas ... >> > > > > ;; Loaded file >> /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/xref.fas >> > > > > ;; Loading file >> /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/metering.fas >... >> > > > > ;; Loaded file >> /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/metering.fas >> > > > > ;; Loading file >> /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/clisp.fas >... >> > > > > WARNING: DEFUN/DEFMACRO: redefining function BREAK in >> > > > > >> /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/clisp.fas, >> > > > > was defined in >/builddir/clisp-2.49/src/condition.fas >> > > > > WARNING: Replacing method #<STANDARD-METHOD (#<BUILT-IN-CLASS >T>)> >> in >> > > > > #<STANDARD-GENERIC-FUNCTION EMACS-INSPECT> >> > > > > ;; Loaded file >> /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/clisp.fas >> > > > > ;; Loading file >> /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/gray.fas ... >> > > > > WARNING: The generic function #<STANDARD-GENERIC-FUNCTION >> STREAM-LINE-COLUMN> >> > > > > is being modified, but has already been called. >> > > > > WARNING: The generic function #<STANDARD-GENERIC-FUNCTION >> STREAM-FORCE-OUTPUT> >> > > > > is being modified, but has already been called. >> > > > > WARNING: The generic function #<STANDARD-GENERIC-FUNCTION >> STREAM-LINE-COLUMN> >> > > > > is being modified, but has already been called. >> > > > > ;; Loaded file >> /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/gray.fas >> > > > > ;; Loading file >> /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/match.fas >... >> > > > > ;; Loaded file >> /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/match.fas >> > > > > ;; Loading file >> /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/rpc.fas ... >> > > > > ;; Loaded file >> /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/rpc.fas >> > > > > ;; Loading file >> /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/swank.fas >... >> > > > > ;; Loaded file >> /home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/swank.fas >> > > > > 0 errors, 5 warnings >> > > > > ;; Swank started at port: 41975. >> > > > > CL-USER> >> > > > > ;; Loading file >> >/home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-trace-dialog.fas >> ... >> > > > > ;; Loaded file >> >/home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-trace-dialog.fas >> > > > > ;; Loading file >> >/home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-package-fu.fas >> ... >> > > > > ;; Loaded file >> >/home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-package-fu.fas >> > > > > ;; Loading file >> >/home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-presentations.fas >> ... >> > > > > ;; Loading file >> >/home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-repl.fas >> ... >> > > > > WARNING: The generic function >> > > > > #<STANDARD-GENERIC-FUNCTION THREAD-FOR-EVALUATION> >is >> being modified, >> > > > > but has already been called. >> > > > > WARNING: Replacing method >> > > > > #<STANDARD-METHOD >> > > > > (#<STRUCTURE-CLASS MULTITHREADED-CONNECTION> (EQL >> :FIND-EXISTING))> >> > > > > in #<STANDARD-GENERIC-FUNCTION >THREAD-FOR-EVALUATION> >> > > > > ;; Loaded file >> >/home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-repl.fas >> > > > > ;; Loaded file >> >/home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-presentations.fas >> > > > > ;; Loading file >> >/home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-macrostep.fas >> ... >> > > > > ;; Loaded file >> >/home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-macrostep.fas >> > > > > ;; Loading file >> >/home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-fuzzy.fas >> ... >> > > > > ;; Loading file >> >/home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-util.fas >> ... >> > > > > ;; Loaded file >> >/home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-util.fas >> > > > > ;; Loading file >> >/home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-c-p-c.fas >> ... >> > > > > ;; Loaded file >> >/home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-c-p-c.fas >> > > > > ;; Loaded file >> >/home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-fuzzy.fas >> > > > > ;; Loading file >> >/home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-fancy-inspector.fas >> ... >> > > > > ;; Loaded file >> >/home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-fancy-inspector.fas >> > > > > ;; Loading file >> >/home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-arglists.fas >> ... >> > > > > WARNING: Test failed: (&KEY #'#'+) => "(&key (function >#'+))" >> > > > > Expected: One of: "(&key (function #'+))", "(&key >> (function (function >> > > > > +)))" >> > > > > ;; Loaded file >> >/home/chirvasitua/.slime/fasl/2.24/clisp-2.49-unix-pc386/contrib/swank-arglists.fas >> > > > > >> > > > > Process inferior-lisp segmentation fault >> > > > > >> > > > > --- buffer ends --- >> > > > > >> > > > > More information: >> > > > > >> > > > > - starting clisp in a terminal all on its own seems to work >fine; >> I haven't had segmentation faults using it in isolation from slime. >> > > > > >> > > > > - I tried to start the server from within clisp and connect >to it: >> > > > > >> > > > > (a) rlwrap clisp >> > > > > (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 >> > > > > >> >> -- Sent from my Android device with K-9 Mail. Please excuse my brevity.

1 0

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

slime-devel