Using binary name as the command?

[jaskij]

It's not unusual to have a single binary linked under various names and executing different code depending on it. Probably the most prominent example is busybox.

In other words, the first (top-level) command would be parsed from Path(argv[0]).file_stem().

It is entirely possible to do it manually, like the example below, but it would be very nice to have this kind of capability built into Clap.

match Path(env::args().next().unwrap().as_str()).file_stem() {
    "cmd" => run_cmd(),
    "foo" => run_foo(),
    "bar" => run_bar(),
    _ => return Err("unknown command"),
}

[jaskij]

Thinking on it a bit further, there might be differences based on the OS: for Linux it could be file_name(), where Windows would want file_stem(), and I'm not sure about MacOS. A detail that will need hashing out if this idea is accepted.

[epage]

See Command::multicall along with the hostname and busybox examples in the cookbook.

[jaskij]

Thank you, somehow my search did not turn that up.

I'm guessing that it can be used with the derive API using raw attributes?

[epage]

Yes, all settings work as raw attributes. We try to have all cookbook examples using both APIs but some of these haven't been done yet.