Man page section for complete's -C option is inconsistent

[Mark Chandler]

Configuration Information [Automatically generated, do not change]:
Machine: x86_64
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS: -O2 -flto=auto -ffat-lto-objects -fexceptions -g 
-grecord-gcc-switches -pipe -Wall -Werror=format-security 
-Wp,-D_FORTIFY_SOURCE=2 -Wp,-D_GLIBCXX_ASSERTIONS 
-specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong 
-specs=/usr/lib/rpm/redhat/redhat-annobin-cc1  -m64 -mtune=generic 
-fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection
uname output: Linux ice-mef 5.18.7-200.fc36.x86_64 #1 SMP 
PREEMPT_DYNAMIC Sat Jun 25 20:06:14 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
Machine Type: x86_64-redhat-linux-gnu

Bash Version: 5.1
Patch Level: 16
Release Status: release

Description:
        Even though the -C option of "complete" is functionally very 
similar to -F, the man page
        only provides detailed usage for -F. The -C description doesn't 
mention parameter passing.

Repeat-By:
        man bash
        read the section under BUILT-IN COMMANDS for the -C option of 
"complete"

Fix:
        Expand the -C option text to be similar to -F, or put a 
reference to the -F description
        to explain how the parameter passing works.
        E.g.
        The shell command *command* is executed in a subshell 
environment. When it is executed,
        $1 is the name of the command whose arguments are being 
completed, $2 is the word being completed,
        and $3 is the word preceding the word being completed, as 
described above (see Programmable
        Completion). When it finishes, its output is used as the 
possible completions.

        Or
        command is executed in a subshell environment, and its output 
is used as the possible completions.
        See -F below for a description of how parameters are passed to 
the command.