how to parse mv <files>... <target>?

[hh9527]

E.g.: mv a1 a2 a3/

I use the code like this:

let m = App::new()
  .arg(Arg::with_name("files").required(true).multiple(true))
  .arg(Arg::with_name("target").required(true))
  .get_matches();

When input mv a1 a2 a3/, I expect result like this:

{
  files: ["a1", "a2"],
  target: "a3",
}

But I got a error:

error: The following required arguments were not provided:
    <target>

[kbknapp]

This is because there's no way to know when <files> ends and <target> starts. Positional arguments that take multiple values must be the last positional argument.

There are two ways to fix this, either swap the arguments (i.e. <target> <files>...) or limit the number of values to a fixed number (i.e. <file> <file> <target>). Obviously one of those solutions is less viable than the other (fixed number of files), but it's still an option.

Hope this helps! I'm also open to suggestions 😉

[kbknapp]

Also, thinking about this a little more, there may be a way I could add this feature. Let me play with some implementations and get back with you!

[kbknapp]

I found a way to make this work, after #727 merges I'll upload v2.17.0 to crates.io

At which point this will give the expected results:

let m = App::new()
  .arg(Arg::with_name("files").required(true).multiple(true))
  .arg(Arg::with_name("target").required(true))
  .get_matches();

[kbknapp]

@hh9527 v2.17.0 is up on crates.io now

[hh9527]

waooo, it is so nice of you! thank you for this great project!

[hh9527]

@kbknapp I have tried v2.17.0, it works without subcommand, but still break in subcommand.

This works:

    let m = App::new("mv")
        .arg(Arg::with_name("paths").required(true).multiple(true))
        .arg(Arg::with_name("target").required(true))
        .get_matches();

And this not:

    let m = App::new("cli")
        .subcommand(
            SubCommand::with_name("mv")
                .arg(Arg::with_name("paths").required(true).multiple(true))
                .arg(Arg::with_name("target").required(true))
        ).get_matches();

[kbknapp]

Ah, thanks for pointing this out, I hadn't testsed it after a subcommand, only before!

[kbknapp]

It's fixed in #730 😉

[kbknapp]

v2.17.1 is up now!