On 2022-12-15, Alberto Luaces wrote: > Just confirming this issue also affects debian's emacs. > > /etc/profile.d/guix.sh implicitly sets up EMACSLOADPATH when sourcing > the profile. > > I think that emacs only reads dirs in EMACSLOADPATH if it is set, so > after that any .el files under /usr/ are not found. Even if that were > not the case, I also think that it would be still undesirable for > debian emacs to look first into the guix profile directories, since it > could cause mixed version .el file loads. > > I am a new guix user, so maybe I am not understanding something, but I > tend to believe that currently the rationale is that it is not > expected that the user can have co-existing guix and debian versions > of the same software.
There are certain softwares where this is not possible because of how they are designed, yes... namely anything that uses a PATH-like variable that does not work with multiple sources, or modules that cannot handle multiple underlying libraries at play... Figuring that out on a case-by-case basis is definitely tricky. > So far I have deleted /etc/profile.d/guix.sh and I am proceeding to > activate guix profiles only when I am needing them. This will mean you will need to manually add the guix profile directories to your path if you want to be able to access software installed via guix in your user profile, and to add the guix installed via "guix pull" to your PATH (e.g. to get newer versions of software and/or features available in guix). live well, vagrant
signature.asc
Description: PGP signature
