From: Trev <trev@trevdev.ca>
To: Guillaume Le Vaillant <glv@posteo.net>
Cc: help-guix@gnu.org
Subject: Re: sbcl-slime-swank won't load
Date: Sat, 20 Aug 2022 15:58:34 -0700 [thread overview]
Message-ID: <878rnir085.fsf@codinator.mail-host-address-is-not-set> (raw)
In-Reply-To: <8735drfexw.fsf@kitej>
[-- Attachment #1: Type: text/plain, Size: 1077 bytes --]
Guillaume Le Vaillant <glv@posteo.net> writes:
> Trev <trev@trevdev.ca> skribis:
>
>>
>> Would the path of least resistance be to install sbcl explicitly in my home profile?
>>
>
> Try installing sbcl to your home profile to see if it fixes the problem,
> then if you don't want to keep it in your home profile, remove it and
> set the environment variables using guix-home instead.
By putting sbcl into my guix-home profile along with the sbcl-stumpwm-*
modules, I am now getting these 3rd party modules without a gexp
work-around. Thanks for that!
However, I still can't get sbcl-slime-swank working in stumpwm. I tried
having sbcl-slime-swank in my guix-home profile. Then I tried putting it
in my system profile where stumpwm is currently declared. Neither of
these cases work with stumpwm's init or eval methods.
I can, however, fire up sbcl from the terminal, require asdf and then
(asdf:load-system :swank) without any issues. I was sure to reboot my
machine before trying.
--
Trev : 0FB7 D06B 4A2A F07E AD5B 1169 183B 6306 8AA1 D206
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 251 bytes --]
next prev parent reply other threads:[~2022-08-20 23:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-18 22:18 sbcl-slime-swank won't load Trev
2022-08-19 8:42 ` Guillaume Le Vaillant
2022-08-19 14:21 ` Trev
2022-08-19 14:49 ` Guillaume Le Vaillant
2022-08-19 15:40 ` Trev
2022-08-20 9:16 ` Guillaume Le Vaillant
2022-08-20 22:58 ` Trev [this message]
2022-08-22 11:03 ` Guillaume Le Vaillant
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=878rnir085.fsf@codinator.mail-host-address-is-not-set \
--to=trev@trevdev.ca \
--cc=glv@posteo.net \
--cc=help-guix@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).