I think I might have found a bug in clap_complete

[nicole-jf]

when generating completions with multiple possible long arguments it seems like clap_complete generates invalid fish completions

I haven't made a minimum reproducible case yet, but I plan on

in short, clap_complete generates the following line:

complete -c rtag -n "__fish_rtag_using_subcommand get" -s 0 -l print0 null

which is wrong, it should be:

complete -c rtag -n "__fish_rtag_using_subcommand get" -s 0 -l print0 -l null

I am using derive to build my cli and relevant parts of cli struct are:

// [...] Importing clap
#[derive(Parser)]
#[command(name = "rtag",
    version, about, long_about = None)]
pub(crate) struct Cli {
    #[command(subcommand)]
    pub(crate) command: Option<Commands>,
}
#[derive(Subcommand)]
pub(crate) enum Commands {
    Get {
        #[arg(short = '0', long = "print0, null")]
        nullprint: bool,
        #[arg(value_name = "FILES", required = true)]
        paths: Vec<PathBuf>,
    },
// [...] other subcommands
}

[nicole-jf]

I figured out what is going on, long = "print0, null" sets one long flag --print0, null and not 2, my bad

for anyone having this same issue
just change this
#[arg(short = '0', long = "print0, null")]
to
#[arg(short = '0', long = "print0", alias = "null")]