From: Kristaps Dzonsons <kristaps@bsd.lv>
To: tech@mdocml.bsd.lv
Subject: mandocdb(8) issues when locating source manuals
Date: Wed, 07 Dec 2011 12:43:11 +0100 [thread overview]
Message-ID: <4EDF514F.7080704@bsd.lv> (raw)
Hi,
Another bug flushed out by man.cgi: some architecture-specific manuals
refer to the catman file instead of the source file.
Example follows below, where apropos.c is modified to show the type of
the located record. Notice that all archs use the cat page except i386
(??).
Ideas?
Kristaps
% ./apropos 'Nm~^intro$'
intro(4/alpha) - introduction to special files and hardware support (cat)
intro(4/i386) - introduction to special files and hardware support (mdoc)
intro(4/landisk) - introduction to special files and hardware support (cat)
intro(4/sgi) - introduction to special files and hardware support (cat)
intro(4/loongson) - introduction to special files and hardware support (cat)
intro(4/luna88k) - introduction to special files and hardware support (cat)
intro(4/mac68k) - introduction to special files and hardware support (cat)
intro(1) - introduction to general commands (tools and utilities) (mdoc)
intro(4/macppc) - introduction to special files and hardware support (cat)
intro(4/amd64) - introduction to special files and hardware support (cat)
intro(3) - introduction to the C libraries (mdoc)
intro(4/hp300) - introduction to special files and hardware support (cat)
intro(4/vax) - introduction to special files and hardware support (cat)
intro(4/sparc64) - introduction to special files and hardware support (cat)
intro(4/socppc) - introduction to special files and hardware support (cat)
intro(4/zaurus) - introduction to special files and hardware support (cat)
intro(4/sparc) - introduction to special files and hardware support (cat)
intro(2) - introduction to system calls and error numbers (mdoc)
intro(4/mvme68k) - introduction to special files and hardware support (cat)
intro(4/mvme88k) - introduction to special files and hardware support (cat)
intro(9) - introduction to the kernel internals (mdoc)
intro(4/i386) - introduction to special files and hardware support (cat)
intro(4/armish) - introduction to special files and hardware support (cat)
intro(4/hppa) - introduction to special files and hardware support (cat)
intro(7) - miscellaneous information pages (mdoc)
intro(8) - introduction to system maintenance and operation commands (mdoc)
intro(6) - introduction to the games (mdoc)
intro(5) - introduction to file formats (mdoc)
intro(4/aviion) - introduction to special files and hardware support (cat)
--
To unsubscribe send an email to tech+unsubscribe@mdocml.bsd.lv
reply other threads:[~2011-12-07 11:43 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4EDF514F.7080704@bsd.lv \
--to=kristaps@bsd.lv \
--cc=tech@mdocml.bsd.lv \
/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 NNTP newsgroup(s).