slime-devel

slime-devel@common-lisp.net

4231 discussions

slime.el cleanup and a minor improvement
by joaotavora＠gmail.com 08 Apr '15

08 Apr '15

Hi, I'd like to push the three changes to SLIME's master branch. These effectively mark the end of XEmacs compatibility and are mostly about deleting code. They live in my fork, git@github.com:capitaomorte/slime.git, in the the `slime-el-cleanup' branch: commit b9dfcba7d59c56e7b6b8d38413bd8f8801b13da3 Remove XEmacs portability layer and fix some FIXMEs 44 0 ChangeLog 108 632 slime.el commit 92be40bcd47d640849f1df807d971cbe76b733c5 Redesign and simplify some window-managing code in slime.el 32 1 ChangeLog 80 212 slime.el commit 8951befc40df6f693f0606789c616f312442992a Improve window selection for popup buffers Use Emacs 24.3's window-managing API to do less surprising choices when popping up temporary SLIME buffers. This is innocuous on previous Emacs versions. 12 0 ChangeLog 20 5 slime.el The first is mostly a big cleanup of slime.el's XEmacs "portability layer", fixes some FIXME's and uses "declare" specs for indentation. It removes more than 500 lines in slime.el The second simplifies the slime-popup-* logic, targets more FIXME's and adapts some parts to more common idioms. The third commit adds 15 lines that, in my opinion, greatly improve window selection for popup buffers, but only on Emacs >= 24.3. They fix a common debugger annoyance: When I have my frame divided into 3+ windows, selecting restarts that immediatly trigger another debugger makes the SLDB buffer cycle between visible windows. This commit fixes that and subsequent SLDB buffers go to the same window if possible. The cleanup is relatively aggressive and, though neither I nor the automated tests have noticed it, it's likely that I broke something that I don't use regularly. Please test and review my changes. Except for the third commit, no functional changes should be observed. If you're acquainted with slime.el, point to the offending code whenever possible. Otherwise describe your use cases that were broken so I can fix it. Thanks, João

1 1

Save money. Official suppliers
by Meds USA 08 Apr '15

08 Apr '15

1 0

Fwd: Patch for customizing Allegro temp file and directory
by Luís Oliveira 08 Apr '15

08 Apr '15

[after João's message, I noticed that my longer response to Dave wasn't sent to the list. So here it goes.] ---------- Forwarded message ---------- From: Luís Oliveira <luismbo(a)gmail.com> Date: Sat, Feb 22, 2014 at 11:08 PM Subject: Re: Patch for customizing Allegro temp file and directory To: Dave Cooper <gendl(a)genworks.com> Hello Dave, On Fri, Feb 21, 2014 at 9:01 PM, Dave Cooper <gendl(a)genworks.com> wrote: > So with that approach, this would not be a Slime patch at all, but more of a > private patch to be maintained and installed individually at each Allegro site, right? Right. > Did you notice anything about if/how you work around the issue at your > place? Here's what we use at work: (excl:def-fwrapper fixed-temporary-directory () "Returns a temporary directory." (excl:pathname-as-directory (or (sys:getenv "TEMP") (sys:getenv "TMP") #+mswindows (if (>= (getf (excl::windows-major-version) :major-version) 6) "~\\AppData\\Local\\TEMP" "~\\Local Settings\\TEMP")))) (compile 'fixed-temporary-directory) (excl:fwrap 'sys:temporary-directory :fixed-temporary-directory 'fixed-temporary-directory) For some reason, it didn't occur to us to report this to Franz. Actually, I don't remember why this was necessary in the first place since in my machine at work, ACL seems to be returning the value of the TEMP environment variable, as the documentation suggests it should: <http://franz.com/support/documentation/current/doc/operators/system/tempora…>. HTH, -- Luís Oliveira http://kerno.org/~luis/

1 0

【活细胞既能抗衰老又能治病】--来自德国生物医学中心的　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　 59241
by 范雉瘗 08 Apr '15

08 Apr '15

1 0

Test This Out
by Drew C 08 Apr '15

08 Apr '15

This is just a test to make sure things are working as expected. -- drewc

1 0

[patch] Fix for Arg detection inside an "Apply" for functions where the lisp can't discover args
by Matthew Lamari 08 Apr '15

08 Apr '15

When in the IDE you type: (apply #'foo ... ... ...) When it autodocs the apply, swank attempts to show the "apply" with foo's params. Pretty impressive; but it didn't have a case for where #'foo's args can't be queried from the underlying lisp. Discovered this in lispworks, which can't give back the args for functions compiled under tightest settings. The underlying abstraction can return :NOT-AVAILABLE - most of the other cases look for this, the patch below filters out this case so as to not give it special handling. . . --- original/contrib/swank-arglists.lisp Sun Aug 11 16:49:36 2013 +++ replacement/contrib/swank-arglists.lisp Sat Aug 10 23:27:27 2013 @@ -916,26 +916,27 @@ (let ((function-arglist (compute-enriched-decoded-arglist function-name (cdr argument-forms)))) - (return-from compute-enriched-decoded-arglist - (values - (make-arglist :required-args - (list 'function) - :optional-args - (append - (mapcar #'(lambda (arg) - (make-optional-arg arg nil)) - (arglist.required-args function-arglist)) - (arglist.optional-args function-arglist)) - :key-p - (arglist.key-p function-arglist) - :keyword-args - (arglist.keyword-args function-arglist) - :rest - 'args - :allow-other-keys-p - (arglist.allow-other-keys-p function-arglist)) - (list function-name-form) - t))))))) + (unless (eq function-arglist :NOT-AVAILABLE) + (return-from compute-enriched-decoded-arglist + (values + (make-arglist :required-args + (list 'function) + :optional-args + (append + (mapcar #'(lambda (arg) + (make-optional-arg arg nil)) + (arglist.required-args function-arglist)) + (arglist.optional-args function-arglist)) + :key-p + (arglist.key-p function-arglist) + :keyword-args + (arglist.keyword-args function-arglist) + :rest + 'args + :allow-other-keys-p + (arglist.allow-other-keys-p function-arglist)) + (list function-name-form) + t)))))))) (call-next-method)) (defmethod compute-enriched-decoded-arglist

1 0

None
by Matthew Lamari 08 Apr '15

08 Apr '15

1 0

[Slime-devel] SLIME 2.13
by Luís Oliveira 04 Mar '15

04 Mar '15

Hello all, SLIME 2.13 is released! https://github.com/slime/slime/releases/tag/v2.13 * 2.13 (March 2015) ** Core *** slime-cycle-connections has been deprecated It has been replaced by slime-next-connection and slime-prev-connection. A shortcut for the latter has been added to slime-selector. ** slime-mdot-fu The slime-mdot-fu contrib has been brought back to life. (Thanks to Charles Zhang. Issues #8, #231 and #232.) ** slime-typeout-frame The slime-typeout-frame contrib has been restored. (Issue #221.) ** SBCL backend *** Fixed xrefs coming from C-c C-c Issue #227. ** CMUCL, SBCL and SCL backends *** Better support for custom readtables Functionality that depends on SWANK's source-path-parser, such as `slime-find-definition', now works properly in face of custom readtables by honoring SWANK:*READTABLE-ALIST*. (Thanks to Gábor Melis. PR #244.) ** Kawa backend *** Updated for Kawa version 2.0 Cheers, -- Luís Oliveira http://kerno.org/~luis/

1 0

[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

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