From: "J. Lewis Muir" <jlmuir@imca-cat.org>
To: Laurent Bercot <ska-supervision@skarnet.org>
Cc: "supervision@list.skarnet.org" <supervision@list.skarnet.org>
Subject: Re: runit patches to fix compiler warnings on RHEL 7
Date: Wed, 4 Dec 2019 15:32:03 -0600 [thread overview]
Message-ID: <20191204213203.4sb5onelaoa6geu3@mink.imca.aps.anl.gov> (raw)
In-Reply-To: <embe501182-10b1-4994-8671-3abd923d8c4c@elzian>
On 12/04, Laurent Bercot wrote:
> > What about mandoc?
>
> The colour of this bikeshed is not up for debate.
>
> If you want man pages for skaware, provide me with:
> 1. a reasonable source format (e.g. not roff, so mandoc is right out)
> 2. a tool that can be built using *only* a C compiler (so as to keep
> bootstrapping skaware easy), that converts the source format into man
> pages *and* into HTML
> 3. the actual contents of the man pages you want, in that source format.
>
> (https://git.sr.ht/~sircmpwn/scdoc fits 1. and 2., but its author wasn't
> motivated enough to do 3.)
Interesting, I hadn't heard of scdoc before. I don't see where it says
it can convert the source format into HTML, though. Did I miss that?
> Until then, any further discussion of documentation formats is pure
> noise, I've heard it all before - several times - and it has the potential
> to piss me off VERY quickly.
Certainly don't want to cause trouble, and not intending to bikeshed,
but I searched for "halibut" in the archive for this list as well as the
skaware list and did not find that it had been mentioned, so I'll just
mention that another system I've used in the past is Halibut which is
lightweight and written in ANSI C:
https://www.chiark.greenend.org.uk/~sgtatham/halibut/
It can generate ASCII, HTML, PDF, PostScript, man, and info. So, I
think it would satisfy #1 and #2, but certainly not #3. Still, if
someone wanted to do the work to provide #3 at some point, then Halibut
may be a reasonable tool to consider.
Lewis
next prev parent reply other threads:[~2019-12-04 21:32 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-25 21:43 J. Lewis Muir
2019-11-27 20:33 ` J. Lewis Muir
2019-11-28 7:59 ` Ben Franksen
[not found] ` <ecdf4d8f-93f6-3f9f-b84c-351fa91c7f02@uni-bremen.de>
2019-11-28 19:04 ` Laurent Bercot
2019-11-28 20:39 ` Steve Litt
2019-11-28 22:17 ` runit or s6 (was: runit patches to fix compiler warnings on RHEL 7) Laurent Bercot
2019-11-29 14:09 ` runit patches to fix compiler warnings on RHEL 7 Jan Braun
2019-11-29 21:46 ` Dewayne Geraghty
2019-11-30 1:22 ` Colin Booth
2019-11-30 0:21 ` Colin Booth
2019-11-30 3:14 ` Steve Litt
2019-11-30 13:32 ` Jeff
2019-11-30 13:46 ` Jeff
2019-11-30 10:15 ` s6 usability (was: runit patches to fix compiler warnings on RHEL 7) Laurent Bercot
2019-11-30 14:32 ` Jeff
2019-11-30 18:58 ` Laurent Bercot
2019-12-02 12:07 ` Jeff
2019-12-02 22:20 ` Laurent Bercot
2019-12-02 2:47 ` Steve Litt
2019-12-02 3:37 ` s6 usability Dewayne Geraghty
2019-12-02 10:24 ` fungal-net
2019-12-02 21:32 ` s6 usability (was: runit patches to fix compiler warnings on RHEL 7) Laurent Bercot
2019-12-02 23:17 ` s6 usability Samuel Holland
2019-12-03 22:10 ` Steve Litt
2019-12-21 11:49 ` Jan Braun
2019-12-04 12:15 ` Jonathan de Boyne Pollard
2019-12-04 21:02 ` Laurent Bercot
2019-12-04 1:30 ` s6 usability (was: runit patches to fix compiler warnings on RHEL 7) Casper Ti. Vector
2019-12-21 9:26 ` s6 usability Jan Braun
2019-12-21 18:36 ` Guillermo
2019-12-21 21:19 ` Colin Booth
2019-12-22 1:05 ` Jan Braun
2019-12-22 8:30 ` Colin Booth
2019-12-21 23:46 ` Laurent Bercot
2019-12-22 5:53 ` Jan Braun
2019-12-22 20:33 ` Steve Litt
2019-12-22 23:20 ` Laurent Bercot
2019-12-23 1:28 ` Oliver Schad
2019-12-23 9:14 ` Laurent Bercot
2019-12-23 10:15 ` Jonathan de Boyne Pollard
2019-12-24 0:18 ` Oliver Schad
2019-12-23 1:57 ` Steve Litt
2019-12-23 9:00 ` Laurent Bercot
2019-12-22 23:47 ` Dewayne Geraghty
2019-12-04 11:36 ` runit patches to fix compiler warnings on RHEL 7 Jonathan de Boyne Pollard
2019-12-04 16:40 ` J. Lewis Muir
2019-12-04 20:48 ` Laurent Bercot
2019-12-04 21:32 ` J. Lewis Muir [this message]
2019-12-04 21:06 ` Steve Litt
2019-12-04 21:50 ` Laurent Bercot
[not found] ` <20191205132736.7f501460@puter>
2019-12-08 19:10 ` Laurent Bercot
2019-12-02 17:57 ` J. Lewis Muir
2019-12-02 21:06 ` J. Lewis Muir
2019-12-02 22:22 ` Laurent Bercot
2019-12-02 21:58 ` Laurent Bercot
2019-12-03 10:57 ` Benjamin Franksen
2019-12-04 10:43 ` Jonathan de Boyne Pollard
2019-12-02 17:13 ` J. Lewis Muir
2019-12-04 11:13 ` Jonathan de Boyne Pollard
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20191204213203.4sb5onelaoa6geu3@mink.imca.aps.anl.gov \
--to=jlmuir@imca-cat.org \
--cc=ska-supervision@skarnet.org \
--cc=supervision@list.skarnet.org \
/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 NNTP newsgroup(s).