unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Kyle Meyer <kyle@kyleam.com>
To: Marius Bakke <mbakke@fastmail.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 21:40:30 -0400	[thread overview]
Message-ID: <877eywkmb5.fsf@kyleam.com> (raw)
In-Reply-To: <87shhkcibd.fsf@fastmail.com>

Marius Bakke <mbakke@fastmail.com> writes:

> 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.

I think the behavior here is unspecified because --pure is about
unsetting shell variables while this is about how the load-path and
autoloads are set up within an environment's Emacs instance.
Conceptually, though, I agree that a --pure flag would match
guix-emacs-autoload-packages considering only the environment's Emacs
packages, whereas no --pure flag would match adding the environment's to
the current profile's.

But in the discussion so far, I've been assuming that currently there's
not a direct way for guix-emacs-autoload-packages to detect if --pure
was given.  If that's not true, I'd be happy with the behavior you
propose.

-- 
Kyle

  reply	other threads:[~2017-07-26  1:40 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
2017-07-26  1:40           ` Kyle Meyer [this message]
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=877eywkmb5.fsf@kyleam.com \
    --to=kyle@kyleam.com \
    --cc=alezost@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=mbakke@fastmail.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).