From: Alexis <flexibeast@gmail.com>
To: supervision@list.skarnet.org
Subject: Re: [request for review] Port of s6 documentation to mdoc(7)
Date: Wed, 02 Sep 2020 10:50:15 +1000 [thread overview]
Message-ID: <87v9gxvw6w.fsf@ada> (raw)
In-Reply-To: <20200901161327.6f215b86@mydesk.domain.cxm>
Steve Litt <slitt@troubleshooters.com> writes:
> Depends on how the HTML is written ... All I'm saying is don't
> assume,
> sight unseen, that the current HTML can't easily be converted to
> semantic LaTeX or Docbook or whatever.
This is good advice in general; but in this particular case,
there's no "sight unseen" involved on my part. i have actually
looked at the HTML sources of the existing s6 documentation. (For
some context, i've authored HTML professionally myself.)
As i indicated in the post to which you responded, as well as in
my last post to this list:
https://www.mail-archive.com/supervision@list.skarnet.org/msg02560.html
the current HTML markup is basically not semantic, but
presentationally-based.
(i'm not complaining about this. i'm very grateful that Laurent
has provided such comprehensive documentation for s6; many
software authors provide far less, or suggest that the source is
the end-user documentation. i feel s6 is a sufficiently important
project that i'm happy to help out with documentation stuff,
rather than putting further demands on Laurent's already-saturated
bandwidth.)
To be more specific regarding one of the points in my last post,
here's an excerpt from s6-envuidgid.html:
<pre>
s6-envuidgid [ -u | -g | -B ] [ -n ] [ -i | -D
<em>uid</em>:<em>gid</em>:<em>gidlist</em> ]
<em>account</em> <em>prog...</em>
</pre>
Alexis.
next prev parent reply other threads:[~2020-09-02 0:50 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-30 8:30 Alexis
2020-08-30 9:10 ` eric vidal
2020-08-31 6:56 ` Alexis
2020-08-30 10:01 ` Laurent Bercot
2020-08-31 7:01 ` Alexis
2020-08-31 11:04 ` Laurent Bercot
2020-08-31 14:29 ` Guillermo
2020-09-01 10:00 ` possible s6-rc redesign (was: [request for review] Port of s6 documentation to mdoc(7)) Laurent Bercot
2020-09-01 19:24 ` possible s6-rc redesign mobinmob
2020-09-01 22:16 ` Dudemanguy
2020-09-01 22:20 ` Laurent Bercot
2020-09-02 9:41 ` mobinmob
2020-09-02 12:14 ` Laurent Bercot
2020-09-01 23:14 ` possible s6-rc redesign (was: [request for review] Port of s6 documentation to mdoc(7)) Steve Litt
2020-08-31 16:08 ` [request for review] Port of s6 documentation to mdoc(7) J. Lewis Muir
2020-08-31 17:45 ` Jason Lenz
2020-08-31 19:14 ` J. Lewis Muir
2020-08-31 20:51 ` Laurent Bercot
2020-09-01 6:38 ` Casper Ti. Vector
2020-09-01 9:03 ` Alexis
2020-09-01 9:20 ` Casper Ti. Vector
2020-09-01 10:02 ` Alexis
2020-09-01 10:15 ` Casper Ti. Vector
2020-09-01 20:13 ` Steve Litt
2020-09-02 0:50 ` Alexis [this message]
[not found] ` <20200901063801.GA2158@caspervector>
2020-09-01 10:11 ` Laurent Bercot
2020-09-01 11:28 ` Casper Ti. Vector
2020-09-01 11:55 ` Alexis
2020-08-31 19:36 ` Laurent Bercot
2020-08-31 19:58 ` J. Lewis Muir
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=87v9gxvw6w.fsf@ada \
--to=flexibeast@gmail.com \
--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).