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

Unwanted completion function
by Andrew Brace 21 May '23

21 May '23

I would like to use the default value for the customization setting Slime Completion At Point Functions, (slime-filename-completion slime-simple-completion-at-point). But something has added slime-c-p-c-completion-at-point to the list of functions from outside Customize. I have not altered slime-completion-at-point-functions in my .emacs or anywhere else. If I use Customize to erase the customization, then I get the desired value for the current session. But there is no option to save the setting and my .emacs is unaltered; in my next Emacs session, slime-c-p-c-completion-at-point is back in the setting. How can I prevent slime-c-p-c-completion-at-point from being added?

2 1

445
by Kyösti Salojensaari 09 May '23

09 May '23

1 0

Debugging an existing error
by Gary Palter 02 May '23

02 May '23

I have an application with Swank loaded running standalone. If the application gets an error and enters the Lisp’s native debugger, I want to be able to attach Slime to that Lisp and see the existing error in SLDB. The application does a CREATE-SERVER on startup and I can use m-X slime-connect to connect to it. But, I only get a Slime REPL and don’t see how to point SLDB at the Lisp thread that’s already in the debugger. If the above makes sense, can you suggest how to do what I want? (The concept is that, if a customer ends up in the debugger, we can help him debug using Slime.) Thanks, - Gary

2 2

Loading slime 2.27 going into debugger as of last night.
by Jeff Cunningham 29 Mar '22

29 Mar '22

