slime-devel March 2013

slime-devel@common-lisp.net

11 participants
12 discussions

[slime-devel] SLIME talk at the Emacs Conference
by Luke Gorrie 08 Apr '15

08 Apr '15

Howdy! Long time no chat :-) I will give a talk at the Emacs Conference (emacsconf.org, London March 31) called "How to write an Emacs-based IDE like SLIME". The idea is to demo SLIME, explain how its development works, and give some encouragement and practical tips to people who might want to build something similar for other languages. If you have some ideas please fire away :) particularly about things I might easily overlook being as my SLIME know-how is about 10 years old! Cheers, -Luke

2 2

[slime-devel] cutting and pasting S-expressions from buffer to REPL
by Faheem Mitha 27 Dec '14

27 Dec '14

Hello everyone, I've recently started using SLIME with SBCl on Debian, where SLIME defaults to using SBCL, at least when it is installed. So far I am very impressed. I haven't been able to take off and fly yet, but I'm on the runway.:-) I'm particularly impressed by the underlining source which has compile errors, and doing a popup on mouseover feature. I don't know whose idea this was, but it is pretty damn cool. Does anyone know the history of this feature? So, I have a question about SLIME. When debugging, or indeed otherwise, I find it useful to copy and paste S-expressions from a buffer to the REPL. I've been using the mouse for this, which is decidedly sub-optimal. I hate using the mouse. I was thinking that it would be handy to have a command which would copy and paste S-expressions from a buffer to the REPL, while at the same time switching the buffer to the REPL. The S-expression would be chosen by having the cusor to the right of the closing expression. I'm not sure if this position has a name. I don't know if this command already exists. I could not find it in the manual. If it doesn't, could someone tell me what code would tell emacs to do this? My knowledge of Emacs programming is non-existent. Please CC me on any reply. Thanks. Regards, Faheem

6 14

[slime-devel] [PATCH] hiding swank frames from debugger backtrace on Allegro
by Luís Oliveira 02 Apr '13

02 Apr '13

Hello, As you well know, SLIME's debugger, when invoked, will inevitably add some frames to the current stack, which SWANK attempts to hide. On Allegro, when signalling an error from the REPL, those extra frames look something like this: 0: ((FLET (:TOP-LEVEL-FORM "swank-allegro.lisp" 4123) SWANK- BACKEND:CALL-WITH-DEBUGGING-ENVIRONMENT) #<Function (:INTERNAL SWANK::DEBUG-IN-EMACS 0)>) 1: (SWANK-BACKEND:CALL-WITH-DEBUGGING-ENVIRONMENT #<Function (:INTERNAL SWANK::DEBUG-IN-EMACS 0)>) 2: (SWANK::DEBUG-IN-EMACS #<SIMPLE-ERROR @ #x218114d2>) 3: (SWANK:INVOKE-SLIME-DEBUGGER #<SIMPLE-ERROR @ #x218114d2>) 4: ((:INTERNAL SWANK:SWANK-DEBUGGER-HOOK 1)) 5: ((:INTERNAL (:TOP-LEVEL-FORM "swank-backend.lisp" 32198) 0) #<Function SWANK-DEBUGGER-HOOK> #<Closure (:INTERNAL SWANK:SWANK- DEBUGGER-HOOK 1) @ #x218115f2>) 6: (SWANK-BACKEND:CALL-WITH-DEBUGGER-HOOK #<Function SWANK- DEBUGGER-HOOK> #<Closure (:INTERNAL SWANK:SWANK-DEBUGGER-HOOK 1) @ #x218115f2>) 7: (SWANK:SWANK-DEBUGGER-HOOK #<SIMPLE-ERROR @ #x218114d2> #<Function SWANK-DEBUGGER-HOOK>) 8: (ERROR "foo") In this case, FIND-TOPLEVEL in swank-allegro.lisp successfully figures out that the first 8 frames are to be hidden. However, if the error comes from some other thread -- this can be reproduced via (mp:process-run-function nil (lambda () (error "foo"))) for example -- there will a couple of extra frames: 0: ((FLET (:TOP-LEVEL-FORM "swank-allegro.lisp" 4123) SWANK- BACKEND:CALL-WITH-DEBUGGING-ENVIRONMENT) #<Function (:INTERNAL SWANK::DEBUG-IN-EMACS 0)>) 1: (SWANK-BACKEND:CALL-WITH-DEBUGGING-ENVIRONMENT #<Function (:INTERNAL SWANK::DEBUG-IN-EMACS 0)>) 2: (SWANK::DEBUG-IN-EMACS #<SIMPLE-ERROR @ #x21552f92>) 3: ((:INTERNAL SWANK:INVOKE-SLIME-DEBUGGER 0)) 4: ((:INTERNAL (:TOP-LEVEL-FORM "swank-backend.lisp" 32198) 0) #<Function SWANK-DEBUGGER-HOOK> #<Closure (:INTERNAL SWANK:INVOKE-SLIME-DEBUGGER 0) @ #x215530e2>) 5: (SWANK-BACKEND:CALL-WITH-DEBUGGER-HOOK #<Function SWANK- DEBUGGER-HOOK> #<Closure (:INTERNAL SWANK:INVOKE-SLIME-DEBUGGER 0) @ #x215530e2>) 6: ((:INTERNAL SWANK:INVOKE-SLIME-DEBUGGER 3)) 7: (SWANK::CALL-WITH-BINDINGS ..) 8: (SWANK:INVOKE-SLIME-DEBUGGER #<SIMPLE-ERROR @ #x21552f92>) 9: ((:INTERNAL SWANK:SWANK-DEBUGGER-HOOK 1)) 10: ((:INTERNAL (:TOP-LEVEL-FORM "swank-backend.lisp" 32198) 0) #<Function SWANK-DEBUGGER-HOOK> #<Closure (:INTERNAL SWANK:SWANK- DEBUGGER-HOOK 1) @ #x2155309a>) 11: (SWANK-BACKEND:CALL-WITH-DEBUGGER-HOOK #<Function SWANK- DEBUGGER-HOOK> #<Closure (:INTERNAL SWANK:SWANK-DEBUGGER-HOOK 1) @ #x2155309a>) 12: (SWANK:SWANK-DEBUGGER-HOOK #<SIMPLE-ERROR @ #x21552f92> #<Function SWANK-DEBUGGER-HOOK>) 13: (ERROR "foo") Because FIND-TOPLEVEL currently only looks at the first eleven frames, it will fail to find frame #12 in the stacktrace above. Consequently, the extra debugger frames won't be hidden. The attached patch fixes this by looking a bit further (30 frames) taking care not to fail on small stacks. I considered the idea of not hard-coding an arbitrary limit, but in the end went with the more conservative fix since walking through a very large stack takes a while. (However, it seems unlikely that FIND-TOPFRAME would ever be called in a context where SWANK-DEBUGGER-HOOK is not on the stack, modulo protocol changes that would break the whole scheme anyway.) Cheers, -- Luís Oliveira http://r42.eu/~luis

