From: Kenny Ballou <kballou@devnulllabs.io>
To: Chris Marusich <cmmarusich@gmail.com>
Cc: help-guix@gnu.org
Subject: Re: Guix and Emacs Integration for Polyglot Development
Date: Sun, 05 Aug 2018 13:16:29 -0600 [thread overview]
Message-ID: <871sbcpqsy.fsf@devnulllabs.io> (raw)
In-Reply-To: <87bmalchr9.fsf@gmail.com>
On 2018年08月02日 08:08 GMT, Chris Marusich wrote:
> Kenny Ballou <kballou@devnulllabs.io> writes:
>
>> I would like to be able to specify a project's dependencies in a
>> manifest file, add any environment variables as necessary, and have
>> Emacs be aware of those variables when entering that environment.
>
> It may not be what you're looking for, but projects like Haunt [1] put a
> guix.scm file in the root directory of their project. The file contains
> a package as its top-level form (I think that's the right terminology),
> and you can get the dependencies via "guix environment -l guix.scm".
When I mentioned the "manifest" file, I wasn't aware it was common to
refer to this file as `guix.scm`, but yes, this is definitely the first
part. However, to clarify, my question is regarding the second part:
how to get the `guix.scm` and any environment variables loaded as part
of `guix environment -l guix.scm` or `guix environment -m
project_manifest.scm`-- search paths and similar -- integrated into the
buffers local to the project directory? I believe `.dir-locals.el` or
similar might actually be the right approach here, but I'm still in the
early stages of exploring this.
I hope that clarifies my question better. For more reference, I'm also
thinking of wingo's blog on developing v8 with guix[1] (though I believe
`guix environment` wasn't yet available).
Again, if this is the wrong list, I can move this question to emacs-help
instead.
-Kenny
[1]: https://wingolog.org/archives/2015/08/04/developing-v8-with-guix
next prev parent reply other threads:[~2018-08-05 19:17 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-27 18:53 Guix and Emacs Integration for Polyglot Development Kenny Ballou
2018-08-02 8:08 ` Chris Marusich
2018-08-05 19:16 ` Kenny Ballou [this message]
2018-08-20 12:32 ` Maxim Cournoyer
2018-08-24 21:55 ` Ludovic Courtès
2018-08-25 19:47 ` Alex Kost
2018-08-25 21:59 ` Ludovic Courtès
2018-08-31 12:49 ` Maxim Cournoyer
2018-09-10 15:25 ` Kenny Ballou
2018-09-11 1:10 ` George Clemmer
-- strict thread matches above, loose matches on Subject: below --
2018-08-29 18:41 Jan Nieuwenhuizen
2018-09-01 14:41 ` Ludovic Courtès
2018-09-01 15:11 ` Jan Nieuwenhuizen
2018-09-01 17:25 ` Ludovic Courtès
2018-09-13 20:45 ` Jan Nieuwenhuizen
2018-09-14 9:56 ` Ludovic Courtès
2018-09-14 11:53 ` Jan Nieuwenhuizen
2018-09-14 21:34 ` Alex Kost
2018-09-15 5:21 ` Jan Nieuwenhuizen
2018-09-15 19:40 ` Alex Kost
2018-10-26 4:59 ` George Clemmer
2018-10-26 17:04 ` Alex Kost
2018-10-26 18:01 ` George Clemmer
2018-10-26 20:56 ` George Clemmer
2018-10-27 14:42 ` Alex Kost
2018-10-27 19:32 ` George Clemmer
2018-10-28 14:39 ` Alex Kost
2018-10-28 21:19 ` George Clemmer
2018-10-29 16:37 ` Alex Kost
2018-10-26 1:22 ` Maxim Cournoyer
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=871sbcpqsy.fsf@devnulllabs.io \
--to=kballou@devnulllabs.io \
--cc=cmmarusich@gmail.com \
--cc=help-guix@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.