public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: Collin Funk <collin.funk1@gmail.com>
To: Alejandro Colomar <alx@kernel.org>
Cc: "Pádraig Brady" <P@draigbrady.com>,
	coreutils@gnu.org, linux-man@vger.kernel.org
Subject: Re: Move GNU manual pages to the Linux man-pages project
Date: Sat, 20 Sep 2025 13:05:52 -0700	[thread overview]
Message-ID: <87o6r4zy73.fsf@gmail.com> (raw)
In-Reply-To: <jcxx3nfilug5tfk7ktgr4n4sw3nsvympz7tslsblqlqxbm6ou3@hu34rdpdtajr>

Alejandro Colomar <alx@kernel.org> writes:

> Hi Pádraig,
>
> On Sat, Sep 20, 2025 at 06:01:21PM +0100, Pádraig Brady wrote:
>> > > All of the man pages have links to the info docs for full documentation.
>> > 
>> > I know.  However, many users don't enjoy the info docs.
>> 
>> I my experience user don't enjoy the info _reader_, while the docs are fine.
>> The full docs are on the web though and also linked from each man page.
>
> Yeah, the info online docs are much nicer.  However, I (and others)
> don't enjoy going online for documentation, when offline documentation
> is available.

I wish distributions installed the HTML docs to
/usr/share/doc/coreutils, or somewhere similar (and substitute package
name for other packages). The gnu.org site is down or takes ages to load
frequently nowadays.

That said, I have seen complaints about the Coreutils man pages being
"incomplete". However, it is grown on me personally. I use the man pages
as a quick reference when I want to find an option or understand what it
does. And the info page for examples and/or commentary that is too long
to reasonably fit in --help.

Writing all of that in groff would be a pain. More of my time would be
spent understanding the syntax than it would be focusing on the content.
Texinfo's syntax is much more readable and easy to remember. And the
HTML and PDF output look nice to read.

I guess Markdown or reStructuredText would be more friendly to new
contributors since many do not know Texinfo. However, I haven't seen
good PDFs generated by them (though I concede that I very well could be
unaware of examples).

Collin

  reply	other threads:[~2025-09-20 20:05 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-20 16:08 Move GNU manual pages to the Linux man-pages project Alejandro Colomar
2025-09-20 16:27 ` Sam James
2025-09-20 16:50   ` Alejandro Colomar
2025-09-20 17:00   ` Alejandro Colomar
2025-09-20 16:34 ` Pádraig Brady
2025-09-20 16:55   ` Alejandro Colomar
2025-09-20 17:01     ` Pádraig Brady
2025-09-20 17:04       ` Alejandro Colomar
2025-09-20 20:05         ` Collin Funk [this message]
2025-09-20 21:05           ` Alejandro Colomar
2025-09-20 23:02             ` Collin Funk
2025-09-21  8:36               ` Alejandro Colomar
     [not found]           ` <PA3P190MB24382227EA61EC2758D5AA11C410A@PA3P190MB2438.EURP190.PROD.OUTLOOK.COM>
2025-09-20 23:18             ` Collin Funk
2025-09-22 15:06             ` Michael Greenberg
2025-09-20 17:42       ` Jakub Wilk
2025-09-20 21:10         ` Alejandro Colomar
2025-09-20 21:22           ` Collin Funk
2025-09-21  8:28         ` Bernhard Voelker
2025-09-21 20:00       ` Chuck Wolber
2025-09-21 12:02 ` Arsen Arsenović
2025-09-21 12:53   ` Alejandro Colomar
2025-09-25 14:04     ` Arsen Arsenović
2025-09-25 14:31       ` Alejandro Colomar
2025-09-29  9:46         ` Arsen Arsenović
2025-09-29 10:33           ` Alejandro Colomar
2025-09-29 21:26             ` Arsen Arsenović
2025-09-29 21:38               ` Alejandro Colomar
2025-09-29 21:41             ` Pádraig Brady
2025-09-29 23:27               ` Alejandro Colomar
2025-09-30 10:12                 ` Pádraig Brady
2025-09-30 21:14                   ` Bernhard Voelker
2025-09-30 13:23       ` Rob Landley
2025-09-30 13:35         ` G. Branden Robinson
2025-09-30 19:57         ` Arsen Arsenović
2025-09-30 20:55           ` G. Branden Robinson
2025-10-01 13:21             ` Arsen Arsenović
2025-10-01 19:37           ` Rob Landley
2025-10-02 18:46             ` Arsen Arsenović
2025-10-02 20:48               ` G. Branden Robinson

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=87o6r4zy73.fsf@gmail.com \
    --to=collin.funk1@gmail.com \
    --cc=P@draigbrady.com \
    --cc=alx@kernel.org \
    --cc=coreutils@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