From: Alejandro Colomar <alx@kernel.org>
To: Douglas McIlroy <douglas.mcilroy@dartmouth.edu>
Cc: linux-man@vger.kernel.org
Subject: Re: syntax of options in man1
Date: Fri, 17 Jul 2026 14:10:23 +0200 [thread overview]
Message-ID: <alobDcKZVkwVqzRx@devuan> (raw)
In-Reply-To: <CAKH6PiXx=WycAiPGti3LAAfpmDQExkcWsatXjOXpD=GdiMc0ng@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1719 bytes --]
Hi Doug,
On 2026-07-16T13:19:20-0400, Douglas McIlroy wrote:
> > I think there should be a separation between an introduction to the
> > entire system (maybe this could be intro(0)), and an introduction to the
> > first section of the manual (intro(1)).
>
> I agree. In the early days, at least, there was such a section, called
> "getting started". I like the idea of calling it intro(0). The very name
> suggests that there are more intro(.) pages. Elegant!
Thanks! I've done the split already.
commit 214f536963b0a108abc54b336d8ac21b4c9f1c7f
Author: Alejandro Colomar <alx@kernel.org>
Date: 2026-07-17 14:05:19 +0200
man/man?/intro.[01]: Split part of intro(1) into a new intro(0)
Let's keep intro(1) for introducing just the man1 section, and move the
more general introduction of the entire manual to a new intro(0).
Acked-by: Douglas McIlroy <douglas.mcilroy@dartmouth.edu>
Signed-off-by: Alejandro Colomar <alx@kernel.org>
I haven't yet documented the syntax we were talking about, though. I'll
think about the best way to document that.
Here's how intro(1) looks like now:
$ MANWIDTH=64 man man1/intro.1 | cat
intro(1) General Commands Manual intro(1)
NAME
intro - introduction to user commands
DESCRIPTION
Section 1 of the manual describes user commands and tools,
for example, file manipulation tools, shells, compilers,
web browsers, file and image viewers and editors, and so
on.
SEE ALSO
intro(0)
Linux man‐pages (unreleased) (date) intro(1)
Have a lovely day!
Alex
--
<https://www.alejandro-colomar.es>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2026-07-17 12:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAKH6PiXDGL658h1t_bstW0Z+MjjJfcNmcde-DA3QNOYKc0TTGg@mail.gmail.com>
2026-07-16 14:45 ` syntax of options in man1 Alejandro Colomar
2026-07-16 15:55 ` G. Branden Robinson
2026-07-16 16:20 ` Alejandro Colomar
2026-07-16 17:05 ` G. Branden Robinson
[not found] ` <CAKH6PiXx=WycAiPGti3LAAfpmDQExkcWsatXjOXpD=GdiMc0ng@mail.gmail.com>
2026-07-16 19:43 ` Douglas McIlroy
2026-07-17 12:10 ` Alejandro Colomar [this message]
2026-07-17 17:15 ` G. Branden Robinson
2026-07-17 17:23 ` 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=alobDcKZVkwVqzRx@devuan \
--to=alx@kernel.org \
--cc=douglas.mcilroy@dartmouth.edu \
--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.