From: Stanley Lieber <sl@stanleylieber.com>
To: 9front@9front.org
Subject: Re: [9front] werc/apps/wman botches some man page links
Date: Wed, 15 Aug 2018 09:41:13 -0400 [thread overview]
Message-ID: <FC88414D-F8ED-4033-B11B-0E0DBAA1878C@stanleylieber.com> (raw)
In-Reply-To: <1534338496.1344379.1474948184.2D0BA924@webmail.messagingengine.com>
On Aug 15, 2018, at 9:08 AM, Ethan A. Gardener <eekee57@fastmail.fm> wrote:
>
>> On Tue, Aug 14, 2018, at 5:40 PM, sl@stanleylieber.com wrote:
>> Counterpoint:
>>
>> If we hack nroff to solve a wman problem, now wman needs 9front.
>
> Counter-counterpoint: It's not just a wman problem, it's a plumber problem too. Does that mean the plumber will need 9front? :)
The point about werc is that most of its users are not even running Plan 9, and we only control one fork of Plan 9 tools for UNIX, which is run by approximately one werc user (me, for openbsd.stanleylieber.com). So, fixing wman by modifying one possible underlying OS doesn’t fix wman, because wman runs everywhere.
I would like for the plumbing issue to be addressed as well.
IMO, the approach that makes the most sense in this case is to \- escape the troff sources of the problem man pages.
sl
next prev parent reply other threads:[~2018-08-15 13:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <FA9BA3B9FCBF4FA28D3066A7570CD898@ewsd.inri.net>
2018-08-15 13:08 ` Ethan A. Gardener
2018-08-15 13:41 ` Stanley Lieber [this message]
2018-08-15 13:44 ` Stanley Lieber
2018-08-16 15:51 ` Ethan A. Gardener
2018-08-14 16:40 sl
-- strict thread matches above, loose matches on Subject: below --
2018-08-14 16:38 sl
2018-08-14 4:49 Travis Moore
2018-08-13 8:26 Travis Moore
2018-08-13 14:23 ` Stanley Lieber
[not found] <3638FBEF9AC44BA220720D0E4D3CDE45@ewsd.inri.net>
2018-08-12 16:50 ` Eckard Brauer
[not found] <6660A841262D98FFBB4792A0F0CB0E5D@ewsd.inri.net>
2018-08-10 8:47 ` Ethan A. Gardener
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=FC88414D-F8ED-4033-B11B-0E0DBAA1878C@stanleylieber.com \
--to=sl@stanleylieber.com \
--cc=9front@9front.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).