From: Simon Tournier <zimon.toutoune@gmail.com>
To: Luis Felipe <luis.felipe.la@protonmail.com>
Cc: "mhrunnels@yahoo.com" <mhrunnels@yahoo.com>,
"help-guix@gnu.org" <help-guix@gnu.org>
Subject: Re: Understanding config.scm Modules
Date: Wed, 8 Feb 2023 18:03:25 +0100 [thread overview]
Message-ID: <CAJ3okZ0tM26THX3++=xnJbb3SNh50J3rAKfoKhdxG2WyUekGtA@mail.gmail.com> (raw)
In-Reply-To: <Ge1jdBirEbQ1aQDedtLOwagvvfQ1WThDoXZumu3itYAIiL5_x5-Ay3Ks-UXS7o19Wt_1OuuQQC41IdRWgEQHyalwwOS_llHviPtF7HDdKqw=@protonmail.com>
Hi,
On Wed, 8 Feb 2023 at 16:49, Luis Felipe <luis.felipe.la@protonmail.com> wrote:
>
> On Wednesday, February 8th, 2023 at 14:07, Simon Tournier <zimon.toutoune@gmail.com> wrote:
>
> > On jeu., 02 févr. 2023 at 19:02, "mhrunnels@yahoo.com" mhrunnels@yahoo.com wrote:
> >
>
> > > 4) Where does the manual list the modules and module options for quick
> > > reference?
> >
>
> > I do not understand this question but I guess it is because the question
> > #2.
>
> I guess mhrunnels refers to an index of modules, something that is commonly found in API documents. As far as I know, Guix doesn't provide such an index or separate API reference documentation. The Guix manual mentions modules and what they provide in the context of sections.
Ah I see. Well, using use-package-modules or use-service-modules, why
would you need to know that index of modules?
However, yeah, I agree that some modules from 'gnu' or 'guix' could be
also required. Indeed, this video...
> https://10years.guix.gnu.org/program/#guixy-guile-the-derivation-factory-a-tour-of-the-guix-source-tree.
...is a really good start. Maybe, it could be a starting point for
improving the manual.
In addition, I would mention: https://toys.whereis.みんな/
Cheers,
simon
next prev parent reply other threads:[~2023-02-08 17:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <484018477.1836111.1675364529911.ref@mail.yahoo.com>
2023-02-02 19:02 ` Understanding config.scm Modules mhrunnels
2023-02-08 14:07 ` Simon Tournier
2023-02-08 15:49 ` Luis Felipe
2023-02-08 17:03 ` Simon Tournier [this message]
2023-02-08 19:00 ` Andreas Enge
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='CAJ3okZ0tM26THX3++=xnJbb3SNh50J3rAKfoKhdxG2WyUekGtA@mail.gmail.com' \
--to=zimon.toutoune@gmail.com \
--cc=help-guix@gnu.org \
--cc=luis.felipe.la@protonmail.com \
--cc=mhrunnels@yahoo.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).