2 1

[slime-devel] patch for "Failed test on CCL"
by Ben Hyde 28 Mar '13

28 Mar '13

The issue reported in http://article.gmane.org/gmane.lisp.slime.devel/10751 i.e. that when using CCL swank complains of a test failing upon a fresh connection maybe resolved by adding #+ccl (ccl::*print-abbreviate-quote* t) as shown: (defun decoded-arglist-to-string (decoded-arglist &key operator highlight print-right-margin) (with-output-to-string (*standard-output*) (with-arglist-io-syntax (let ((*print-right-margin* print-right-margin) #+ccl (ccl::*print-abbreviate-quote* t)) (print-decoded-arglist decoded-arglist :operator operator :highlight highlight))))) - ben fyi ccl's *print-abbreviate-quote* is an extension, see also http://paste.lisp.org/display/136370

1 0

[slime-devel] Where to look the trace output ?
by z_axis 23 Mar '13

23 Mar '13

STUMPWM> *trace-output* #<SWANK-BACKEND::SLIME-OUTPUT-STREAM #x38924796> STUMPWM> (trace unmap-message-window) => NIL But i see no trace output after the message window disappears. Sincerely!

2 1

[slime-devel] Can i make slime enter the specified package once slime-connect successfully ?
by z_axis 22 Mar '13

22 Mar '13

Now i have to call (in-package :foo) after slime-connect ? Sincerely!

2 2

[slime-devel] Daily ChangeLog diff
by Helmut Eller 13 Mar '13

13 Mar '13

Index: slime/ChangeLog diff -u slime/ChangeLog:1.2396 slime/ChangeLog:1.2397 --- slime/ChangeLog:1.2396 Fri Mar 8 03:12:25 2013 +++ slime/ChangeLog Tue Mar 12 10:49:47 2013 @@ -1,3 +1,8 @@ +2013-03-12 Helmut Eller <heller(a)common-lisp.net> + + * slime.el (slime-read-interactive-args): Use read-shell-command + to enable completion. Patch by Daimrod/Greg. + 2013-03-08 Mark Evenson <evenson(a)tethys.local> * swank-abcl.lisp: Allow SLIME inspector to perform class

1 0

[slime-devel] [PATCH] Completion with C-u M-x slime
by Daimrod 12 Mar '13

12 Mar '13

Hi, Here is a small patch to enable completion on pathname with C-u M-x slime. -- Daimrod/Greg

2 1

[slime-devel] Daily ChangeLog diff
by Helmut Eller 09 Mar '13

09 Mar '13

Index: slime/ChangeLog diff -u slime/ChangeLog:1.2395 slime/ChangeLog:1.2396 --- slime/ChangeLog:1.2395 Fri Mar 1 17:17:09 2013 +++ slime/ChangeLog Fri Mar 8 03:12:25 2013 @@ -1,3 +1,8 @@ +2013-03-08 Mark Evenson <evenson(a)tethys.local> + + * swank-abcl.lisp: Allow SLIME inspector to perform class + finalization. + 2013-03-02 Stas Boukarev <stassats(a)gmail.com> * slime-autoloads.el: Don't load autoloads when slime is already

1 0

[slime-devel] sldb find-definition wrong package
by Lynn Quam 08 Mar '13

08 Mar '13

Sorry if I have missed a previous thread about this problem. I am running SLIME 2013-03-02 with SBCL-1.1.5 with :SB-THREADS on Mac OS X. In the SLIME debugger (sldb) I attempt to find the definition of a function shown in a stack frame and it fails with the message: "No known definition for: MERGE-SHARED-LIBRARY-PATHNAME-TYPE (in COMMON-LISP-USER)" That symbol is actually in my package QFFI.

2 1

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

slime-devel March 2013