- slime-devel - mailman3.common-lisp.net

How to save process threads when using source code blocks in org-mode's babel?
by Mirko Vukovic 05 Apr '16

05 Apr '16

Hello, This is on Windows, on a several months old Slime. I am using org-mode's babel with the lisp module to document a data analysis project. In one of the first code blocks I initialize a stream that communicates with GNUPlot. Subsequent blocks (BEGIN_SRC...END_SRC) send plot commands, one plot per code block. In a slime session, I can generate multiple plots communicating with that one stream. But in the org-mode, after successfully creating the first plot, the subsequent ones raise the error that the stream is private to a thread. So I have to restart GNUplot for each plot. In a previous email exchange on the list (unrelated to org-mode) it was pointed out that executing code via REPL in Slime uses a different thread then executing code from a lisp buffer. I assume something like that is going on here as well. So, is there a way for me to store the process thread which invoked GNUplot, and use that one for execution of subsequent code blocks? Thanks, Mirko

2 2

Can't locate module: SWANK-IO-PACKAGE::SWANK-MACROSTEP
by David Hodge 31 Mar '16

31 Mar '16

Hi there, I recently upgraded slime via melpa and restarting emacs produced this message: " Can't locate module: SWANK-IO-PACKAGE::SWANK-MACROSTEP" and puts me into the common lisp debugger. Quitting the debugger aborts the slime start up. I can see the swank macrostep source in the distribution ( but it has not been compiled yet I think) so I am hoping someone more knowledgable might be able to advise me how to debug this? Best Regards

2 1

Removing SLIME's ChangeLog files
by Luís Oliveira 25 Mar '16

25 Mar '16

Hello, I'm considering removing SLIME's ChangeLog files. If you have an opinion about that, please make yourself heard over at https://github.com/slime/slime/pull/308. Cheers, -- Luís Oliveira http://kerno.org/~luis/

2 2

Re: SLIME 2.17 and macrostep on MELPA stable: needs 0.9, only 0.8 available?
by Stas Boukarev 03 Mar '16

03 Mar '16

On Thu, Mar 3, 2016 at 12:56 PM, Georges Ko <gko(a)gko.net> wrote: >> Slime ships macrostep.el, so, how come MELPA doesn't like it? (I don't > use MELPA). > > In slime.el, there is: > > ;; Package-Requires: ((cl-lib "0.5") (macrostep "0.9")) So then it becomes a bit silly, no point in bundling a package if it can't be used. I would say MELPA should just have the latest macrostep. -- With best regards, Stas.

2 1

SLIME 2.17 and macrostep on MELPA stable: needs 0.9, only 0.8 available?
by Georges Ko 03 Mar '16

03 Mar '16

Hello, When trying to install SLIME 2.17 on MELPA stable, it needs macrostep-0.9, but only 0.8 is available. Can this explicit dependency be removed in SLIME, as macrostep.el is already in lib? Or make 0.9 available on MELPA stable? Georges -- Georges KO (gko(a)gko.net)

2 2

SLIME and in-package
by Peter Keller 10 Feb '16

10 Feb '16

Hello, I have a question, hopefully easy, but I can't seem to find the answer. I'd like to evaluate a region which contains something like this: (asdf:load-system '#:foo) (in-package #'foo) and have my slime REPL actually change its current package. I realize that some problems can happen with the above, which led me to this page: http://stackoverflow.com/questions/27095320/common-lisp-how-to-get-in-packa… When I rewrite the above to (eval-when (:compile-toplevel :load-toplevel :execute) (asdf:load-ssytem '#:foo)) (in-package #'foo) It loads the package, but can't change the current REPL package to it, SLIME continues to say CL-USER. I also realize that slime may be LOADing the file, which preserves the current package. Since I get a => <PACKAGE "FOO"> in my *slime-events* buffer I think that may be also happening. Is there any way to change the current REPL package by using any SLIME evaluation methods that involve evaluating a region? Or must I either manually type (in-package :foo) in the REPL or use the ,in-package SLIME command helper. I'm just about to write some elisp to take the region, find the slime repl buffer, manually append the region into the REPL buffer, and enter a return to execute it! There must be a better way! Thank you! -pete

4 4

Re: SLIME and in-package
by Peter Keller 07 Feb '16

07 Feb '16

Hello, I deeply apologize for the multiple emails. Apparently, you can author a filter in Thunderbird which will take your partially written message and cause it to be sent (!!!) instead of stored in drafts.... ----- Anyways, he comes from slimv on vim where you can apparently eval the paragraph of code I had written previously and the repl would go into the package. He was curious of he could do it in SLIME too. Thank you! -pete

2 2

Reloading slime.el upon starting SLIME.
by Dmitry Igrishin 14 Dec '15

14 Dec '15

