All of lore.kernel.org
 help / color / mirror / Atom feed
From: "G. Branden Robinson" <g.branden.robinson@gmail.com>
To: Alejandro Colomar <alx.manpages@gmail.com>
Cc: linux-man@vger.kernel.org
Subject: Re: [PATCH 2/9] ldconfig.8: Fix style nits
Date: Thu, 5 Jan 2023 06:35:38 -0600	[thread overview]
Message-ID: <20230105123538.kkg53yge3e2fhxjk@illithid> (raw)
In-Reply-To: <ee241821-34a4-a5a3-f757-dc7018241bc7@gmail.com>

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

Hi Alex,

At 2023-01-05T13:03:01+0100, Alejandro Colomar wrote:
> On 1/4/23 21:04, G. Branden Robinson wrote:
> > Official GNU resistance to man pages is broad and deep, but not
> > universal.
> 
> Is there still resistance apart from written?

This is hard to me to judge, but I also interpret unorthodox man page
typography as constitutive of resistance.  I credit Albert Cahalan with
giving me a formative experience in reading a man page that was written
with resentment.[1]  Countless thousands of Debian ps(1) page readers,
often under stress trying to figure out how to identify and kill a rogue
process, attempted self-help and found themselves served a dinner plate
of steaming documentary hostility, innocent bystanders caught up in a
pointless vendetta against a text formatting language.

When Mr. Cahalan passes, I hope his family has the funds to engrave the
first comment block from his ps(1) rewrite on his headstone.

> Most contributors to GNU today seem to use man pages.  There are still
> a few projects, like make(1) which would be better with manual pages
> documenting the language, but most have useful manual pages, don't
> they?

GNU programs whose manuals have Invariant Sections or Cover Texts under
the FDL tend also to lack freely-licensed man pages.

Fortunately groff doesn't have this problem, because it's all
dual-licensed GPL.

> Maybe Debian helped get there.

I'd like to think so.  I was around when Debian still took a lot of crap
for adopting that stance.  Now it has users who weren't born yet when
that policy decision was made.

If you don't have further comments on v2 I'll make a few more changes to
v3 and submit it.

Regards,
Branden

[1] https://gitlab.com/procps-ng/procps/blob/7ac9a0e1f5606696dc799b773d5ec70183ca91a3/ps/ps.1

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

  reply	other threads:[~2023-01-05 12:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-04  7:38 [PATCH 2/9] ldconfig.8: Fix style nits G. Branden Robinson
2023-01-04 18:50 ` Alejandro Colomar
2023-01-04 20:04   ` G. Branden Robinson
2023-01-05 12:03     ` Alejandro Colomar
2023-01-05 12:35       ` G. Branden Robinson [this message]
2023-01-05 18:09         ` Alejandro Colomar
2023-01-06  0:29       ` 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=20230105123538.kkg53yge3e2fhxjk@illithid \
    --to=g.branden.robinson@gmail.com \
    --cc=alx.manpages@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.