From: Suhail Singh <suhailsingh247@gmail.com>
To: Richard Sent <richard@freakingpenguin.com>
Cc: ludo@gnu.org, help-guix@gnu.org
Subject: Re: Why are custom channels not available to guix repl?
Date: Sat, 13 Jul 2024 11:55:39 -0400 [thread overview]
Message-ID: <87v819477o.fsf@gmail.com> (raw)
In-Reply-To: <ZpKT3suZ_dZ471Rl@ws> (Tomas Volf's message of "Sat, 13 Jul 2024 16:49:02 +0200")
Tomas Volf <~@wolfsden.cz> writes:
> Thank you very much, I can just stuff it into .guile for now.
For the benefit of others on the mailing list, something like the below
in .guile ensures that the customization runs only for guix repl:
#+begin_src scheme
(when (equal? (module-name (current-module)) '(guix-user))
;; `guix repl`-only init code
;; ensure custom channels are available in guix repl
(use-modules (gnu packages)) ;; <https://issues.guix.gnu.org/61343>
)
#+end_src
--
Suhail
prev parent reply other threads:[~2024-07-13 15:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-12 8:11 Why are custom channels not available to guix repl? Tomas Volf
2024-07-12 14:15 ` Richard Sent
2024-07-13 14:49 ` Tomas Volf
2024-07-13 15:55 ` Suhail Singh [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=87v819477o.fsf@gmail.com \
--to=suhailsingh247@gmail.com \
--cc=help-guix@gnu.org \
--cc=ludo@gnu.org \
--cc=richard@freakingpenguin.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).