From: Cameron Katri <me@cameronkatri.com>
To: Ingo Schwarze <schwarze@usta.de>
Cc: discuss@mandoc.bsd.lv
Subject: Re: Specify man section name at runtime
Date: Mon, 4 Oct 2021 14:07:15 -0400 [thread overview]
Message-ID: <20211004180715.yhztmn455f77s25r@FreeBSDY540> (raw)
In-Reply-To: <YVq2I0bI8dYoNPWk@asta-kit.de>
[-- Attachment #1: Type: text/plain, Size: 1472 bytes --]
On Mon, Oct 04, 2021 at 10:06:59AM +0200, Ingo Schwarze wrote:
> Hi Cameron,
>
> Cameron Katri wrote on Sun, Oct 03, 2021 at 07:16:30PM -0400:
>
> > Well this is a very niche use case, but on FreeBSD they patch msec.in
> > to say "FreeBSD General Commands Manual" etc.
>
> I think that patching is ill-advised. In manual pages, the operating
> system name is supposed to be printed in the footer line (lower left
> corner), not in the header line. One consequence of the FreeBSD
> patching is that if you format manual pages of another operating system
> on FreeBSD, the header line will always include the misleading string
> "FreeBSD" anyway, and as you observed, there is no way to tell mandoc
> to leave it out.
>
> The string in the footer line, on the other hand, defaults to uname(3),
> which already includes "FreeBSD" by default, and can be overridden
> both by the "-I os=" option on the command line and by the .Os macro
> in the manual page.
>
> The file msec.in does not exist for the purpose of branding that
> FreeBSD abuses it for, but to accomodate differing volume conventions
> of operating systems. For example, illumos has traditionally been
> using the System V convention that includes
>
I will try and get this patch removed from FreeBSD, which I agree is a
much better solution.
- Cameron Katri
--
Cameron Katri
Email: me@cameronkatri.com
PGP Fingerprint: 7D3B36CEA40FCC2181FB6DCDBAFFD97826540F1C
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2021-10-04 18:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-03 17:49 Cameron Katri
2021-10-03 18:40 ` Jan Stary
2021-10-03 18:49 ` Ingo Schwarze
2021-10-03 23:16 ` Cameron Katri
2021-10-04 8:06 ` Ingo Schwarze
2021-10-04 18:07 ` Cameron Katri [this message]
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=20211004180715.yhztmn455f77s25r@FreeBSDY540 \
--to=me@cameronkatri.com \
--cc=discuss@mandoc.bsd.lv \
--cc=schwarze@usta.de \
/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).