From: Kyle Meyer <kyle@kyleam.com>
To: Alex Kost <alezost@gmail.com>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Should guix-emacs-autoload-packages use GUIX_ENVIRONMENT?
Date: Mon, 24 Jul 2017 18:25:31 -0400 [thread overview]
Message-ID: <87h8y1jwv8.fsf@kyleam.com> (raw)
In-Reply-To: <87379l1qip.fsf@gmail.com>
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 ...
>>> 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 :-)
... I'd say "along with" is better.
As I said in my previous post, it's quite easy for me to get the
behavior I want, so I'd prefer to go with your gut feeling about the
expected behavior.
--
Kyle
next prev parent reply other threads:[~2017-07-24 22:25 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 [this message]
2017-07-25 21:33 ` Marius Bakke
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87h8y1jwv8.fsf@kyleam.com \
--to=kyle@kyleam.com \
--cc=alezost@gmail.com \
--cc=guix-devel@gnu.org \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.