From: Guillem Jover <guillem@hadrons.org>
To: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
Cc: Alejandro Colomar <colomar.6.4.3@gmail.com>,
Florian Weimer <fweimer@redhat.com>,
linux-man <linux-man@vger.kernel.org>,
libbsd@lists.freedesktop.org
Subject: Re: [IDEA] New pages for types: structs and typedfefs
Date: Fri, 18 Sep 2020 04:16:03 +0200 [thread overview]
Message-ID: <20200918021603.GA596604@thunder.hadrons.org> (raw)
In-Reply-To: <CAKgNAkjys+LYn1qaSXhM2gJfkv_UOnpeNPyh3QCqNLcMNBKB+g@mail.gmail.com>
Hi!
[ I see this has already been merged, just giving some little context,
from the libbsd side. :) ]
On Sun, 2020-09-13 at 14:01:22 +0200, Michael Kerrisk (man-pages) wrote:
> On Sat, 12 Sep 2020 at 10:59, Alejandro Colomar <colomar.6.4.3@gmail.com> wrote:
> > On 2020-09-12 08:33, Michael Kerrisk (man-pages) wrote:
> > > Your not the first to suggest this. Most recently, if I recall
> > > correctly, Florian also suggested it.
> > >
> > > The idea seems reasonable, but I wonder about the best way of doing it.
Yes, this sounds great, this is also something I've missed from time
to time. :)
> > libbsd already provides a few pages on types. Maybe we could have a
> > look at them. At least I've seen 'man timespec' (which redirects to
> > timeval.3bsd):
> >
> > https://gitlab.freedesktop.org/libbsd/libbsd/-/blob/master/man/timeval.3bsd
Ah, timespec.3bsd is actually (at least) a man-db construct, libbsd
does not install an actual link on disk, I assume the .Nm macros in
the .Sh NAME section are being indexed. I should add such explicit
link for completeness though, thanks!
> > > Then of course, we'd need to have links to that page, so that
> > > people could just type 'man timer_t'. What section should the links
> > > be in? The reasonable candidates would be section 3 or 7. I'm not
> > > yet sure which is better. But the point is that we'd have files
> > > such as timer_t.3 (or timer_t.7) that are link pages containing the
> > > line:
> > >
> > > .so man7/system_data_types.7
> >
> > Sure. And for the structs, I'd allow:
> >
> > 'man struct timespec' (For simplicity)
> > 'man struct-timespec' (Similar to the git man pages)
> > 'man timespec' (For compatibility with libbsd)
>
> Mainly, I'm interested in the last case. That's the one I think that
> people would most likely use. In a follow-up mail, you expressed
> concern with conflicts with libbsd pages. I'm not too worried about
> that. There are already *many* conflicts between libbsd and man-pages.
In libbsd I try to have man pages for at least every function and macro,
ideally originating from the related BSD. The timeval.3bsd came mostly
out of a need to document the TIMEVAL_TO_TIMESPEC and TIMESPEC_TO_TIMEVAL
macros, and finding this on NetBSD:
<http://man.netbsd.org/timeval.3>
and they do seem to have dedicated man pages for some other
structures, which seems rather nice, and indeed worth imitating.
Regarding conflicts, I specifically chose to place all libbsd man
pages in the 3bsd section (both in filename and in the .Dt macro, to
avoid an actual conflict, and to not override the system man pages.
So once a man page appears in say man-pages, then that will take
precedence:
$ man explicit_bzero # man-pages version recentish addition
vs
$ man 3bsd explicit_bzero # libbsd version
Thanks,
Guillem
next prev parent reply other threads:[~2020-09-18 2:48 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-11 12:47 [IDEA] New pages for types: structs and typedfefs Alejandro Colomar
2020-09-12 6:33 ` Michael Kerrisk (man-pages)
2020-09-12 8:59 ` Alejandro Colomar
2020-09-12 9:26 ` Alejandro Colomar
2020-09-13 12:01 ` Michael Kerrisk (man-pages)
2020-09-13 12:53 ` Alejandro Colomar
2020-09-13 20:20 ` Michael Kerrisk (man-pages)
2020-09-13 21:29 ` Alejandro Colomar
2020-09-14 0:20 ` [RFC v1] system_data_types.7: Draft (and links to it: <type>.3) Alejandro Colomar
2020-09-14 10:37 ` Michael Kerrisk (man-pages)
2020-09-14 10:55 ` Michael Kerrisk (man-pages)
2020-09-22 20:21 ` [IDEA] New pages for types: structs and typedfefs Michael Kerrisk (man-pages)
2020-09-22 20:38 ` Thorsten Glaser
2020-09-23 8:36 ` Michael Kerrisk (man-pages)
2020-09-23 19:54 ` Thorsten Glaser
2020-09-14 9:19 ` Jakub Wilk
2020-09-14 9:49 ` Alejandro Colomar
2020-09-18 2:16 ` Guillem Jover [this message]
2020-09-19 8:45 ` Michael Kerrisk (man-pages)
2020-09-14 10:22 ` Alejandro Colomar
2020-09-14 14:03 ` [RFC v2] system_data_types.7: Draft v2 Alejandro Colomar
2020-09-14 15:00 ` Michael Kerrisk (man-pages)
2020-09-14 15:52 ` Alejandro Colomar
2020-09-14 19:33 ` Michael Kerrisk (man-pages)
2020-09-15 0:47 ` [RFC v3] sigval.3, ssize_t.3, suseconds_t.3, time_t.3, timer_t.3, timespec.3, timeval.3, system_data_types.7: Document system types (draft v3) Alejandro Colomar
2020-09-15 6:22 ` Michael Kerrisk (man-pages)
2020-09-15 13:33 ` [RFC v4] system_data_types.7: Document sigval, ssize_t, suseconds_t, time_t, timer_t, timespec & timeval Alejandro Colomar
2020-09-15 21:30 ` Michael Kerrisk (man-pages)
2020-09-16 0:59 ` Thorsten Glaser
2020-09-16 8:03 ` Michael Kerrisk (man-pages)
2020-09-16 10:06 ` Andries E. Brouwer
2020-09-16 11:00 ` Michael Kerrisk (man-pages)
2020-09-16 10:52 ` [RFC v5] system_data_types.7: Document types: sigval, ssize_t, suseconds_t, time_t, timer_t, timespec, timeval Alejandro Colomar
2020-09-16 10:56 ` Alejandro Colomar
2020-09-16 11:01 ` [RFC v6] " Alejandro Colomar
2020-09-16 19:24 ` Michael Kerrisk (man-pages)
2020-09-16 19:51 ` Alejandro Colomar
2020-09-16 21:32 ` Thorsten Glaser
2020-09-17 9:23 ` Alejandro Colomar
2020-09-17 10:27 ` Michael Kerrisk (man-pages)
2020-09-17 10:42 ` [PATCH v7 0/8] Document system data types Alejandro Colomar
2020-09-17 21:05 ` Michael Kerrisk (man-pages)
2020-09-17 21:16 ` Alejandro Colomar
2020-09-17 10:42 ` [PATCH v7 1/8] system_data_types.7: Document types: sigval, ssize_t, suseconds_t, time_t, timer_t, timespec, timeval Alejandro Colomar
2020-09-17 10:43 ` [PATCH v7 2/8] sigval.3: Add link page Alejandro Colomar
2020-09-17 10:43 ` [PATCH v7 3/8] ssize_t.3: " Alejandro Colomar
2020-09-17 10:43 ` [PATCH v7 4/8] suseconds_t.3: " Alejandro Colomar
2020-09-17 10:43 ` [PATCH v7 5/8] time_t.3: " Alejandro Colomar
2020-09-17 10:43 ` [PATCH v7 6/8] timer_t.3: " Alejandro Colomar
2020-09-17 10:43 ` [PATCH v7 7/8] timespec.3: " Alejandro Colomar
2020-09-17 10:43 ` [PATCH v7 8/8] timeval.3: " 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=20200918021603.GA596604@thunder.hadrons.org \
--to=guillem@hadrons.org \
--cc=colomar.6.4.3@gmail.com \
--cc=fweimer@redhat.com \
--cc=libbsd@lists.freedesktop.org \
--cc=linux-man@vger.kernel.org \
--cc=mtk.manpages@gmail.com \
/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