emacs-guix: Requires GUILE_LOAD_(COMPILED_)PATH env vars (or "guile" package)

  • Open
  • quality assurance status badge
Details
One participant
  • Ivan Vilata i Balaguer
Owner
unassigned
Submitted by
Ivan Vilata i Balaguer
Severity
normal
I
I
Ivan Vilata i Balaguer wrote on 23 Aug 2022 12:43
(address . bug-guix@gnu.org)
YwSvTDnXzX76ExzC@sax.terramar.selidor.net
Hi! I have `emacs-guix` in a separate Guix profile with all Emacs stuff,
running on a foreign distro. I noticed that removing the `guile` package
(from all profiles) broke `emacs-guix` after a session restart, and that
restoring the `guile` package or just Guile's environment variables fixed the
issue:

```
$ nog # a script of mine running a distro shell with no Guix variables
$ . ~/env/guix/ivan/emacs/etc/profile # from profile with Emacs stuff
$ . ~/.config/guix/current/etc/profile
$ command -v guile || echo missing
missing
$ emacs

Running M-x guix then v yields this error:

Starting Guix REPL ... [5 times]
guix-geiser-eval: Error in evaluating guile expression: ice-9/boot-9.scm:1685:16: In procedure raise-exception:
Unbound variable: %max-returned-list-size

$ realpath ~/env/guix/ivan/emacs
/gnu/store/ahq…-profile
$ export GUILE_LOAD_PATH=/gnu/store/ahq…-profile/share/guile/site/3.0
$ export GUILE_LOAD_COMPILED_PATH=/gnu/store/ahq…-profile/lib/guile/3.0/site-ccache:/gnu/store/ahq…-profile/share/guile/site/3.0
$ emacs

Running M-x guix works successfully.

$ exit
```

I'm no Guix packaging expert, but it looks like `emacs-guix` should either
have `guile` as propagated input, or somehow add `GUILE_LOAD_PATH` and
`GUILE_LOAD_COMPILED_PATH` to the profile's search paths.

Thank you very much!

--
Ivan Vilata i Balaguer -- https://elvil.net/
-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEHpvwBPZcchIQr6TuPezBBfXdI4IFAmMEr0MACgkQPezBBfXd
I4Lvog/9EpZc9pRp3mCLEN37KZYjV/ALUOsYYMWW/L4rUYvhFy5Y8VbGCtdvPoEE
ZIJ5t9frXovz7r7QQYvggC41Ko0qS9pF10d7ahijLKjtLe9OPicSWsJfqV3/jrnA
eSJGg5SLH3PLTdDzmEaTMGGguBexD9IPz88YcJoEvaQJT4kiWqz9dqSmteYHedpX
ET5Z7iNtFYjE0Jc/GdVXGx875WzHnRjznEEG3v6kAUPNcYsHNfRMoAhpD7PFiTAW
VS6/p/Ph65wjtSZXWMJaLVwVC2FG5ehMXDuRzxQjxJ8xh8UDaIm0O665m2VfDYlQ
Wx3aJ6AkcC8QxqAnOlQeySaKMgGeSO8HSyMB1dFymasdw6R0VHQ+DS7VaaxhTAHo
DwnqP2Dgj56uzmJaUKS13dWmDl8OTCLT/z/DNkOoTH51/2MHBWWVu9LHnvsFfVV9
HLNP0BgJ2Oph9jP6ZEdxapW1XKaiVziddvnji6L2ZZgUFxKQsloXbAM1GIxCt+Qw
siJooS/o68+JjPTlGhxum8lMhzxJPi5z+sTL9wOgdJ796witUJbN03BopNO+SSYs
eTvc9P104zFAbn7J88R6GUMZMBOsi4AEbY8+Bt9qOjR4YPI3IGZkPwIyGHdOLEUq
+NhTfC8F6fVVns755jZx6SL8fia38v/JzdMqZuuhllDMimFN8DY=
=Bevf
-----END PGP SIGNATURE-----


?
Your comment

Commenting via the web interface is currently disabled.

To comment on this conversation send an email to 57352@debbugs.gnu.org

To respond to this issue using the mumi CLI, first switch to it
mumi current 57352
Then, you may apply the latest patchset in this issue (with sign off)
mumi am -- -s
Or, compose a reply to this issue
mumi compose
Or, send patches to this issue
mumi send-email *.patch