9front - general discussion about 9front
 help / color / mirror / Atom feed
From: sl@stanleylieber.com
To: 9front@9front.org
Subject: Re: [9front] werc/apps/wman botches some man page links
Date: Tue, 14 Aug 2018 12:38:56 -0400	[thread overview]
Message-ID: <20180814163856.Q7intVgeu3-_4JFe5Fs3464Y-CjpNsY5zP-fOWnfupc@z> (raw)
In-Reply-To: 0DD69EF566814D200356382A0279A190@prosimetrum.com

>> I think the best solution is to insert a newline
>> immediately after the man page link, wherever
>> it may fall. This isn’t perfect but it’s better than
>> having one infinitely long line sticking out of
>> an otherwise consistently formatted section.
> 
> Sorry, I think I was unclear.  What I mean is
> if, eg, you change /sys/man/8/venti:319 to read:
> 
> .IR venti\-fmt (8)).

[...]

> My other point was that perhaps these strings
> shouldn't be broken in normal nroff output
> anyway. I mean, it breaks plumbing the string,
> which is kind of the whole point of the cmd(#)
> format..., so fixing it in the source is
> perhaps justified?

This sounds reasonable to me.

Anyone else have an opinion?

sl


             reply	other threads:[~2018-08-14 16:38 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-14 16:38 sl [this message]
     [not found] <FA9BA3B9FCBF4FA28D3066A7570CD898@ewsd.inri.net>
2018-08-15 13:08 ` Ethan A. Gardener
2018-08-15 13:41   ` Stanley Lieber
2018-08-15 13:44     ` Stanley Lieber
2018-08-16 15:51       ` Ethan A. Gardener
  -- strict thread matches above, loose matches on Subject: below --
2018-08-14 16:40 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=20180814163856.Q7intVgeu3-_4JFe5Fs3464Y-CjpNsY5zP-fOWnfupc@z \
    --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).