slime-devel November 2015

slime-devel@common-lisp.net

7 participants
5 discussions

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

New Maintainer.
by Helmut Eller 27 Nov '15

27 Nov '15

I'm resigning as maintainer. The new maintainer is Stas Boukarev. Helmut

2 2

reconnecting and *GLOBALLY-REDIRECT-IO*
by mega＠retes.hu 26 Nov '15

26 Nov '15

Hi If I connect to a swank server starting simply with: (require :swank) (swank:create-server :port 4095 :dont-close t) and evaluate an output producing form such as: (loop (format t "~S~%" *standard-output*) (sleep 2)) then the output is printed to the repl, but after disconnecting and connecting again the output no longer makes it there. This is seemingly regardless of the value of *GLOBALLY-REDIRECT-IO* (set in ~/.swank.lisp) which is contradicting the documentation at https://common-lisp.net/project/slime/doc/html/Global-IO-Redirection.html Is there a way to get standard streams redirected to the new repl upon reconnect? Thanks, Gabor

5 10

Re: [named-readtables] in-readtable does not touch swank:*readtable-alist* anymore (#8)
by 73budden . 06 Nov '15

06 Nov '15

> Skimming through that slime-devel thread, it's not clear there is a consensus on whether this is the right approach. There is consensus about two things: 1. Understanding readtables in SLIME is useful and desired 2. Frobbing made by (in-readtable) is kludgy and potentially harmful. But I'm not sure people understood that the change I suggest is breaking. Currently, once readtable is associated to a package, every file with that package implies that readtable due to record in *readtable-alist*. So it is enough to issue (in-readtable) once in the package and it sticks to that package until changed. After suggested modification to SLIME and NAMED-READATBLES, explicit in-readtable form is required at every file, and also every time we issue in-package form in REPL. We are also free to add records to *readtable-alist* manually. How will user adapt to suggested modifications? Simplest way is to fill *readtable-alist* in his initialization file.

2 1

using (in-readtable) to select a readtable
by 73budden . 05 Nov '15

05 Nov '15

Hi! I've made some changes so that one can specify a readtable on a per-file basis. It seems to work. Code can be found here: https://bitbucket.org/budden/budden-slime Sorry I'm new to git so I had some problems with cr/lf on Windows. I'd like to get some feedback.

6 24

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

slime-devel November 2015