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: Sun, 3 Oct 2021 19:16:30 -0400 [thread overview]
Message-ID: <20211003231630.mb65kbrsb4cpb4yn@FreeBSDY540> (raw)
In-Reply-To: <YVn7L0m60z2NylGt@asta-kit.de>
[-- Attachment #1: Type: text/plain, Size: 1093 bytes --]
On Sun, Oct 03, 2021 at 08:49:19PM +0200, Ingo Schwarze wrote:
> Hi Cameron,
>
> Cameron Katri wrote on Sun, Oct 03, 2021 at 01:49:18PM -0400:
>
> > I want to add the ability to specify the man section name
>
> I suspect you are talking about the volume titles (for example,
> "General Commands Manual", "System Calls Manual", etc.), not about
> section names (for example, "SYNOPSIS", "DESCRIPTION", "SEE ALSO", etc.).
Yes.
> > at runtime, instead of at compile time in msec.in.
>
> Why?
>
> What is the use case requiring that?
Well this is a very niche use case, but on FreeBSD they patch msec.in to
say "FreeBSD General Commands Manual" etc. which means that when I use
mandoc -T html to generate my website I have to use a different build of
mandoc so that the volume title just says "Miscellaneous Information Manual"
instead of "FreeBSD Miscellaneous Information Manual."
>
> Yours,
> Ingo
Thanks for the feedback.
- Cameron Katri
--
Cameron Katri
Email: me@cameronkatri.com
PGP Fingerprint: 7D3B36CEA40FCC2181FB6DCDBAFFD97826540F1C
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2021-10-03 23:16 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 [this message]
2021-10-04 8:06 ` Ingo Schwarze
2021-10-04 18:07 ` Cameron Katri
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=20211003231630.mb65kbrsb4cpb4yn@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).