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

[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] M-. vs readtable on SBCL
by mega＠retes.hu 27 Jan '15

27 Jan '15

Compile a file with these contents: ------------------------------------- (cl:defpackage :xxx (:use #:common-lisp)) (in-package :xxx) (named-readtables:in-readtable pythonic-string-reader:pythonic-string-syntax) (defun foo () """ "#<>" """) (defun bar ()) ------------------------------------- Press M-. on BAR, it works. Open the scratch buffer, type XXX::BAR and press M-. on it to get (with *DEBUG-SWANK-BACKEND* T): ------------------------------------- illegal sharp macro character: #\< Line: 9, Column: 11, File-Position: 167 Stream: #<SB-IMPL::STRING-INPUT-STREAM {102387D1B3}> [Condition of type SB-INT:SIMPLE-READER-ERROR] Restarts: 0: [*ABORT] Return to SLIME's top level. 1: [ABORT] abort thread (#<THREAD "worker" RUNNING {102386D683}>) Backtrace: 0: ((FLET SWANK/BACKEND:CALL-WITH-DEBUGGING-ENVIRONMENT :IN "/home/mega/quicklisp/local-projects/slime/swank/sbcl.lisp") #<FUNCTION (LAMBDA NIL :IN SWANK::DEBUG-IN-EMACS) {1007266DEB}>) 1: (SWANK::DEBUG-IN-EMACS #<SB-INT:SIMPLE-READER-ERROR "illegal sharp macro character: ~S" {102387D713}>) 2: (SWANK:INVOKE-SLIME-DEBUGGER #<SB-INT:SIMPLE-READER-ERROR "illegal sharp macro character: ~S" {102387D713}>) 3: (SWANK/SBCL::CALL-WITH-BREAK-HOOK #<FUNCTION SWANK:SWANK-DEBUGGER-HOOK> #<CLOSURE (LAMBDA NIL :IN SWANK:SWANK-DEBUGGER-HOOK) {102387E08B}>) 4: ((FLET SWANK/BACKEND:CALL-WITH-DEBUGGER-HOOK :IN "/home/mega/quicklisp/local-projects/slime/swank/sbcl.lisp") #<FUNCTION SWANK:SWANK-DEBUGGER-HOOK> #<CLOSURE (LAMBDA NIL :IN SWANK:SWANK-DEBUGGER-HOOK).. 5: (SWANK:SWANK-DEBUGGER-HOOK #<SB-INT:SIMPLE-READER-ERROR "illegal sharp macro character: ~S" {102387D713}> #<unavailable argument>) 6: (SB-DEBUG::RUN-HOOK *DEBUGGER-HOOK* #<SB-INT:SIMPLE-READER-ERROR "illegal sharp macro character: ~S" {102387D713}>) 7: (INVOKE-DEBUGGER #<SB-INT:SIMPLE-READER-ERROR "illegal sharp macro character: ~S" {102387D713}>) 8: (ERROR SB-INT:SIMPLE-READER-ERROR :STREAM #<SB-IMPL::STRING-INPUT-STREAM {102387D1B3}> :FORMAT-CONTROL "illegal sharp macro character: ~S" :FORMAT-ARGUMENTS (#\<)) 9: (SB-INT:SIMPLE-READER-ERROR #<SB-IMPL::STRING-INPUT-STREAM {102387D1B3}> "illegal sharp macro character: ~S" #\<) 10: (SB-IMPL::SHARP-ILLEGAL #<SB-IMPL::STRING-INPUT-STREAM {102387D1B3}> #\< #<unavailable argument>) 11: (SB-IMPL::READ-MAYBE-NOTHING #<SB-IMPL::STRING-INPUT-STREAM {102387D1B3}> #\#) 12: (SB-IMPL::READ-LIST #<SB-IMPL::STRING-INPUT-STREAM {102387D1B3}> #<unavailable argument>) 13: (SB-IMPL::READ-MAYBE-NOTHING #<SB-IMPL::STRING-INPUT-STREAM {102387D1B3}> #\() 14: (SB-IMPL::%READ-PRESERVING-WHITESPACE #<SB-IMPL::STRING-INPUT-STREAM {102387D1B3}> T (NIL) T) 15: (SB-IMPL::%READ-PRESERVING-WHITESPACE #<SB-IMPL::STRING-INPUT-STREAM {102387D1B3}> T (NIL) NIL) 16: (SB-IMPL::%READ-PRESERVING-WHITESPACE #<SB-IMPL::STRING-INPUT-STREAM {102387D1B3}> T (NIL) NIL) [tl,external] 17: (READ #<SB-IMPL::STRING-INPUT-STREAM {102387D1B3}> T NIL NIL) 18: (SWANK/SOURCE-PATH-PARSER::SKIP-TOPLEVEL-FORMS 4 #<SB-IMPL::STRING-INPUT-STREAM {102387D1B3}>) 19: (SWANK/SOURCE-PATH-PARSER:READ-SOURCE-FORM 4 #<SB-IMPL::STRING-INPUT-STREAM {102387D1B3}>) 20: (SWANK/SOURCE-PATH-PARSER::SOURCE-PATH-STREAM-POSITION (4) #<SB-IMPL::STRING-INPUT-STREAM {102387D1B3}>) 21: (SWANK/SOURCE-PATH-PARSER:SOURCE-PATH-STRING-POSITION (4) "(cl:defpackage :xxx ..) 22: (SWANK/SBCL::CALL-WITH-DEBOOTSTRAPPING #<CLOSURE (LAMBDA NIL :IN SWANK/SBCL::SOURCE-FILE-POSITION) {102387D19B}>) 23: (SWANK/SBCL::SOURCE-FILE-POSITION "/home/mega/own/mgl-pax/src/x.lisp" 3631296724 (4)) 24: (SWANK/SBCL::DEFINITION-SOURCE-FILE-LOCATION #S(SB-INTROSPECT:DEFINITION-SOURCE :PATHNAME #P"/home/mega/own/mgl-pax/src/x.lisp" :FORM-PATH (4) :CHARACTER-OFFSET 177 :FILE-WRITE-DATE 3631296724 :PLIST .. 25: ((FLET SWANK/BACKEND:FIND-DEFINITIONS :IN "/home/mega/quicklisp/local-projects/slime/swank/sbcl.lisp") XXX::BAR) 26: (SWANK:FIND-DEFINITIONS-FOR-EMACS "xxx::bar") 27: (SB-INT:SIMPLE-EVAL-IN-LEXENV (SWANK:FIND-DEFINITIONS-FOR-EMACS "xxx::bar") #<NULL-LEXENV>) 28: (EVAL (SWANK:FIND-DEFINITIONS-FOR-EMACS "xxx::bar")) 29: (SWANK:EVAL-FOR-EMACS (SWANK:FIND-DEFINITIONS-FOR-EMACS "xxx::bar") "COMMON-LISP-USER" 381) ------------------------------------- So the source location has the index of the top-level form in the file (4) and swank tries to skip some forms by reading which, even with *READ-SUPPRESS* T, fails on #<. There are three options that I can see: A. Make SOURCE-FILE-POSITION find the right readtable for the file. Currently has logic for SB! only. B. Record the absolute position of the form in the file. C. Apply some heuristics to SKIP-TOPLEVEL-FORMS. OK. C is ugly and fragile, B is just fragile, A requires changes in both NAMED-READTABLES and SLIME/SWANK. Perhaps, you have better ideas? Cheers, Gabor

3 8

[Slime-devel] M-. and interning
by Zach Beane 27 Jan '15

27 Jan '15

If I load a file like this: (defpackage xach (:use cl)) (in-package xach) (defun attack () 'attack) Then do: > (apropos "attack") XACH::ATTACK (fbound) ; No value Then if I M-. on XACH::ATTACK, it jumps to the definition as expected. But then: > (apropos "attack") ATTACK XACH::ATTACK (fbound) ; No value Why does ATTACK get interned in the current package? Thanks, Zach

3 2

[Slime-devel] Stepping in sbcl when using the Slime debugger.
by Michael Malis 21 Jan '15

21 Jan '15

I posted this as a question to Stack Overflow <http://stackoverflow.com/questions/27889989/stepping-in-sbcl-from-within-th…> (follow the link to see the description). Basically I'm trying to single step after hitting a break point with sbcl and Slime. I was able to do what I want in sbcl without using Slime by using 'start' debugger command. As far as I can tell, there is no way to use that command from the Slime debugger. Can someone tell me if I am missing something obvious or if it is currently is not possible to step after breaking with sbcl and Slime?

2 2

[Slime-devel] Fwd: cutting and pasting S-expressions from buffer to REPL (fwd)
by Faheem Mitha 05 Jan '15

05 Jan '15

Hi, I had an earlier wishlist item in 2012, which I wrote to slime-devel about (see my post quoted below). João has kindly implemented this in his SLY project. I was wondering if the SLIME devs would consider adding a similar feature, or just copying João's feature. I'm sure he'll give you all the relevant information. Thank you for your consideraion. Regards, Faheem Mitha ---------- Forwarded message ---------- Date: Mon, 29 Dec 2014 00:19:17 +0000 From: João Távora <joaotavora(a)gmail.com> To: faheem(a)faheem.info Subject: Fwd: [Slime-devel] cutting and pasting S-expressions from buffer to REPL Hi, I've found this idea useful so I've added the feature that Faheem described to SLY's `sly-mrepl-sync` command. SLY is a fork/clone of SLIME with a cleaner UI and more features. See https://github.com/capitaomorte/sly and read the NEWS.md file at https://github.com/capitaomorte/sly/blob/master/NEWS.md if you're interested. Bye, João On Sat, Dec 27, 2014 at 4:19 AM, Frank <kulugox(a)gmail.com> wrote: > Faheem Mitha <faheem(a)faheem.info> writes: > >> 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 >> > I found "M-x slime-eval-last-expression" in other buffer is an > alternative way to achieve. > > -- > Sincerely, > Frank > > > _______________________________________________ > Slime-devel mailing list > Slime-devel(a)common-lisp.net > http://mailman.common-lisp.net/cgi-bin/mailman/listinfo/slime-devel -- João Távora -- João Távora

2 1

[Slime-devel] SLIME 2.12
by Luís Oliveira 02 Jan '15

02 Jan '15

Hello all, SLIME 2.12 is released! https://github.com/slime/slime/releases/tag/v2.12 * 2.12 (January 2015) ** Core A couple of regression introduced in version 2.10 were fixed. *** slime-compile-buffer (C-c C-k) no longer tries to save every buffer *** slime-autodoc-mode doesn't spam the minibuffer anymore ** SWANK *** CREATE-SERVER provides interactive restarts when port is taken Thanks to Adlai Chandrasekhar. (PR #204.) ** slime-fuzzy New variable *FUZZY-DUPLICATE-SYMBOL-FILTER* allows customization of how symbols accessible from multiple packages should be canonicalized. Defaults to :NEAREST-PACKAGE, a departure from the previous default behaviour which is still available using :HOME-PACKAGE. The new behaviour expands "ui:e-l" to "uiop:ensure-list" rather than "uiop/utility:ensure-list". Consult the manual for other options and other details. Thanks to Ivan Shvedunov. (PR #205.) Happy new year, -- Luís Oliveira http://kerno.org/~luis/

1 0