Program name (bin_name) should be configurable

[DanielKeep]

The first line of the --help message for my program is as follows:

cargo-script.exe-script 0.1.1

The obvious issue is that this is hideously ugly, and also misleading. I'm writing a Cargo subcommand and, as such, the user is never going to invoke this program as "cargo-script". I need to tell clap that the program should identify itself as "cargo". Ideally, I'd be able to tell it to lie when using the "script" subcommand, but not when it isn't provided.

I thought about just altering the arguments clap is parsing, but there doesn't appear to be any way to do this.

Also, it would help to not have the file extension present in the name.

[kbknapp]

This shouldn't be too hard, let me play with an implementation idea and I'll post back here. Thanks for taking the time to file this!

[DanielKeep]

No problem. If it's of any use, the code in question is in cargo-script/v0.1.1.

[kbknapp]

Thanks! I was just about to ask. So ideally, you'd like to be able to say the bin_name of the parent command is cargo and you've got a subcommand of script which in the help/version should be dispalyed as:

$ cargo script -v
cargo-script v1.0

But in usage strings should be displayed as:

USAGE:
    cargo script <script>

Correct?

If that's the case I should have this working in about 10 minutes ;)

[DanielKeep]

Pretty much, yeah. So long as it doesn't call itself cargo-script-script or cargo.exe script, it's all good. :)

[kbknapp]

Aright, I've got it working tested with this scenario. Uploading now, use 0.10.2 on crates.io
The relevant piece for you is on the App struct set the .bin_name("cargo") which allows you to override the system determined binary name with whatever you want. You could also use cargo.exe if you prefer, it could be anything.

[kbknapp]

It's up on crates.io now, you can also use the master branch here.

off topic, cargo script looks awesome! I'm going to have to keep an eye on this!

[DanielKeep]

Thanks; updated.