all messages for Guix-related lists mirrored at yhetil.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: zimoun <zimon.toutoune@gmail.com>,
	"Thompson, David" <dthompson2@worcester.edu>,
	guix-devel <guix-devel@gnu.org>
Subject: Re: Emacs integration for 'guix shell'
Date: Tue, 27 Sep 2022 08:06:32 -0400	[thread overview]
Message-ID: <878rm5m37b.fsf@laura> (raw)
In-Reply-To: <86wn9puqj7.fsf@gmail.com>

On Tue, 27 Sep 2022, zimoun <zimon.toutoune@gmail.com> wrote:
>
> --8<---------------cut here---------------start------------->8---
> #!/bin/sh
>
> guix time-machine -C channels.scm  \
>      -- shell --pure               \
>      -m manifest.scm               \
>      -- $@
> --8<---------------cut here---------------end--------------->8---

How about:
--8<---------------cut here---------------start------------->8---
#!/bin/sh
 guix time-machine -C channels.scm    \
     -- shell --pure                  \
     --development $(basename $(pwd)) \
      -- $@
--8<---------------cut here---------------end--------------->8---

Of course you need to A) have a channels.scm in your project and B) have
your project directory named after the package's name in your channel. 

> where manifest.scm and channels.scm are kept with the Git project.  I
> prefer to pin a specific Guix revision to avoid bad surprises. :-) Well,
> in a project, I just run:
>
>     guixify make   # run make using the Guix environment
>     guixify        # enter in the environment
>
>
> I thought to write an extension but I am not convinced by the interface
> I want. :-)

I was using channel too before!  It felt good to pin dependencies to a
version so it does not break while you're developing.  Howeverff, I felt
that the time-machine was taking enormous time everytime a push was made
to a channel.

My biggest usage of the channel was to have the definition of my package
before it was merged into Guix channel.  But this could also be used for
a development version that differs.

-- 
Olivier Dion
oldiob.dev


  reply	other threads:[~2022-09-27 13:59 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. [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=878rm5m37b.fsf@laura \
    --to=guix-devel@gnu.org \
    --cc=dthompson2@worcester.edu \
    --cc=olivier.dion@polymtl.ca \
    --cc=zimon.toutoune@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.
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.