Linux Manual Pages development
 help / color / mirror / Atom feed
From: "G. Branden Robinson" <g.branden.robinson@gmail.com>
To: Alejandro Colomar <alx@kernel.org>
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 08:21:59 -0500	[thread overview]
Message-ID: <20231028132159.zkf6fh34mmfjzu37@illithid> (raw)
In-Reply-To: <ZTpz3A0yijoxDvip@debian>

[-- Attachment #1: Type: text/plain, Size: 1985 bytes --]

Hi Alex,

At 2023-10-26T16:12:36+0200, Alejandro Colomar wrote:
> Yup.  I have similar feelings about C++, BTW.  I have a hard time
> understanding complex languages.  I prefer simpler languages.  Most
> features can be implemented as library code, without complicating the
> language.

Just know that following this road will take you to Lisp.  Or Scheme.

Or Forth.  ;-)

(Personally, I wish regular C _had_ put memcpy and memset (or bzero :P )
in the language.)

> Yep, I have 2/2 locally.  Maybe reply to the mail CCing vger, keeping
> only the commit message, so that readers of the list can get a notice
> of what MR.sed is.

Okay.  I'll aim for that for v5.

> I always make the mistake of writing MS instead of MT, out of inertia
> of having an 'S' for the start!  :D

Yes, that's what Doug McIlroy thought might happen.

> The others have nicer mnemonics that work for me; I wouldn't change
> them.  And well, just for changing MT, I wouldn't do it.
> 
> > 	SY -> NS (syNopsis start)
> > 	YS -> NE (syNopsis end)
> 
> Hmmm, no; I don't like it.

Fair enough.  I venture these things on the off chance that they're
brilliant strokes that will greatly increase the appeal of learning
man(7).

> 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.

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.)

Regards,
Branden

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  parent reply	other threads:[~2023-10-28 13:22 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       ` G. Branden Robinson [this message]
2023-10-28 16:30         ` `\c`, mdoc(7), and man(7) extension macros (was: [PATCH 1/2] man*/: srcfix) Alejandro Colomar
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=20231028132159.zkf6fh34mmfjzu37@illithid \
    --to=g.branden.robinson@gmail.com \
    --cc=alx@kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox