clap_mangen does not write the arg information in the subcommand

[eatradish]

Please complete the following tasks

• I have searched the discussions
• I have searched the open and rejected issues

Rust Version

rustc 1.68.2 (9eb3afe9e 2023-03-27)

Clap Version

clap 4.2.1

Minimal reproducible code

fn main() -> std::io::Result<()> {
    let cmd = command_builder();

    let man = clap_mangen::Man::new(cmd);
    let mut buffer: Vec<u8> = Default::default();
    man.render(&mut buffer)?;

    let man_dir = std::path::PathBuf::from(
        std::env::var_os("CARGO_MANIFEST_DIR").ok_or(std::io::ErrorKind::NotFound)?,
    )
    .join("man");

    if !man_dir.is_dir() {
        std::fs::create_dir_all(&man_dir)?;
    }

    std::fs::write(man_dir.join("oma.1"), buffer)?;

    Ok(())
}

fn command_builder() {
command!()
        .subcommand(
            Command::new("install")
                .about("Install Package")
                .arg(&pkgs)
                .arg(
                    Arg::new("install_dbg")
                        .alias("dbg")
                        .long("install-dbg")
                        .help("Install package(s) debug symbol")
                        .requires("packages")
                        .action(ArgAction::SetTrue)
                )
                .arg(
                    Arg::new("reinstall")
                        .long("reinstall")
                        .help("Reinstall package(s)")
                        .requires("packages")
                        .action(ArgAction::SetTrue),
                )
        )
}

Steps to reproduce the bug with the above code

1. cargo build --release
2. Check SRCDIR/man/oma.1 file
3. See result, like:

...
SUBCOMMANDS
       oma-install(1)
              Install Package

       oma-upgrade(1)
              Update Package

...

Does not have argument help information.

Actual Behaviour

No information is written to the argment in the subcommand

Expected Behaviour

written to the argment in the subcommand

Additional Context

No response

Debug Output

No response

[epage]

No information is written to the argment in the subcommand

What do you mean by "argument help information"?

Are you expecting the one manpage to service all subcommands? Currently, we only support generating man pages for the model where the is one man page per subcommand.

See also

• Unclear how to handle subcommands with clap_man #3365
• Display help for all subcommands at the same time #1334

[eatradish]

Looks like your advice solved my problem, thanks!