Linux-man Archive mirror
 help / color / mirror / Atom feed
From: Guillem Jover <guillem@hadrons.org>
To: Alejandro Colomar <alx@kernel.org>
Cc: linux-man@vger.kernel.org
Subject: Order priority issues for special 3type sub-section
Date: Thu, 7 Mar 2024 00:22:58 +0100	[thread overview]
Message-ID: <Zej60rSb9Ve5rRPy@thunder.hadrons.org> (raw)

Hi!

I just realized the other day that we have currently a problem with
the order priority for a couple of the manual pages in (at least) the
3type sub-section. These pages have been provided by libbsd in the
3bsd sub-section for some time, and that sorts earlier than 3type.
This has not been a problem for the section 3 pages, as then those
will always be preferred if present over the 3bsd ones. This also
means I might be reluctant to add new 3bsd manual pages related to
types, to avoid future occlusions.

I think this only affects timeval.3* and timespec.3*. But I'm not
sure how best this would be solved though. :/ Hmm perhaps thinking
about it, I could rewrite these manual pages and only provide them
for the TIMEVAL_TO_TIMESPEC and TIMESPEC_TO_TIMEVAL macros.

But perhaps this is a more general problem as «t» sorts pretty late,
for example later than «3cxx», «3ncurses», «3perl», «3pm», «3p» or
«3posix». And ah, now I recalled the SECTION option in man-db, which
on my system already lists 3type before many others, but I guess the
problem is still that unlisted sub-sections get folded into their
parent section, so perhaps some of these need to be proposed for
addition there. Not sure about other man pagers though.

(BTW, I very much like that these types are provided on their own
manual pages, and their own sub-section, thanks for that!)

Thanks,
Guillem

             reply	other threads:[~2024-03-06 23:30 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-06 23:22 Guillem Jover [this message]
2024-03-07  0:42 ` Order priority issues for special 3type sub-section Alejandro Colomar
2024-03-07  1:08   ` Oskari Pirhonen
2024-03-07  2:05     ` Alejandro Colomar
2024-03-07  2:09     ` Mail-Followup-To header (was: Order priority issues for special 3type sub-section) Alejandro Colomar
2024-03-07  9:37       ` Lennart Jablonka
2024-03-07 10:37         ` Alejandro Colomar
2024-03-07  4:06   ` Order priority issues for special 3type sub-section Guillem Jover
2024-03-07 10:24     ` Alejandro Colomar
2024-03-20  9:18     ` Guillem Jover
2024-03-20 10:07       ` 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=Zej60rSb9Ve5rRPy@thunder.hadrons.org \
    --to=guillem@hadrons.org \
    --cc=alx@kernel.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).