Program option taking multiple values with subcommands

[lazytiger]

What should I do if I want something like this?

./program --optiona-general xxx subcommand --option-for-subcommand yy

[lazytiger]

I am using clap derive, and I do not find anything about global setting, I think that's what I am looking for.

[CreepySkeleton]

Aghm... I'm not sure I really understand what you mean, but something like this will work as you requested:

use clap::{Clap, Subcommand};

#[derive(Clap)]
struct Opt {
    #[clap(long)]
    option_general: String,
 
    #[clap(subcommand)]
    sub: Subcommands
}

#[derive(Subcommand)]
enum Subcommands {
    Subcommand {
        #[clap(long)]
        option_for_subcommand: String
    }
}

[lazytiger]

Yes, that's what I have done, but the result is frustrated.
./program --option-general xxx subcommand ---option-for-subcommand -> wrong
./program subcommand --option-general xxx --option-for-subcommand yyy -> wrong
I know there is a method for Arg called global, and I don't find anywhere set that in derive.

I think this may be some bug for 3.0, I use App in 2.33 to build my options, it's all ok

[CreepySkeleton]

Phfff... OK, Could you please give me a detailed explanation of what you want, like

• --option-general must be usable on top level, but not with subcommand.
• --option-sub must me usable with subcommand, but not at the top level.

Something like that. I'm having really hard time struggling with your description. If you want others to get to understanding your problem, you need to explain what is expected, in detail, step by step, comprehensive.

I know there is a method for Arg called global, and I don't find anywhere set that in derive.

If this is what you want, use #[clap(global = true)]. I don't see how this could help you though.

[lazytiger]

I have figured it out. I defined Vec type in my struct, all that's all the mess is. When I remove it from Opt, everything is fine. Could this be a bug?

[CreepySkeleton]

I defined Vec type in my struct, all that's all the mess is

Could you please post the whole snippet?

[lazytiger]

use clap::Clap;


#[derive(Clap)]
struct Opts {
    #[clap(long)]
    option_general: String,

    #[clap(subcommand)]
    sub: Subcommands,

    #[clap(long, required = true)]
    files: Vec<String>,
}

#[derive(Clap)]
enum Subcommands {
    Subcommand {
        #[clap(long)]
        option_for_subcommand: String
    }
}

fn main() {
    let opt = Opts::parse();
}

Please test this code, it will fail

[CreepySkeleton]

$ cargo run -- --option-general fuuu --files file1 file2 subcommand --option-for-subcommand argh
    Finished dev [unoptimized + debuginfo] target(s) in 0.19s
     Running `target\debug\lucid.exe --option-general fuuu --files file1 file2 subcommand --option-for-subcommand argh`
error: Found argument '--option-for-subcommand' which wasn't expected, or isn't valid in this context
If you tried to supply `--option-for-subcommand` as a PATTERN use `-- --option-for-subcommand`

USAGE:
    lucid.exe --option-general <option-general> --files <files>... <SUBCOMMAND>

For more information try --help
error: process didn't exit successfully: `target\debug\lucid.exe --option-general fuuu --files file1 file2 subcommand --option-for-subcommand argh` (exit code: 2)

$ cargo run -- --files file1 file2 --option-general fuu subcommand --option-for-subcommand argh
   Compiling lucid v0.2.0 (D:\workspace\probe)
    Finished dev [unoptimized + debuginfo] target(s) in 2.44s
     Running `target\debug\lucid.exe --files file1 file2 --option-general fuu subcommand --option-for-subcommand argh`
Opts {
    option_general: "fuu",
    sub: Subcommand {
        option_for_subcommand: "argh",
    },
    files: [
        "file1",
        "file2",
    ],
}

Well, this is kind of expected. If you have an option taking multiple values followed by a subcommand, there's no way to detect where the values end and where the subcommand starts. So, use the second variant and not the first one.

I'm closing this until you post a clear comprehensive explanation of what behavior you expect.