Multiple commands declared at the same level are parsed and executed in sequence

[mknejp]

When one defines multiple commands at the same level

cli.add_argument(
  lyra::command("foo", [&](lyra::group const& g) { fmt::println("running foo"); })
);
cli.add_argument(
  lyra::command("bar", [&](lyra::group const& g) { fmt::println("running bar"); })
);

Then the following invocation exec foo bar prints

running foo
running bar

I think the expectation here is that only one command is recognized and the other rejected as a syntax error.

Note that this differs from nesting commands like this

cli.add_argument(
  lyra::command("foo", [&](lyra::group const& g) { fmt::println("running foo"); })
    .add_argument(
      lyra::command("bar", [&](lyra::group const& g) { fmt::println("running bar"); })
    )
);

Which when invoked with exec foo bar prints

running bar
running foo

And works as expected.

[akoutian]

I second this. I have not yet seen any command line tool that allows multiple subcommands to be executed. Usually it's just one, and any following ones are discarded. Common examples are conan, cryptsetup and cargo.

[jpyllman]

I do not know what the best solution is. I know to little of the parser. But I guess just having a 'global' flag to tell you not to allow more then one command.

[jpyllman]

Another thing. Does the parser know to group the command specific options. So options does not spill over between the commands?