unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: pinoaffe <pinoaffe@gmail.com>
To: Jan Nieuwenhuizen <janneke@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: Some emacs stuff to activate/deactivate guix profiles
Date: Thu, 17 Dec 2020 15:28:30 +0100	[thread overview]
Message-ID: <8736048q29.fsf@gmail.com> (raw)
In-Reply-To: <87o8is6aly.fsf@gnu.org>


Jan Nieuwenhuizen writes:
> My emacs-guix already has a file called guix-profiles.el; how do you
> handle that
oops, I think I'll rename this script then :)
    
> or how do I best look at / try your profiles?
I think the easiest way to try this is to source the guix-profiles file,
set the three "defcustom" variables, and to then run guix-enable-profile
or guix-disable-profile interactively.

> This looks interesting; I'm using M-x guix-set-emacs-environment a
> lot but my biggest problem/gripe with that is that it's global.
Yeah this is also global, as far as I can tell the only difference with
guix-set-emacs-environment seems to be that this allows enabling several
profiles at the same time and that this script maintains a list of which
profiles should be active. I think I'll take a look at how this could be
integrated into emacs-guix.
    
As to non-global things: I think a way to open a shell in emacs with a
specific set of packages available would be nice, but I'm not sure
whether it'd be better to wrap `guix environment` or to implement
something that starts a subprocess with the environment variables
corresponding to a (set of) profile(s). When implemented correctly, this
could also be applied through per-project profiles when combined with a
project manager such as projectile.
    
Blessings,
pinoaffe


  reply	other threads:[~2020-12-17 14:28 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-17  8:29 Some emacs stuff to activate/deactivate guix profiles pinoaffe
2020-12-17  9:32 ` Jan Nieuwenhuizen
2020-12-17 14:28   ` pinoaffe [this message]
  -- strict thread matches above, loose matches on Subject: below --
2020-12-17  4:59 pinoaffe
2020-12-17  8:26 ` zimoun
2020-12-17  8:36   ` pinoaffe
2020-12-17  8:52     ` zimoun
2020-12-17  8:31 ` pinoaffe
2020-12-17  4:57 pinoaffe
2020-12-16 19:43 pinoaffe
2020-12-16 19:43 pinoaffe

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=8736048q29.fsf@gmail.com \
    --to=pinoaffe@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=janneke@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 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).