From: Marius Bakke <mbakke@fastmail.com>
To: Kyle Meyer <kyle@kyleam.com>, Alex Kost <alezost@gmail.com>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Should guix-emacs-autoload-packages use GUIX_ENVIRONMENT?
Date: Tue, 25 Jul 2017 23:33:58 +0200 [thread overview]
Message-ID: <87shhkcibd.fsf@fastmail.com> (raw)
In-Reply-To: <87h8y1jwv8.fsf@kyleam.com>
[-- Attachment #1: Type: text/plain, Size: 854 bytes --]
Kyle Meyer <kyle@kyleam.com> writes:
> Alex Kost <alezost@gmail.com> writes:
>
> [...]
>
>>> 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".
>
> OK, given that many (all other? :]) users would expect a different
> behavior ...
Wait, isn't this what --pure is for? I haven't followed the discussion,
but I would expect `guix environment` to *add* to my current profile,
and use '--pure' if I want a "clean" environment.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2017-07-25 21:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-23 1:39 Should guix-emacs-autoload-packages use GUIX_ENVIRONMENT? Kyle Meyer
2017-07-23 21:12 ` Alex Kost
2017-07-23 22:29 ` Kyle Meyer
2017-07-24 21:19 ` Alex Kost
2017-07-24 22:25 ` Kyle Meyer
2017-07-25 21:33 ` Marius Bakke [this message]
2017-07-26 1:40 ` Kyle Meyer
2017-07-26 20:02 ` Alex Kost
2017-07-27 11:38 ` Ricardo Wurmus
2017-07-26 20:06 ` Alex Kost
2017-07-27 5:04 ` Kyle Meyer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87shhkcibd.fsf@fastmail.com \
--to=mbakke@fastmail.com \
--cc=alezost@gmail.com \
--cc=guix-devel@gnu.org \
--cc=kyle@kyleam.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).