From: Alejandro Colomar <alx@kernel.org>
To: "G. Branden Robinson" <g.branden.robinson@gmail.com>
Cc: linux-man@vger.kernel.org
Subject: Re: managing tagged paragraphs (was: [PATCH 2/2] ioctl_pagemap_scan: add page for pagemap_scan IOCTL)
Date: Sun, 29 Oct 2023 02:42:31 +0200 [thread overview]
Message-ID: <ZT2qfeegOCgUTKOH@debian> (raw)
In-Reply-To: <20231028180703.e4kqfnueaxp5dx7q@illithid>
[-- Attachment #1: Type: text/plain, Size: 2123 bytes --]
Hi Branden,
On Sat, Oct 28, 2023 at 01:07:03PM -0500, G. Branden Robinson wrote:
> At 2023-10-28T18:22:52+0200, Alejandro Colomar wrote:
> > I meant to ask if modifying RS's behavior to not break after TP was
> > something you'd consider viable.
>
> Ahh. Hmm. Can you show me an exhibit of desired output?
I'd like both sections to be identical in the following page (with the
behavior of the first one).
$ cat RS.man
.TH RS 7 to-morrow Alex
.SH Continuing TP with IP
.TP
tag
First paragraph.
.IP
Second paragraph.
.SH Continuing TP with RS
.TP
tag
.RS
First paragraph.
.PP
Second paragraph.
.RE
$ MANWIDTH=72 man ./RS.man | cat
RS(7) Miscellaneous Information Manual RS(7)
Continuing TP with IP
tag First paragraph.
Second paragraph.
Continuing TP with RS
tag
First paragraph.
Second paragraph.
Alex to‐morrow RS(7)
>
> > $ MANWIDTH=82 man groff_man_style | wc
> > 1442 10152 81154
> > $ MANWIDTH=83 man groff_man_style | wc
> > 1435 10156 80990
>
> Only thing I can guess here is that man-db man(1) runs sandboxed and so
> might not be running a groff from $HOME.
Heh, I've managed to reproduce it! It seems I run that thing just
before installing groff from git in this computer:
$ /usr/bin/groff --version | head -n1
GNU groff version 1.23.0
$ /usr/local/bin/groff --version | head -n1
GNU groff version 1.23.0.497-e982
$ MANROFFOPT=--version man man | head -n1
GNU nroff (groff) version 1.23.0.497-e982
$ PATH=/usr/bin
$ MANROFFOPT=--version man man | head -n1
GNU nroff (groff) version 1.23.0
$ MANWIDTH=80 man groff_man_style | wc
1439 9943 81331
>
> > Me too. I remember my promise to review it; I'm just very slow; even
> > slower than sloppy recuriters.
>
> I had no idea such a low speed was possible.
I've taken an entire year to read the Picture of Dorian Gray, if that
gives you an idea. :D
Cheers,
Alex
--
<https://www.alejandro-colomar.es/>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-10-29 0:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-19 13:12 [PATCH 1/2] ioctl_userfaultfd.2: add UFFD_FEATURE_WP_ASYNC Muhammad Usama Anjum
2023-10-19 13:12 ` [PATCH 2/2] ioctl_pagemap_scan: add page for pagemap_scan IOCTL Muhammad Usama Anjum
2023-10-23 21:52 ` Alejandro Colomar
2023-10-24 2:48 ` G. Branden Robinson
2023-10-24 10:40 ` Alejandro Colomar
2023-10-28 13:07 ` managing tagged paragraphs (was: [PATCH 2/2] ioctl_pagemap_scan: add page for pagemap_scan IOCTL) G. Branden Robinson
2023-10-28 16:22 ` Alejandro Colomar
2023-10-28 18:07 ` G. Branden Robinson
2023-10-29 0:42 ` Alejandro Colomar [this message]
2023-10-24 15:51 ` [PATCH 2/2] ioctl_pagemap_scan: add page for pagemap_scan IOCTL Muhammad Usama Anjum
2023-10-19 13:27 ` [PATCH 1/2] ioctl_userfaultfd.2: add UFFD_FEATURE_WP_ASYNC Alejandro Colomar
2023-10-19 13:29 ` Alejandro Colomar
2023-10-19 13:34 ` Muhammad Usama Anjum
2023-10-19 13:42 ` Alejandro Colomar
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=ZT2qfeegOCgUTKOH@debian \
--to=alx@kernel.org \
--cc=g.branden.robinson@gmail.com \
--cc=linux-man@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.