I asked this question over on sbcl-help already. Stas objected. So I'll ask it again here. Last night I started running into the debugger when trying to start slime in emacs. This morning I decided to delete all my .slime/ fasls, all of .cache/common-lisp/ all of ~/quicklisp and start with a fresh copy of quicklisp.lisp. I updated my arch system (slightly newer version of emacs) then tried to reinstall quicklisp. The problem occurs upstream of emacs ever being started. I can reproduce the problem with these steps: $ rm -rf .slime .cache/common-lisp/* quicklisp $ curl -O https://beta.quicklisp.org/quicklisp.lisp $ sbcl --load quicklisp.lisp * (quicklisp-quickstart:install) * (ql:quickload "quicklisp-slime-helper") To load "quicklisp-slime-helper": Load 1 ASDF system: asdf Install 3 Quicklisp releases: alexandria quicklisp-slime-helper slime ; Fetching #<URL "http://beta.quicklisp.org/archive/slime/2022-02-20/slime-v2.27.tgz"> ; 803.72KB ================================================== 823,006 bytes in 0.09 seconds (9273.62KB/sec) ; Fetching #<URL "http://beta.quicklisp.org/archive/alexandria/2022-02-20/alexandria-20220220…"> ; 55.16KB ================================================== 56,486 bytes in 0.01 seconds (5516.21KB/sec) ; Fetching #<URL "http://beta.quicklisp.org/archive/quicklisp-slime-helper/2015-07-09/quickli…"> ; 2.16KB ================================================== 2,211 bytes in 0.00 seconds (0.00KB/sec) ; Loading "quicklisp-slime-helper" [package swank-loader]............................ [package swank/backend]........................... [package swank/rpc]............................... [package swank/match]............................. [package swank-mop]............................... [package swank]................................... [package swank/source-path-parser]................ [package swank/source-file-cache]................. [package swank/sbcl].............................. [package swank/gray].............................. ........ ; compiling file "/home/jcunningham/quicklisp/dists/quicklisp/software/slime-v2.27/contrib/swank-util.lisp" (written 24 MAR 2022 12:08:30 PM): . ; wrote /home/jcunningham/.slime/fasl/2.27/sbcl-2.2.2-linux-x86-64/contrib/swank-util.fasl ; compilation finished in 0:00:00.010 ; compiling file "/home/jcunningham/quicklisp/dists/quicklisp/software/slime-v2.27/contrib/swank-repl.lisp" (written 24 MAR 2022 12:08:30 PM): ......................................... [package swank-repl].. ; wrote /home/jcunningham/.slime/fasl/2.27/sbcl-2.2.2-linux-x86-64/contrib/swank-repl.fasl ; compilation finished in 0:00:00.040 ; compiling file "/home/jcunningham/quicklisp/dists/quicklisp/software/slime-v2.27/contrib/swank-c-p-c.lisp" (written 24 MAR 2022 12:08:30 PM): . ; wrote /home/jcunningham/.slime/fasl/2.27/sbcl-2.2.2-linux-x86-64/contrib/swank-c-p-c.fasl ; compilation finished in 0:00:00.030 ; compiling file "/home/jcunningham/quicklisp/dists/quicklisp/software/slime-v2.27/contrib/swank-arglists.lisp" (written 24 MAR 2022 12:08:30 PM): ................ ; wrote /home/jcunningham/.slime/fasl/2.27/sbcl-2.2.2-linux-x86-64/contrib/swank-arglists.fasl ; compilation finished in 0:00:00.360 ; compiling file "/home/jcunningham/quicklisp/dists/quicklisp/software/slime-v2.27/contrib/swank-fuzzy.lisp" (written 24 MAR 2022 12:08:30 PM): ... ; wrote /home/jcunningham/.slime/fasl/2.27/sbcl-2.2.2-linux-x86-64/contrib/swank-fuzzy.fasl ; compilation finished in 0:00:00.080 ; compiling file "/home/jcunningham/quicklisp/dists/quicklisp/software/slime-v2.27/contrib/swank-fancy-inspector.lisp" (written 24 MAR 2022 12:08:30 PM): ........ . ; wrote /home/jcunningham/.slime/fasl/2.27/sbcl-2.2.2-linux-x86-64/contrib/swank-fancy-inspector.fasl ; compilation finished in 0:00:00.163 ; compiling file "/home/jcunningham/quicklisp/dists/quicklisp/software/slime-v2.27/contrib/swank-presentations.lisp" (written 24 MAR 2022 12:08:30 PM): ;; ;; Error compiling /home/jcunningham/quicklisp/dists/quicklisp/software/slime-v2.27/contrib/swank-presentations.lisp: ;; SWANK-REPL also exports the following symbols: ;; (SWANK-REPL:CREATE-REPL SWANK-REPL:LISTENER-GET-VALUE ;; SWANK-REPL:CLEAR-REPL-VARIABLES SWANK-REPL:LISTENER-SAVE-VALUE ;; SWANK-REPL:LISTENER-EVAL SWANK-REPL:REDIRECT-TRACE-OUTPUT) ;; See also: ;; The ANSI Standard, Macro DEFPACKAGE ;; debugger invoked on a SB-INT:PACKAGE-AT-VARIANCE-ERROR in thread #<THREAD "main thread" RUNNING {10019B0073}>: SWANK-REPL also exports the following symbols: (SWANK-REPL:CREATE-REPL SWANK-REPL:LISTENER-GET-VALUE SWANK-REPL:CLEAR-REPL-VARIABLES SWANK-REPL:LISTENER-SAVE-VALUE SWANK-REPL:LISTENER-EVAL SWANK-REPL:REDIRECT-TRACE-OUTPUT) See also: The ANSI Standard, Macro DEFPACKAGE Type HELP for debugger help, or (SB-EXT:EXIT) to exit from SBCL. restarts (invokable by number or by possibly-abbreviated name): 0: [DROP-THEM ] Unexport them. 1: [KEEP-THEM ] Keep exporting them. 2: [TRY-RECOMPILING ] Recompile swank-loader and try loading it again 3: [RETRY ] Retry loading FASL for #<SWANK-LOADER-FILE "swank" "swank-loader">. 4: [ACCEPT ] Continue, treating loading FASL for #<SWANK-LOADER-FILE "swank" "swank-loader"> as having been successful. 5: Retry ASDF operation. 6: [CLEAR-CONFIGURATION-AND-RETRY] Retry ASDF operation after resetting the configuration. 7: Retry ASDF operation. 8: Retry ASDF operation after resetting the configuration. 9: [ABORT ] Give up on "quicklisp-slime-helper" 10: [REGISTER-LOCAL-PROJECTS ] Register local projects and try again. 11: Exit debugger, returning to top level. (SB-IMPL::NOTE-PACKAGE-VARIANCE :FORMAT-CONTROL "~A also exports the following symbols:~% ~S" :FORMAT-ARGUMENTS ("SWANK-REPL" (SWANK-REPL:CREATE-REPL SWANK-REPL:LISTENER-GET-VALUE SWANK-REPL:CLEAR-REPL-VARIABLES SWANK-REPL:LISTENER-SAVE-VALUE SWANK-REPL:LISTENER-EVAL SWANK-REPL:REDIRECT-TRACE-OUTPUT)) :PACKAGE #<PACKAGE "SWANK-REPL">) 0] Neither locate nor find show any signs of any other copy of swank or slime on this system. The only thing in my .sbclrc is this: ;;; The following lines added by ql:add-to-init-file: ;;#-quicklisp (let ((quicklisp-init (merge-pathnames "quicklisp/setup.lisp" (user-homedir-pathname)))) (when (probe-file quicklisp-init) (load quicklisp-init))) ;;; Added this to test reading bad char streams (setf sb-impl::*default-external-format* :utf-8) ;;; Added this so I can change the names of package symbols and get ;;; prompted about whether or not I want to drop them: (setf sb-ext:*on-package-variance* '(:error t)) I'm running out of ideas. Does anyone have any? Thanks. --Jeff

