From: James Thomas <jimjoe@gmx.net>
To: "Thompson, David" <dthompson2@worcester.edu>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Emacs integration for 'guix shell'
Date: Sat, 01 Oct 2022 10:17:47 +0530 [thread overview]
Message-ID: <87fsg8w3nw.fsf@gmx.net> (raw)
In-Reply-To: <CAJ=RwfbsGuwY3-zxnkPUDOZ4vR9gWjgt3eb0RD9=+TA2tGNgRQ@mail.gmail.com> (David Thompson's message of "Mon, 26 Sep 2022 13:48:25 -0400")
Thompson, David wrote:
> It's very cool that it works, and I should have done this years ago,
> but direnv is an unnecessary middleman for me because I don't use it
> for any other purpose. It would be *even cooler* if Emacs could call
> 'guix shell --search-paths' directly, parse the result, and update the
> buffer environment. Furthemore, it could integrate with project.el
> (thus requiring Emacs 28) so that per-project search paths "just
> work." The emacs-guix-shell [1] project attempts to do this.
Great work!
You might also want to check out a package called buffer-env [1] for
this, which is more generally applicable. [2] is a blog post describing
one way to use it in Guix.
[1] https://github.com/astoff/buffer-env/
[2] https://amodernist.com/texts/emacs-guix.html
--
next prev parent reply other threads:[~2022-10-01 10:06 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-26 17:48 Emacs integration for 'guix shell' Thompson, David
2022-09-26 18:30 ` Olivier Dion via Development of GNU Guix and the GNU System distribution.
2022-09-27 2:44 ` Maxim Cournoyer
2022-09-27 11:13 ` Thompson, David
2022-09-28 14:11 ` Maxim Cournoyer
2022-09-27 9:15 ` zimoun
2022-09-27 12:06 ` Olivier Dion via Development of GNU Guix and the GNU System distribution.
2022-09-27 14:39 ` zimoun
2022-09-26 18:58 ` pinoaffe
2022-09-28 7:36 ` Efraim Flashner
2022-09-28 12:42 ` Efraim Flashner
2022-10-01 4:47 ` James Thomas [this message]
2022-10-01 8:22 ` Philip Kaludercic
2022-10-01 11:58 ` Thompson, David
2022-10-01 14:38 ` Philip Kaludercic
2022-12-06 14:59 ` [EXT] " Thompson, David
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=87fsg8w3nw.fsf@gmx.net \
--to=jimjoe@gmx.net \
--cc=dthompson2@worcester.edu \
--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 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).