From: Philip Beadling <phil@beadling.co.uk>
To: jgart <jgart@dismail.de>, Guix Help <help-guix@gnu.org>
Subject: Re: GNU Guix Channel with Babel
Date: Mon, 29 Aug 2022 06:42:41 +0000 [thread overview]
Message-ID: <LO0P123MB38985F8F211934674DA2F0C4F9769@LO0P123MB3898.GBRP123.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <20220828175015.GB25037@gac>
I've thought about doing this for Channel definitions, and also for packages in my own channel.
One thing that struck me is Skribilio might be a more interesting literate format, given its written in Guile too.
https://www.nongnu.org/skribilo/
________________________________
From: Help-Guix <help-guix-bounces+phil=beadling.co.uk@gnu.org> on behalf of jgart <jgart@dismail.de>
Sent: Sunday, August 28, 2022 11:50:15 PM
To: Guix Help <help-guix@gnu.org>
Subject: GNU Guix Channel with Babel
Hi, has anyone tried to create a GNU Guix channel as org babel file(s)
that get untangled and serve a dual purpose as a blog describing the
channel packages, reasons for packaging them, etc?
The blog would get generated and published via HTTP and/or gemini.
next prev parent reply other threads:[~2022-08-29 6:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-28 22:50 GNU Guix Channel with Babel jgart
2022-08-29 6:42 ` Philip Beadling [this message]
2022-08-29 13:00 ` Akib Azmain Turja
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=LO0P123MB38985F8F211934674DA2F0C4F9769@LO0P123MB3898.GBRP123.PROD.OUTLOOK.COM \
--to=phil@beadling.co.uk \
--cc=help-guix@gnu.org \
--cc=jgart@dismail.de \
/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).