3 3

Re: Removal of define-obsolete-variable-alias without when
by Po Lu 02 Oct '21

02 Oct '21

Calling `define-obsolete-variable-alias' without a when argument was obsoleted in Emacs 27, and has been deleted from Emacs 28. SLIME, or at least the version in NonGNU ELPA, still does this in hyperspec.el, causing a failure to build in Emacs 28. According to Stefan Monnier: > The fix is a small matter of adding the WHEN argument (if they really > can't figure out what this WHEN should be (like a release version or a > year), they can just put a nil in there (or remove the thing > altogether since it's probably a sign that it happened long enough ago > that it's of no importance any more)). Thanks.

1 0

Slime installation instructions via elpa package-install no longer working!
by Hrvoje Blazevic 14 Sep '21

14 Sep '21

I'm repeating this because it was rejected. Hi, I don't know if anybody is aware of this situation. I have been using slime for working with CL for years (on and off - I mean Lisp). Last time i set up SBCL and Slime on Fedora in March this year (I think) That time M-x package-install was still working. But a few days ago I tried to set up SBCL and Slime on raspberry pi 4B (just for fun) and this does not work any more! Somebody (or something) has overwritten slime package, and replaced it with slime-voleyball package, apparently some BS game. How to fix this???

2 1

Is this expected behaviour?
by Robert Krug 12 Jul '21

12 Jul '21

Greetings! I realize that this is not a sensible thing to do, but is this expected behaviour? Thanks for the nifty system, Robert ========== In Slime: ; SLIME 2.26.1 CL-USER> (defmethod print-object ((obj string) s) (format s "\"foo\"")) foofoo CL-USER> 'foo foofoo CL-USER> 22 foofoo CL-USER> ========== In the shell: alecto$ sbcl This is SBCL 2.0.1.openbsd, an implementation of ANSI Common Lisp. More information about SBCL is available at <http://www.sbcl.org/>. SBCL is free software, provided as is, with absolutely no warranty. It is mostly in the public domain; some portions are provided under BSD-style licenses. See the CREDITS and COPYING files in the distribution for more information. * (defmethod print-object ((obj string) s) (format s "\"foo\"")) #<STANDARD-METHOD COMMON-LISP:PRINT-OBJECT (STRING T) {10020C01C3}> * "xxx" "foo" * 'foo FOO * 22 22 ========== I am using: (progn (load "/home/<name>/quicklisp/dists/quicklisp/software/slime-v2.26.1/swank-loader.lisp" :verbose t) (funcall (read-from-string "swank-loader:init") :from-emacs t) (funcall (read-from-string "swank:start-server") "/tmp/slime.81676")) This is SBCL 2.0.1.openbsd, an implementation of ANSI Common Lisp. More information about SBCL is available at <http://www.sbcl.org/>. SBCL is free software, provided as is, with absolutely no warranty. It is mostly in the public domain; some portions are provided under BSD-style licenses. See the CREDITS and COPYING files in the distribution for more information. * ; loading #P"/home/<name>/quicklisp/dists/quicklisp/software/slime-v2.26.1/swank-loader.lisp" WARNING: redefining EMACS-INSPECT (#<SB-PCL:SYSTEM-CLASS COMMON-LISP:T>) in DEFMETHOD ;; Swank started at port: 6421. 6421 * WARNING: redefining SWANK::SYMBOL-INDENTATION in DEFUN WARNING: redefining SWANK::MACRO-INDENTATION in DEFUN WARNING: redefining THREAD-FOR-EVALUATION (#<STRUCTURE-CLASS SWANK::MULTITHREADED-CONNECTION> #<SB-MOP:EQL-SPECIALIZER :FIND-EXISTING>) in DEFMETHOD

2 1

Fwd: How do I get the docstring for a symbol from emacs?
by Rudi C 24 May '21

24 May '21

I have tried: ``` (sly-eval `(cl:documentation 'mapcar 'function) :cl) ``` But it doesn't work. My use case is to add docstrings to my ivy completor, like this (so I also need a way to do this for strings, not actual symbols): [image: image.png] PS: Does sly has its own mailing list(s)?

1 0

CLIME, or, a (Mc)CLIM backend based on SLIME
by Luke Gorrie 29 Apr '21

29 Apr '21

Howdy! [Resending this mail that was blocked for having a large screenshot as attachment] I've started hacking on a SLIME frontend ("backend") for McCLIM. It's super early days but there's a WITH-OUTPUT-TO-EMACS macro that lets you use CLIM drawing commands and have the final result rendered as an inline image in the SLIME REPL. There's lots to add e.g. a way to choose a CLIM command to execute and a way to click on presentations to select them as arguments. Add add support for missing shapes including text. If anyone wants to hack on this with me that would be most welcome! The problem this solves is being able to write and debug CLIM code from the comfort of Emacs. It should also be suitable for writing user interfaces that don't need really fast response times (I'm planning to use it for a CAD drawing application in the style of KiCad.) The backend is based on SVG under the hood so in principle it could be made browser-friendly too. Anyway! Initial demo screenshot: https://imgur.com/a/4MdaXTb McCLIM code @ https://github.com/nuddyco/mcclim branch clime SLIME code @ https://github.com/nuddyco/slime branch clime The McCLIM code currently fails to build just because it doesn't find my ASD file. I've no idea what's wrong but it's probably something "obvious." The workaround is to #+nil the #:mcclim-emacs dependency in mcclim.asd and then load Backend/Emacs/emacs.lisp manually. Cheers! -Luke

2 1

CLIME, or, a (Mc)CLIM backend based on SLIME
by Luke Gorrie 29 Apr '21

29 Apr '21

Howdy! I've started hacking on a SLIME frontend ("backend") for McCLIM. It's super early days but there's a WITH-OUTPUT-TO-EMACS macro that lets you use CLIM drawing commands and have the final result rendered as an inline image in the SLIME REPL. There's lots to add e.g. a way to choose a CLIM command to execute and a way to click on presentations to select them as arguments. If anyone wants to help that would be most welcome! The problem this solves is being able to write and debug CLIM code from the comfort of Emacs. It should also be suitable for writing user interfaces that don't need really fast response times (I'm planning to use it for a CAD drawing application in the style of KiCad.) The backend is based on SVG under the hood so in principle it could be made browser-friendly too. Anyway! Initial demo screenshot attached & linked: https://imgur.com/a/4MdaXTb McCLIM code @ https://github.com/nuddyco/mcclim branch clime SLIME code @ https://github.com/nuddyco/slime branch clime The McCLIM code currently fails to build just because it doesn't find my ASD file. I've no idea what's wrong but it's probably something "obvious." Cheers! -Luke

1 0