Hi Branden,

On Fri, May 02, 2025 at 09:19:48AM -0500, G. Branden Robinson wrote:

Hi Alex,

At 2025-05-02T14:26:23+0200, Alejandro Colomar wrote:

quoted

On Fri, May 02, 2025 at 07:01:39AM -0500, G. Branden Robinson wrote:

quoted

[2] $ type mailman
mailman is a function
mailman ()
{
    local cmd=;
    case "$1" in
        -*)
            opts="$opts $1";
            shift
        ;;
    esac;
    set -- $(man -w "$@");
    cmd=$(zcat --force "$@" | grog -Tutf8 -b -ww -P -cbou -rU0 -rLL=72n -rHY=0 -dAD=l $opts);
    zcat --force "$@" | $cmd | less
}

I was trying to simplify your mailman() function to the following pipe
(after parsing the options):

	man -w "$@" \
	| xargs zcat --force \
	| grog --run \
		-Tutf8 -b -ww -P -cbou -rU0 -rLL=72n -rHY=0 -dAD=l \
		$opts \
		2>/dev/null \
	| less;

And I found out that grog(1) seems to be not accepting a documented
option: --run. [1]  Am I doing something incorrectly?  I never used
grog(1) before, so it might very well be.

Your grog executable may be out of sync with the man page you're
reading.

Compare `type grog` with `man -w grog`.

Hmmmm.

alx@devuan:~$ which grog
/usr/local/bin/grog
alx@devuan:~$ grog --version
GNU grog (groff) 1.23.0.2695-49927
alx@devuan:~$ man grog | tail -n1
groff 1.23.0                    26 December 2024                        grog(1)

quoted

alx@devuan:~$ grog --run
grog: error: unrecognized grog option '--run'; ignored

grog's `--run` option has been removed in the forthcoming groff 1.24.0
release, so if you're running groff Git's master branch, that could
explain it.

NEWS:

*  grog(1) no longer supports the `--ligatures` and `--run` options.
   Simulate the former (which was specific to the "pdf" output device)
   with the option sequence "-P -U -P y", and the latter by using the
   command substitution feature of your shell; see section "Examples" of
   groff(1).

Okay, this complicates things a bit.  :)


Cheers,
Alex

Regards,
Branden

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