From: zimoun <zimon.toutoune@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>, Phil <phil@beadling.co.uk>
Cc: guix-devel@gnu.org
Subject: Re: Compile skribilo doc containing guix channel references
Date: Sun, 06 Nov 2022 19:50:56 +0100 [thread overview]
Message-ID: <86wn87lxwv.fsf@gmail.com> (raw)
In-Reply-To: <878rkpjn3e.fsf@gnu.org>
Hi,
On Sat, 05 Nov 2022 at 19:03, Ludovic Courtès <ludo@gnu.org> wrote:
>> This generates the docs with guix imports - see compile-command in the header:
>> https://github.com/quantiletechnologies/qt-guix/blob/feature/EA-133/compile-docs.scm
>>
>> This is the document - it's less ambitious than my internal version in
>> terms of generating content from guix - but has a few examples of
>> generating content from channels:
>> https://github.com/quantiletechnologies/qt-guix/blob/feature/EA-133/qtdocs/qt-guix.skb
I am missing how the Skribilo file is it compiled? At “guix pull” time?
Or manually when running the script compile-docs.scm?
> Nice! Including channel info in the document like you do here is
> probably a major use case; it also makes a lot of sense in the context
> of reproducible research workflows.
Ludo, what do you have in mind about reproducible research workflow?
Cheers,
simon
next prev parent reply other threads:[~2022-11-06 19:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-30 20:46 Compile skribilo doc containing guix channel references Phil
2022-10-31 21:56 ` Phil
2022-11-02 11:36 ` Ludovic Courtès
2022-11-04 22:13 ` Phil
2022-11-05 16:40 ` Phil
2022-11-05 18:03 ` Ludovic Courtès
2022-11-06 18:50 ` zimoun [this message]
2022-11-06 22:12 ` Phil
2022-11-07 8:37 ` zimoun
2022-11-07 9:21 ` Ludovic Courtès
2022-11-07 9:47 ` zimoun
2022-11-10 11:58 ` Ludovic Courtès
2022-11-10 12:39 ` zimoun
2022-11-17 14:54 ` Ludovic Courtès
2022-11-05 17:58 ` Ludovic Courtès
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=86wn87lxwv.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=guix-devel@gnu.org \
--cc=ludo@gnu.org \
--cc=phil@beadling.co.uk \
/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).