Emacs packages not visible out of the box

  • Done
  • quality assurance status badge
Details
2 participants
  • Ludovic Courtès
  • Maxim Cournoyer
Owner
unassigned
Submitted by
Ludovic Courtès
Severity
normal
L
L
Ludovic Courtès wrote on 11 Jan 2021 14:37
(address . bug-guix@gnu.org)
874kjnegs9.fsf@gnu.org
Hi!

Consider this Emacs:

guix environment -E DISPLAY --expose=/tmp/.X11-unix \
--ad-hoc -C emacs emacs-geiser emacs-guix guile \
-- emacs -Q

Things like M-x run-guile (from Geiser) or M-x guix are not accessible
by default. I have to explicitly (require 'geiser) etc. to get them.

It seems to me that it used to be the case that Emacs packages were
readily usable in fresh environments, no? Did something change
recently?

That’s with:

Toggle snippet (8 lines)
$ guix describe
Generacio 171 Jan 11 2021 11:38:39 (nuna)
guix 458cb25
repository URL: https://git.savannah.gnu.org/git/guix.git
branch: master
commit: 458cb25b9e7e7c954f468023abea2bebb5d8c75b

Ludo’.
M
M
Maxim Cournoyer wrote on 21 Jan 2021 14:47
(name . Ludovic Courtès)(address . ludo@gnu.org)(address . 45781-done@debbugs.gnu.org)
87mtx2flkp.fsf@gmail.com
tags 45781 notabug
thanks

Hi Ludovic!

Ludovic Courtès <ludo@gnu.org> writes:

Toggle quote (11 lines)
> Hi!
>
> Consider this Emacs:
>
> guix environment -E DISPLAY --expose=/tmp/.X11-unix \
> --ad-hoc -C emacs emacs-geiser emacs-guix guile \
> -- emacs -Q
>
> Things like M-x run-guile (from Geiser) or M-x guix are not accessible
> by default. I have to explicitly (require 'geiser) etc. to get them.

That's expected when using -Q, which does --no-site-file. The site file
is responsible to load the package autoloads files, via
'guix-emacs-autoload-packages'.

Toggle quote (4 lines)
> It seems to me that it used to be the case that Emacs packages were
> readily usable in fresh environments, no? Did something change
> recently?

No, nothing changed!

Closing,

Thank you.

Maxim
Closed
?
Your comment

This issue is archived.

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

To respond to this issue using the mumi CLI, first switch to it
mumi current 45781
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