From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from [192.168.1.7] ([108.95.88.138]) by ewsd; Mon Aug 13 10:23:17 EDT 2018 Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (1.0) Subject: Re: [9front] werc/apps/wman botches some man page links From: Stanley Lieber X-Mailer: iPhone Mail (15G77) In-Reply-To: <40B20E9A9E6289EA955A6EF6D4BAAF94@prosimetrum.com> Date: Mon, 13 Aug 2018 10:23:15 -0400 Content-Transfer-Encoding: quoted-printable Message-Id: <042D6631-697B-420C-B44B-ABB6CD7DE48C@stanleylieber.com> References: <40B20E9A9E6289EA955A6EF6D4BAAF94@prosimetrum.com> To: 9front@9front.org List-ID: <9front.9front.org> List-Help: X-Glyph: ➈ X-Bullshit: optimized full-stack polling HTTP over WEB2.0 STM base proxy-scale backend On Aug 13, 2018, at 4:26 AM, Travis Moore wrote= : >=20 > if you insert a backslash before the offending > hyphen in the source it prevents the split. >=20 > not sure if this is helpful, but perhaps it > shouldn't be splitting in the regular text > output either... >=20 > from /sys/doc/troff.ps!25 : >=20 > Words that contain hyphens ... are > always subject to splitting after > those characters, whether automatic > hyphenation is on or off. >=20 > 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=E2=80=99t perfect but it=E2=80=99s better than having one infinitely long line sticking out of an otherwise consistently formatted section. I=E2=80=99m reluctant to bin the markdown-transiting version because it=E2=80=99s output includes less tags and is less likely to trigger CSS convulsions. sl