Man page synopsis doesn't use the bin_name

[arusahni]

Please complete the following tasks

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

Rust Version

1.67.1

Clap Version

4.1.8

Minimal reproducible code

use clap::{arg, CommandFactory, Parser};
use clap::CommandFactory;
use clap_mangen::Man;

#[derive(Debug, Parser)]
#[command(
    bin_name = "myapp",
)]
struct Cli {
   #[arg(long)]
    list: bool
}

fn main() {
    let cmd = Cli::comand();
    let man = Man::new(cmd);
    let mut buffer: Vec<u8> = Default::default();
    man.render(&mut buffer)?;
    Ok(())
}

Steps to reproduce the bug with the above code

cargo run

Actual Behaviour

The generated manpage has a synopsis section that uses the Crate name for the sample invocation:

SYNOPSIS
       appname [--list]

Expected Behaviour

The generated manpage should have synopsis section that uses the provided bin_name for the sample invocation:

SYNOPSIS
       myapp [--list]

Additional Context

No response

Debug Output

No response

[epage]

Is there a reason you are setting bin_name and not name or display_name?

[arusahni]

Yes: I'm writing a git extension. By convention, git extensions are discovered by naming the binary git-<extension name>, but invoked as a git subcommand (git <extension name>). Ultimately, I'd like to reflect this nuance on the manpage, with the displayed name being git-<extension name>, but the synopsis showing git <extension name>.

name doesn't suit my need here because I don't want the subcommand variant displayed throughout the manpage, just places where an invocation example is provided. display_name does not currently impact the synopsis (my PR updates it to be considered, but with lower precedence than the bin_name).

[epage]

Thanks for the explanation!

I think its reasonable then for this to go forward if we can find a way to make this work out