From: Raghav Gururajan <raghavgururajan@disroot.org>
To: Andreas Enge <andreas@enge.fr>, zimoun <zimon.toutoune@gmail.com>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: REQUEST to Guix Maintainers
Date: Sun, 10 Nov 2019 06:05:47 -0500 [thread overview]
Message-ID: <d781eb93660aeb23dff392bbb277cb16d3f9752c.camel@disroot.org> (raw)
In-Reply-To: <20191110104114.GA30909@jurong>
[-- Attachment #1: Type: text/plain, Size: 256 bytes --]
> pandoc is a good idea, but the texinfo file causes error messages. I
> did
> the following, which worked well:
>
> makeinfo --html --no-split guix-cookbook.texi
> pandoc guix-cookbook.html -o guix-cookbook.epub
Thank you :-)
Regards,
RG.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2019-11-10 11:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-06 8:08 REQUEST to Guix Maintainers Raghav Gururajan
2019-11-06 10:23 ` Konrad Hinsen
2019-11-06 10:26 ` Raghav Gururajan
2019-11-06 10:35 ` zimoun
2019-11-06 11:18 ` Raghav Gururajan
2019-11-10 10:41 ` Andreas Enge
2019-11-10 11:05 ` Raghav Gururajan [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=d781eb93660aeb23dff392bbb277cb16d3f9752c.camel@disroot.org \
--to=raghavgururajan@disroot.org \
--cc=andreas@enge.fr \
--cc=help-guix@gnu.org \
--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.
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).