From: Lennart Jablonka <ljabl@ljabl.com>
To: "G. Branden Robinson" <g.branden.robinson@gmail.com>,
Paul Eggert <eggert@cs.ucla.edu>
Cc: Alejandro Colomar <alx.manpages@gmail.com>,
linux-man <linux-man@vger.kernel.org>, groff <groff@gnu.org>,
Deri <deri@chuzzlewit.myzen.co.uk>
Subject: Re: Doubts about a typo fix
Date: Sun, 25 Dec 2022 22:07:01 +0000 [thread overview]
Message-ID: <Y6jJhU2rQ3qBYwWD@fluorine.ljabl.com> (raw)
In-Reply-To: <20221213192410.aisrx6gwqcwlodq5@illithid>
Quoth G. Branden Robinson:
>> > I believe Solaris troff to be fossilized
>>
>> Yes and no. Solaris 10 is no longer supported after January 2024, so
>> if it and all the other traditional troffs die out by 2024 we can stop
>> worrying about this then.
>
>That may in fact prove out; the only _currently-maintained_ troffs I
>know of are groff, Heirloom Doctools troff (though it has slowed down)
>and neatroff.
I am devastated that 9front troff is unhesitatingly disregarded
again and again like this. While it’s seeing few commits, it is
serving us very well.
Nope, not all traditional troffs will die that easily.
next prev parent reply other threads:[~2022-12-25 22:13 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-23 19:31 Doubts about a typo fix Alejandro Colomar
2022-11-23 21:40 ` G. Branden Robinson
2022-11-26 2:18 ` Paul Eggert
2022-11-26 3:20 ` [tz] " Russ Allbery
2022-11-26 3:50 ` Paul Eggert
2022-11-26 20:44 ` G. Branden Robinson
2022-11-26 3:52 ` G. Branden Robinson
2022-11-26 12:33 ` Deri
2022-11-26 21:01 ` Paul Eggert
2022-11-26 21:56 ` G. Branden Robinson
2022-11-27 1:58 ` Deri
2022-11-27 2:32 ` Paul Eggert
2022-12-13 19:24 ` G. Branden Robinson
2022-12-25 22:07 ` Lennart Jablonka [this message]
2022-12-25 23:21 ` G. Branden Robinson
2022-11-26 21:20 ` Steffen Nurpmeso
2022-11-26 22:07 ` G. Branden Robinson
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=Y6jJhU2rQ3qBYwWD@fluorine.ljabl.com \
--to=ljabl@ljabl.com \
--cc=alx.manpages@gmail.com \
--cc=deri@chuzzlewit.myzen.co.uk \
--cc=eggert@cs.ucla.edu \
--cc=g.branden.robinson@gmail.com \
--cc=groff@gnu.org \
--cc=linux-man@vger.kernel.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