From: Alejandro Colomar <alx@kernel.org>
To: "G. Branden Robinson" <g.branden.robinson@gmail.com>
Cc: linux-man@vger.kernel.org, groff@gnu.org
Subject: Re: `\c`, mdoc(7), and man(7) extension macros (was: [PATCH 1/2] man*/: srcfix)
Date: Sat, 28 Oct 2023 18:30:13 +0200 [thread overview]
Message-ID: <ZT03FcWI7V5iQIon@debian> (raw)
In-Reply-To: <20231028132159.zkf6fh34mmfjzu37@illithid>
[-- Attachment #1: Type: text/plain, Size: 976 bytes --]
Hi Branden,
On Sat, Oct 28, 2023 at 08:21:59AM -0500, G. Branden Robinson wrote:
> > Regarding PP, LP, and P, what's the history of them? Why do we have
> > the 3? I'm willing to reduce them to just one.
>
> We covered this in another thread, but as Ingo noted, there is no hope
> of actually _retiring_ any of these. At most they can be documentarily
> deprecated and a high "-rCHECKSTYLE" setting can gripe about them.
Makes sense.
>
> groff man(7) formats every Seventh Edition Unix (1979) man page
> correctly as far as I can tell, and I don't want to ever give that up.
>
> (This is a slightly different objective from preserving perfect
> compatibility with 7th edition's tmac.an. I have no qualms about
> discarding compatibility with details of macro package behavior that no
> one relied upon for practical purposes.)
This gives me hope in changing the behavior of RS. :P
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-28 16:30 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-25 18:54 [PATCH 1/2] man*/: srcfix G. Branden Robinson
2023-10-25 19:38 ` Alejandro Colomar
2023-10-26 12:58 ` `\c`, mdoc(7), and man(7) extension macros (was: [PATCH 1/2] man*/: srcfix) G. Branden Robinson
2023-10-26 14:12 ` Alejandro Colomar
2023-10-26 14:51 ` Why does man(7) have 3 paragraph macros for the same thing? (was: `\c`, mdoc(7), and man(7) extension macros) G. Branden Robinson
2023-10-26 14:58 ` Alejandro Colomar
2023-10-26 15:28 ` G. Branden Robinson
2023-10-26 17:52 ` Why does man(7) have 3 paragraph macros for the same thing? Ingo Schwarze
2023-10-26 22:16 ` Alejandro Colomar
2023-10-26 22:02 ` Why does man(7) have 3 paragraph macros for the same thing? (was: `\c`, mdoc(7), and man(7) extension macros) Alejandro Colomar
2023-10-26 16:09 ` G. Branden Robinson
2023-10-26 21:59 ` Alejandro Colomar
2023-10-28 13:21 ` `\c`, mdoc(7), and man(7) extension macros (was: [PATCH 1/2] man*/: srcfix) G. Branden Robinson
2023-10-28 16:30 ` Alejandro Colomar [this message]
2023-10-26 23:27 ` Ingo Schwarze
2023-10-27 0:51 ` 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=ZT03FcWI7V5iQIon@debian \
--to=alx@kernel.org \
--cc=g.branden.robinson@gmail.com \
--cc=groff@gnu.org \
--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.