unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Reza Housseini <reza.housseini@gmail.com>
Cc: help-guix@gnu.org
Subject: Re: Activate multiple profiles inside emacs
Date: Wed, 16 Mar 2022 11:00:56 -0400	[thread overview]
Message-ID: <87fsniaqmv.fsf@gmail.com> (raw)
In-Reply-To: <60d23adb-8515-7942-6520-229dcbff0bf4@gmail.com> (Reza Housseini's message of "Tue, 8 Mar 2022 16:02:32 +0100")

Hi Reza,

Reza Housseini <reza.housseini@gmail.com> writes:

> Hi Guix
>
> Say I have several projects each with their specific profile
> containing the needed dependencies and a profile for all my Emacs
> specific stuff.
>
> Now I want to work on a projects inside Emacs and make therefore a
> union of the project specific profile and my Emacs profile. So as for
> example pylint does not complain about missing modules inside my
> project source code.
>
> As I understand I could source my needed profile files in a shell and
> then start Emacs from there, but this makes it quite cumbersome to 
> switch projects as I have to restart Emacs every time.
>
> Is there a possibility to achieve the same while Emacs keeps running?
>
> How do you guixers handle this scenario? Or is there an obvious
> solution to my needs?

Typically, I keep a manifest.scm per project, then create the
environment with 'guix shell', retrieve the profile link with 'echo
$GUIX_ENVIRONMENT' within that environment, which I then pass to the
'guix-set-emacs-environment' Emacs procedure, which is provided by the
'emacs-guix' package.

Clunky, but it works for me.

Hope that helps,

Maxim


      parent reply	other threads:[~2022-03-16 15:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-08 15:02 Activate multiple profiles inside emacs Reza Housseini
2022-03-08 16:31 ` Justin Veilleux
2022-03-16 15:00 ` Maxim Cournoyer [this message]

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=87fsniaqmv.fsf@gmail.com \
    --to=maxim.cournoyer@gmail.com \
    --cc=help-guix@gnu.org \
    --cc=reza.housseini@gmail.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.
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).