From: Paul Jewell via <help-guix@gnu.org>
To: Trev <trev@trevdev.ca>, "help-guix@gnu.org" <help-guix@gnu.org>
Subject: Re: Stumpwm & using Lisp in guix - particularly quicklisp
Date: Sun, 25 Dec 2022 08:05:39 +0000 [thread overview]
Message-ID: <9a70fb32-06ff-d230-5082-31decf8bcb1e@teulu.org> (raw)
In-Reply-To: <87ili0ylod.fsf@guix.mail-host-address-is-not-set>
Hi Trev,
Thanks for the reply!
On 25/12/2022 07:41, Trev wrote:
> Paul Jewell via <help-guix@gnu.org> writes:
>
>> Good morning Guix,
>>
>> I have a working stumpwm config which I use on my desktop gentoo
>> installation, and I want to use the same configuration file under guix.
>> Unfortunately I run into a problem as when stumpwm starts, it complains
>> it can't find package "ql". Quicklisp is installed in my user home
>> directory, but this is clearly not being seen by stumpwm. I also note
>> that packages I can install through quicklisp are also packaged in guix
>> (e.g. alexandria). When I start sbcl in a terminal, everything works as
>> expected, and quicklisp is seen.
>>
>> This leads me to some questions:
>>
>> * How do I configure stumpwm on my system so it looks in my home
>> directory, and observes my .sbclrc file when starting?
>> * What is the guix recommended way for working with lisp packages?
>> Should I avoid using quicklisp, and instead use the provided
>> packages in guix? I am unable to find any documentation (either
>> official or blog posts etc) explaining this.
>>
>> Many thanks!
> I have no experience with quicklisp and am new to Common Lisp in
> general, but I do use guix and am getting happier with every hack I make
> on stumpwm and I can tell you what has worked for me:
>
> 1. Use the supported asdf system that Guix uses to package lisp programs
> and extensions.
>
> 2. Install your stumpwm, repl & extensions in the same profile, be that
> profile your system or your home/user space. This helps a sbcl find
I have now gone down this path, and nearly everything is working as
expected. The only problem I am tripping up with is sbcl-slime-swank is
trying to (require 'sb-cltl2) and failing, even though I have added
sbcl-trivial-cltl2 to my system configuration. It seems I am not the
only person who has tripped over this issue, although the previous
message thread [1] didn't link the problem to sbcl-slime-swank. When I
comment out the code in my configuration which adds swank, I am up and
running.
This is what I have included in my system configuration:
"stumpwm"
"sbcl-cl-ppcre"
"sbcl-trivial-cltl2"
"sbcl-alexandria"
"sbcl-clx-xembed"
"sbcl-clx-truetype"
"sbcl-stumpwm-ttf-fonts"
"sbcl-stumpwm-swm-gaps"
"sbcl-stumpwm-stumptray"
"sbcl-slime-swank"
although having looked in the source for the package definition for
stumpwm, some of these are superfluous.
Do you use sbcl-slime-swank in your configuration, and if so, did you
come across this problem with cltl2?
[1] https://www.mail-archive.com/help-guix@gnu.org/msg13498.html
next prev parent reply other threads:[~2022-12-25 8:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-24 9:45 Stumpwm & using Lisp in guix - particularly quicklisp Paul Jewell via
2022-12-24 21:20 ` Trev
2022-12-25 4:29 ` Felix Lechner via
2022-12-25 7:16 ` Paul Jewell via
2022-12-25 7:41 ` Trev
2022-12-25 8:05 ` Paul Jewell via [this message]
2022-12-25 18:39 ` Trev
2022-12-26 14:14 ` Paul Jewell via
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=9a70fb32-06ff-d230-5082-31decf8bcb1e@teulu.org \
--to=help-guix@gnu.org \
--cc=paul@teulu.org \
--cc=trev@trevdev.ca \
/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).