Hello, Recently after switching branches in my SLIME Git repo I caught a message about slime/swank versions inconsistence. Presently SLIME urges to recompile slime.el if slime.elc is found and it older the slime.el, but it does not reloads slime.el automatically if it has been changed. The first solution which comes to the mind is the store md5 hashsum of the current slime.el and check it every time of SLIME loading. Thoughts?

2 2

macroexpansion (slime-expand-1) results in error
by Mirko Vukovic 13 Dec '15

13 Dec '15

C-c Ret returns an error on some macros (but not on others): The value NIL is not of the expected type ARRAY. [Condition of type TYPE-ERROR] Restarts: 0: [*ABORT] Return to SLIME's top level. 1: [ABORT-BREAK] Reset this thread 2: [ABORT] Kill this thread Backtrace: 0: (CCL::ARRAY-DATA-AND-OFFSET NIL) 1: (MAKE-STRING-INPUT-STREAM NIL 0 0) 2: (READ-FROM-STRING NIL T NIL :START 0 :END NIL :PRESERVE-WHITESPACE NIL) 3: ((:INTERNAL SWANK::FROM-STRING)) As stated above on other macros it works fine. This is on latest CCL release on 64-bit Windows 7, slime 2015-10-18. I don't know how to generate more debugging information. Any thoughts? Thanks, Mirko

3 11

Slime startup sometimes: Undefined function SWANK::SYMBOL-INDENTATION
by Mark H. David 12 Dec '15

12 Dec '15

I frequently see this (see debugger backtrace below) when starting SLIME. Not all the time. I suspect it's a timing issue. Anyone see this? Anyone looked into fixing? Thanks, --Mark Undefined function SWANK::SYMBOL-INDENTATION called with arguments (:BREAK-OPTIONS-STRING) . [Condition of type CCL::UNDEFINED-FUNCTION-CALL] Restarts: 0: [CONTINUE] Retry applying SWANK::SYMBOL-INDENTATION to (:BREAK-OPTIONS-STRING). 1: [USE-VALUE] Apply specified function to (:BREAK-OPTIONS-STRING) this time. 2: [STORE-VALUE] Specify a function to use as the definition of SWANK::SYMBOL-INDENTATION. 3: [ABORT-BREAK] Reset this thread 4: [ABORT] Kill this thread Backtrace: 0: ((:INTERNAL SWANK::CONSIDER SWANK::UPDATE-INDENTATION/DELTA-FOR-EMACS) :BREAK-OPTIONS-STRING) 1: (#<Anonymous Function #x302000BD1E4F> :BREAK-OPTIONS-STRING) 2: (CCL::APPLY-TO-HTAB-SYMS #<COMPILED-LEXICAL-CLOSURE #x2389553F> #(:NFRAMES #<Unbound> :CODE 0 :PAUSE-PERIOD 0 ...)) 3: (CCL::ITERATE-OVER-PRESENT-SYMBOLS #<Package "KEYWORD"> #<COMPILED-LEXICAL-CLOSURE #x2389553F>) 4: (CCL::ITERATE-OVER-ALL-SYMBOLS #<COMPILED-LEXICAL-CLOSURE #x2389553F>) 5: (SWANK::UPDATE-INDENTATION/DELTA-FOR-EMACS #<HASH-TABLE :TEST EQ size 228/305 #x302000AC574D> (#<Package "X86-DARWIN64"> #<Package "X8664"> #<Package "KEYWORD"> #<Package "CCL"> ..) #<Package "COMMON-.. 6: (SWANK::PERFORM-INDENTATION-UPDATE #<MULTITHREADED-CONNECTION #x302000AC56AD> (#<Package "X86-DARWIN64"> #<Package "X8664"> #<Package "KEYWORD"> #<Package "CCL"> #<Package "COMMON-LISP"> ..) #<Package.. 7: ((:INTERNAL SWANK::INDENTATION-CACHE-LOOP)) 8: (SWANK/BACKEND:CALL-WITH-DEBUGGER-HOOK #<Compiled-function SWANK:SWANK-DEBUGGER-HOOK #x302000A414FF> #<COMPILED-LEXICAL-CLOSURE (:INTERNAL SWANK::INDENTATION-CACHE-LOOP) #x302000ACFD1F>) 9: (SWANK::INDENTATION-CACHE-LOOP #<MULTITHREADED-CONNECTION #x302000AC56AD>) 10: (CCL::RUN-PROCESS-INITIAL-FORM #<PROCESS swank-indentation-cache-thread(6) [Active] #x302000AC982D> (#<COMPILED-LEXICAL-CLOSURE (:INTERNAL CCL::%PROCESS-RUN-FUNCTION) #x302000AC95BF>)) 11: ((:INTERNAL (CCL::%PROCESS-PRESET-INTERNAL (PROCESS))) #<PROCESS swank-indentation-cache-thread(6) [Active] #x302000AC982D> (#<COMPILED-LEXICAL-CLOSURE (:INTERNAL ..))) 12: ((:INTERNAL CCL::THREAD-MAKE-STARTUP-FUNCTION))

4 5