Hello,
Hi Zelphir, Am Dienstag, dem 15.02.2022 um 09:45 +0000 schrieb Zelphir Kaltstahl:Hello Liliana, On 2/14/22 20:33, Liliana Marie Prikler wrote:Hi Zelphir, Am Montag, dem 14.02.2022 um 18:41 +0000 schrieb Zelphir Kaltstahl:[...]I think we need some multi-level printf debugging here. First, after `source "${GUIX_PROFILE}/etc/profile"`, is EMACSLOADPATH correctly pointing to the share/emacs/site-lisp of ${GUIX_EXTRA_PROFILES}/emacs-test-profile? Second, before and after executing your init.el snippet, what are the contents of load-path? Do they contain /gnu/store/SOME_LONG_HASH-magit-MAGIT_VERSION? CheersTo simplify things, I created a shell script, which does the calls: ~~~~ #!/usr/bin/env bash set -Eeuxo pipefail # source the environment GUIX_PROFILE="${GUIX_EXTRA_PROFILES}/emacs-test-profile" . "${GUIX_PROFILE}/etc/profile" printf "emacs load path: %s\n" "${EMACSLOADPATH}" # run emacs env XMODIFIERS='' emacs ~~~~ This outputs the following: ~~~~ [...] ~~~~ Magit line is: ~~~~ "/gnu/store/f0461m96rhnpkmhjlj06yz058pqyj02d-emacs-magit- 3.3.0/share/emacs/site-lisp/magit-3.3.0" ~~~~Okay, this means that subdirs.el is correctly expanded. The next question regards autoloads. Is (featurep 'magit-autoloads) t or nil?
It is t. That is after loading `init.el` and all it contains, but there is no magit configuration happening inside this `init.el` yet.
Best regards,[...]
-- repositories: https://notabug.org/ZelphirKaltstahl