Steve Litt 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"
On Tue, 01 Sep 2020 10:00:22 +
"Laurent Bercot" wrote:
> s6 as a supervision suite? okay, people will use it; but it's
> already perceived as a bit complex, because there are a lot of
> binaries. It's on the high end of the acceptable difficulty range.
I've only used s6 as a supervisor a
On Tue, 01 Sep 2020 19:03:36 +1000
Alexis wrote:
> Casper Ti. Vector writes:
>
> > * We negotiate a HTML schema your documentation can be written
> > in, which
> > is based on current documentation; existing HTML documentation
> > will be
> > converted to the schema, with minimised
Laurent Bercot writes:
I'm totally willing to use a HTML schema we can negotiate, to
write
future documentation in. What I don't want to do is:
- Touch existing documentation, unless I have to rewrite the
content of
a page for some reason. Of course, if the conversion work is
done by
On Tue, Sep 01, 2020 at 10:11:14AM +, Laurent Bercot wrote:
> I'm totally willing to use a HTML schema we can negotiate, to write
> future documentation in. What I don't want to do is:
> - Touch existing documentation, unless I have to rewrite the content of
> a page for some reason. Of
On Tue, Sep 01, 2020 at 08:02:34PM +1000, Alexis wrote:
> That involves ~70 documents. Do you need all of them, or can i just provide
> a diff of a few examples? i don't currently have the HTML sources locally;
> i'd have to download them all.
Preferably some representative samples, thanks.
--
* We negotiate a HTML schema your documentation can be written in, which
is based on current documentation; existing HTML documentation will be
converted to the schema, with minimised changes. (The structuredness
of HTML helps; now you also see why knowing some Lisp is beneficial :)
Casper Ti. Vector writes:
May I request a diff (via PM) between your attempt and the
current HTMLs?
That involves ~70 documents. Do you need all of them, or can i
just provide a diff of a few examples? i don't currently have the
HTML sources locally; i'd have to download them all.
I have only seen one new feature committed to the Git repository so
far. Is it too early to ask what are you planning to change?
The new feature is orthogonal - or, rather, it will be used if I end
up *not* redesigning s6-rc.
The trend with distributions is to make service managers reactive
On Tue, Sep 01, 2020 at 07:03:36PM +1000, Alexis wrote:
> On the basis of my current experiences, it would be No Small Task to convert
> the current, presentationally-based, HTML documentation to markup that's
> sufficiently semantic to enable it to be mechanically converted to
> mdoc/roff. i
Casper Ti. Vector writes:
* We negotiate a HTML schema your documentation can be written
in, which
is based on current documentation; existing HTML documentation
will be
converted to the schema, with minimised changes.
On the basis of my current experiences, it would be No Small
On Mon, Aug 31, 2020 at 08:51:34PM +, Laurent Bercot wrote:
> - Unless, of course, someone comes up with the perfect solution (adding
> a DocBook dependency is not a perfect solution, and neither is
> generating HTML from mandoc), in which case, obviously, they would have
> the time and
For the people who are not on #s6 and have missed the countless
resurgences of this discussion, here is my position regarding
documentation formats. I hope that by the end of this mail things are
quite clear for everyone and I won't need to talk about this again,
ever.
- Doc formats seem
On 08/31, Laurent Bercot wrote:
>
> > Of course, you'd also have to convert the existing HTML documentation
> > into DocBook and then generate the mdoc and HTML from that. I would
> > understand concern over adding a dependency on a potentially heavy
> > DocBook toolchain in order to generate
Of course, you'd also have to convert the existing HTML documentation
into DocBook and then generate the mdoc and HTML from that. I would
understand concern over adding a dependency on a potentially heavy
DocBook toolchain in order to generate the HTML. One possible way
around this, though,
On 08/31, Jason Lenz wrote:
> On 8/31/20 11:08 AM, J. Lewis Muir wrote:
> > On 08/30, Laurent Bercot wrote:
> > > > i've spent the last couple of weeks porting the s6 documentation to
> > > > mdoc(7) format:
> > > >
> > > > https://github.com/flexibeast/s6-man-pages
> > > Excellent, thank you.
On 8/31/20 11:08 AM, J. Lewis Muir wrote:
On 08/30, Laurent Bercot wrote:
i've spent the last couple of weeks porting the s6 documentation to mdoc(7)
format:
https://github.com/flexibeast/s6-man-pages
Excellent, thank you. There is a lot of talk (especially on the #s6
IRC channel, but
On 08/30, Laurent Bercot wrote:
> > i've spent the last couple of weeks porting the s6 documentation to mdoc(7)
> > format:
> >
> > https://github.com/flexibeast/s6-man-pages
>
> Excellent, thank you. There is a lot of talk (especially on the #s6
> IRC channel, but occasionally on the
Hello,
El dom., 30 ago. 2020 a las 7:01, Laurent Bercot escribió:
>
> That would be totally awesome. However, I'd hold off on s6-rc for now,
> because I'm in the process of exploring a possible redesign (for better
> integration of features that distributions want before packaging and
> using
Certainly. i'll do that once i've completed a linting pass.
Excellent.
Sure, i'd be happy to reflect any changes.
And the people rejoiced and celebrated, because they would soon,
finally, have s6 man pages.
Ah, okay - thanks for the heads-up.
Also a heads-up for people who are
Laurent Bercot writes:
This is clearly the most advanced conversion ever
performed, well done!
Thank you!
Would you be willing to add a small Makefile that by default
invokes
the mandoc commands to produce the formatted man pages, and with
an
install target that installs the source to
eric vidal writes:
You're welcome. Thank at you to use 66.
i enjoy using it - trees are excellent. :-)
This is really a hard job to do. Many thanks to make it.
You're welcome!
But i will do some publicizes about your work that be visible by
user.
Thank you, much appreciated. :-)
i've spent the last couple of weeks porting the s6 documentation to mdoc(7)
format:
https://github.com/flexibeast/s6-man-pages
Excellent, thank you. There is a lot of talk (especially on the #s6
IRC channel, but occasionally on the mailing-list too) about people
wanting to have s6 man pages,
On Sun, 30 Aug 2020 18:30:16 +1000
Alexis wrote:
>
> Hi all,
>
> i recently started using 66 instead of runit on Void - thanks to
> @Obarun, @mobinmob and @teldra for their work and help!
You're welcome. Thank at you to use 66.
> Consequently, and further to
>
Hi all,
i recently started using 66 instead of runit on Void - thanks to
@Obarun, @mobinmob and @teldra for their work and help!
Consequently, and further to
https://www.mail-archive.com/supervision@list.skarnet.org/msg02278.html
:
if people like man pages, they should have man pages,
25 matches
Mail list logo
