unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Olivier Dion via "Development of GNU Guix and the GNU System distribution." <guix-devel@gnu.org>
To: "Thompson, David" <dthompson2@worcester.edu>,
	guix-devel <guix-devel@gnu.org>
Subject: Re: Emacs integration for 'guix shell'
Date: Mon, 26 Sep 2022 14:30:28 -0400	[thread overview]
Message-ID: <87czbiugxn.fsf@laura> (raw)
In-Reply-To: <CAJ=RwfbsGuwY3-zxnkPUDOZ4vR9gWjgt3eb0RD9=+TA2tGNgRQ@mail.gmail.com>

On Mon, 26 Sep 2022, "Thompson, David" <dthompson2@worcester.edu> wrote:
> Hello all,
>
> I recently wrote a little blog post titled "Guix for development" [0]
> and in it I mentioned using a tool called direnv and emacs-direnv as a
> way to integrate 'guix shell' with Emacs. This integration has vastly
> improved my Emacs experience. I can open a shell buffer and the
> environment variables are automatically configured the way I want. I
> can run M-x compile and simply enter 'make' as the command instead of
> 'guix shell -D -f guix.scm -- make'.
>
> 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.

Interesting I'll have a look at it!

> I'm not an experienced elisp programmer so I'm sure there's stuff to
> fix, and there are no customizable variables yet, but the essentials
> seem to work OK for me.  If you'd like to try it out, eval
> guix-shell.el and then M-x guix-shell-global-mode to enable it
> everywhere, or M-x guix-shell-mode to enable it just for the current
> buffer.

I have the following in my .dir-locals.el for my library libpatch.  The
idea is the same, but without direnv:
--8<---------------cut here---------------start------------->8---
((nil
  . ((eval .
      (let ((root (locate-dominating-file
                   default-directory ".dir-locals.el")))
        (when root
          (let ((real-root (directory-file-name (expand-file-name root))))
            (setq-local geiser-guile-binary (concat real-root "/.geiser-guile"))
            (setq-local projectile-project-compilation-cmd
                        (concat real-root "/.projectile-compile"))
            (setq-local projectile-project-test-cmd
                        (concat real-root "/.projectile-test")))))))))
--8<---------------cut here---------------end--------------->8---

.projectile-compile:
--8<---------------cut here---------------start------------->8---
#!/bin/sh
./dev-env make -j $(nproc)
--8<---------------cut here---------------end--------------->8---

.projectile-test:
--8<---------------cut here---------------start------------->8---
#!/bin/sh
./dev-env make -j $(nproc) check-nocolor
--8<---------------cut here---------------end--------------->8---

.geiser-guile:
--8<---------------cut here---------------start------------->8---
#!/bin/sh
here=$(pwd)
./dev-env guile -L "$here" -x "$here" $@
--8<---------------cut here---------------end--------------->8---

dev-env:
--8<---------------cut here---------------start------------->8---
#!/bin/sh
guix shell                        \
     --pure                       \
     dyninst                      \
     gdb                          \
     git                          \
     guix                         \
     lcov                         \
     guile-quickcheck             \
     perf                         \
     lttng-ust                    \
     lttng-tools                  \
     --development libpatch       \
     -- $@
--8<---------------cut here---------------end--------------->8---

Note the latest script where I have development packages for libpatch,
but also other utitilies that are good to have for developer.

Regards,
old

-- 
Olivier Dion
oldiob.dev


  reply	other threads:[~2022-09-26 19:13 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. [this message]
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
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=87czbiugxn.fsf@laura \
    --to=guix-devel@gnu.org \
    --cc=dthompson2@worcester.edu \
    --cc=olivier.dion@polymtl.ca \
    /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).