On 2/22/19, Dale Snell wrote:
> you should be able to do something like "mrphl\|\:blrphl" and the two words
> should be separated by a thinspace that can break.
Hi Dale,
Thank you for the idea. If that did work (and with limited testing I
haven't been able to get it to), it would create a nonbr
On 2/27/19, G. Branden Robinson wrote:
> Opinions on the utility of the stripper script among the groff
> development team are mixed.
Historically true, but the last couple of times the topic came up on
this list, no one stepped forward to defend stripping. See threads
starting at:
- http://lis
> The mandoc package is also slowly becoming more popular on Linux.
> For example, optional packages exist for Debian, Ubuntu, Gentoo,
> Arch, Alpine, Void, Slackware, Crux, ... So quite a few Linux users
> may already have Kristaps' modern mdoc(7) manual page in addition
> to the classical groff_
Hi Michael,
Michael Kerrisk (man-pages) wrote on Fri, Mar 01, 2019 at 10:49:41AM +0100:
> Just to be clear, I'm not against mdoc in any way. (I consider it
> unfortunate that man markup isn't at all semantic.)
>
> It's just that the project that I inherited had > 95% pages in man
> format, and t
> [...] it would create a nonbreaking space and then a
> breakpoint, which would result in that space appearing at
> the end of the line, which would misalign the right margin
> in fully justified text. I'm looking for a fixed-width
> space that can be *replaced* by a line break (the typical
>
On Thursday, 28 February 2019 19:42:45 GMT Colin Watson wrote:
> On Thu, Jan 24, 2019 at 02:34:35PM +, Colin Watson wrote:
> > The "<>" operator is implemented using the two-argument form of "open",
> > which interprets magic such as pipe characters, allowing execution of
> > arbitrary commands
