Hi Seth,

On 2026-01-29T05:50:26+0000, Seth McDonald wrote:
> Hi Alex,
> 
> On Wed, 28 Jan 2026 at 19:55:43 +0100, Alejandro Colomar wrote:
> [...]
> > +.SH PARAMETERS
> > +See
> > +.BR mansect (1).
> 
> (If this isn't a problem then feel free to skip this)
> 
> AFAICT, 'PARAMETERS' isn't a heading used anywhere else.  Running
> 
> 	~/Code/Linux/man-pages$ grep -Fnr 'PARAMETERS' man/
> 
> comes up empty for me (besides mansectf(1) of course).  Perhaps instead
> the DESCRIPTION can explicitly state this.  Something akin to "This
> command uses the same interface as mansect(1)."
> 
> [...]
> > +#!/bin/bash
> > +#
> > +# Copyright, the authors of the Linux man-pages project
> > +# SPDX-License-Identifier: GPL-3.0-or-later
> > +
> > +set -Eefuo pipefail;
> > +
> > +mansect "$@" \
> > +| man /dev/stdin;
> 
> Thinking about it, one thing I did like from v1 that would be nice to
> keep is the specified sections being case-insensitive.  Since the
> section headers should always be in uppercase,

This is not necessarily true, and in fact I plan to change that
eventually.

The reason I haven't done that yet is that I'm wondering what would be
the best way to refer to sections in running text.  Currently, we refer
to them by name, and the fact that the name is upper-case makes it
obvious.

Still, if you want case insensitivity, since the section is a PCRE2
pattern, you could use '(?i)' (see pcre2pattern(3)):

	$ man -w snprintf | MANWIDTH=64 xargs mansectf '(?i)name' | cat
	snprintf(3)         Library Functions Manual        snprintf(3)

	NAME
	     snprintf, vsnprintf - string print formatted

	Linux man‐pages 6.16‐43... 2025‐12‐07               snprintf(3)


Have a lovely day!
Alex

> specifying them in
> lowercase when invoking mansectf(1) shouldn't introduce any ambiguity
> (i.e. "Does the user want the 'NAME' or 'Name' section?").
> 
> -- 
> Take care,
> 	Seth McDonald.
> 
> On-list:  2336 E8D2 FEB1 5300 692C  62A9 5839 6AD8 9243 D369
> Off-list: 82B9 620E 53D0 A1AE 2D69  6111 C267 B002 0A90 0289



-- 
<https://www.alejandro-colomar.es>