15:29 <Kabriel> I'm having a bit of trouble with my slime setup. I am using stock debian 10 emacs 26.1, sbcl 1.4.16, slime 2.23 and using quicklisp to load mcclim (mcclim-20190813-git).

15:29 <Kabriel> I get an error that SWANK/BACKEND also exports the following symbols: with a long list

15:30 <Kabriel> I thought maybe I had some stale fasl files, so I removed the .cache/common-lisp/... directory and recompiled everything, but still get the error.

15:30 <luis> Kabriel: sounds like loading mcclim is causing a second swank to be loaded.

15:30 <Kabriel> The folks at #clim assured me that I have a slime setup issue

15:31 <Kabriel> I thought this too, but I can't find where; any tips on debugging

15:33 <luis> Kabriel: open a fresh SBCL, what does (asdf:system-definition-pathname (asdf:find-system :uiop)) say?

15:34 <luis> Kabriel: open a fresh SBCL, what does (asdf:system-definition-pathname (asdf:find-system :swank)) say?

15:34 <luis> swank, not uiop, sorry.

15:35 <Kabriel> #P"/usr/share/common-lisp/source/slime/swank.asd"

15:36 <luis> Kabriel: are you getting SLIME via a Debian package?

15:42 <Kabriel> yes

15:42 <Kabriel> stock debian 10, slime ver 2.23

15:44 <Kabriel> not sure if it matters, but in a fresh sbcl, I can load mcclim with no issues; it is only when I load it from within emacs

15:45 <luis> Kabriel: try (asdf:load-system :swank) beforehand.

15:47 <luis> does that help?

15:47 <Kabriel> that also worked fine; I did (require 'asdf) (asdf:load-system :swank) (load "~/.local/share/quicklisp/setup.lisp") (ql:quickload 'mcclim)

15:48 <luis> Via SLIME?

15:48 <Kabriel> sorry, this was all in a fresh sbcl. I'll try in slime.

15:52 <Kabriel> ok, via a fresh emacs/slime startup, if I do (asdf:load-system :swank), I get the same error that swank-loader also exports these symbols

15:52 <Kabriel> pathname is /usr/share/common-lisp/source/slime/swank.asd:

15:52 <luis> Kabriel: so, it's surprising that you get an error.

15:53 <luis> Kabriel: what value does sb-ext:*on-package-variance* have?

15:53 <Kabriel> I checked in my .cache directory, and there is only one slime/swank set of fasl files

15:54 <luis> I have a vague memory that ASDF promotes WARNINGs to compilation errors on SBCL. But I'm not seeing that in my setup.

15:55 <Kabriel> (:ERROR T)

15:55 <luis> Ah, there you go.

15:56 <luis> Change that to at least '(:warn (:swank :swank-backend) :error t)

15:59 <Kabriel> So I had to do (setf sb-ext:*on-package-variance* '(:warn (:swank :swank/backend :swank-loader) :error t))

15:59 <Kabriel> and it didn't give an error, but lots of warnings. Is this normal?

16:00 <Kabriel> I mean its the same thing, just telling it to ignore the re-exporting

16:02 <Kabriel> funny, the example in the sbcl manual for on-package-varience is to set swank and swank-backend to warning

16:04 <luis> Kabriel: so, what's happening is that SLIME loads SWANK on its own without ASDF. Loading it via ASDF later causes it to be reloaded and that package issue is expected. Your SBCL setup is causing the warning to be promoted to an error. I wonder why. Did you change that setting? Maybe it's the debian package?

16:05 <luis> Kabriel: not sure if the warning normal, but it is expected. :-)

16:05 <Kabriel> I can't believe it. I thought I had an empty sbclrc file, but it actually sets this variable to error t!

16:06 <Kabriel> the default is to warn, right?

16:15 <Kabriel> luis: thanks much for your help

16:17 <luis> Kabriel: ok, cool. Mystery solved. :-)

16:19 <Kabriel> Is there a way to tell mcclim that swank is actually already loaded?

16:19 <Kabriel> or perhaps tell asdf

16:51 <luis> Kabriel: not that I know of, but there might be some way. It'd help if SLIME loaded SWANK via ASDF. There are some pending merge requests to make it do that.

17:23 <Shinmera> Kabriel: there's asdf:register-preloaded-system

17:34 <luis> Shinmera: ah, thanks. I found mark-component-preloaded but that wasn't it.