9front - general discussion about 9front
 help / color / mirror / Atom feed
From: Stanley Lieber <sl@stanleylieber.com>
To: 9front@9front.org
Subject: Re: [9front] werc/apps/wman botches some man page links
Date: Mon, 13 Aug 2018 10:23:15 -0400	[thread overview]
Message-ID: <042D6631-697B-420C-B44B-ABB6CD7DE48C@stanleylieber.com> (raw)
In-Reply-To: <40B20E9A9E6289EA955A6EF6D4BAAF94@prosimetrum.com>

On Aug 13, 2018, at 4:26 AM, Travis Moore <umbraticus@prosimetrum.com> wrote:
> 
> if you insert a backslash before the offending
> hyphen in the source it prevents the split.
> 
> not sure if this is helpful, but perhaps it
> shouldn't be splitting in the regular text
> output either...
> 
> from /sys/doc/troff.ps!25 :
> 
>    Words that contain hyphens ... are
>    always subject to splitting after
>    those characters, whether automatic
>    hyphenation is on or off.
> 
> so you can't just turn off hyphenation...

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.

I’m reluctant to bin the markdown-transiting
version because it’s output includes less
tags and is less likely to trigger CSS
convulsions.

sl




  reply	other threads:[~2018-08-13 14:23 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-13  8:26 Travis Moore
2018-08-13 14:23 ` Stanley Lieber [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 16:38 sl
2018-08-14  4:49 Travis Moore
     [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=042D6631-697B-420C-B44B-ABB6CD7DE48C@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).