Kyle Meyer (2017-07-23 18:29 -0400) wrote:

> Alex Kost <alez...@gmail.com> writes:
>
>> Kyle Meyer (2017-07-22 21:39 -0400) wrote:
>>
>>> I noticed that Emacs packages from the user's profile leak into guix
>>> environment calls.
>>
>> As for me, this is a natural behaviour.  If you want to be safe from any
>> external packages, site settings, etc., run "emacs -Q".
>
> I want "-q" rather than "-Q" because I want the Emacs instance to
> autoload the Emacs packages that I've given as arguments to "guix
> environment".

Oh, right, now I see why "-Q" is not what you want.

>> I'm not sure.  I think if you run "emacs -q", you really want "emacs -Q".
>> Otherwise, if you start emacs normally, you probably don't want to ignore
>> emacs packages from your guix profile.
>
> Maybe I'm underestimating all the ways people use "guix environment".
> When I use it, I'm interested in getting an isolated environment,
> usually for testing, and in this case I don't want the Emacs packages
> from my profile.

OK, now I understand your point and I don't object against your patch.
OTOH I'm pretty sure there are people who will be surprised that when
emacs is started under "guix environment", it ignores packages from the
"~/guix-profile".

>> However, I agree that GUIX_ENVIRONMENT should be honored, but as I wrote
>> *not instead* but *along with* the default profiles.  So if you start
>> emacs like this:
>>
>>   guix environment --ad-hoc emacs emacs-wget -- emacs
>>
>> it should contain emacs-wget in its load-path.  WDYT?
>
> I certainly agree with that load-path should include emacs-wget.  I'm
> just not sure I agree with the "along with".

Now I'm also not sure if "along with" or "instead" is better.  I don't
have a preference, so I agree with any choice :-)

-- 
Alex

Reply via email to