Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Value terminator is not included anywhere in help message #4812

Open
2 tasks done
epbuennig opened this issue Mar 30, 2023 · 5 comments
Open
2 tasks done

Value terminator is not included anywhere in help message #4812

epbuennig opened this issue Mar 30, 2023 · 5 comments
Labels
A-help Area: documentation, including docs.rs, readme, examples, etc... C-enhancement Category: Raise on the bar on expectations E-easy Call for participation: Experience needed to fix: Easy / not much

Comments

@epbuennig
Copy link

epbuennig commented Mar 30, 2023

Please complete the following tasks

Clap Version

v4.2.0

Describe your use case

The following rust program:

use clap::{Command, Arg};

Command::new("cmd")
    .arg(Arg::new("multiple_options").num_args(0..).value_terminator(":"))
    .arg(Arg::new("last").required(false))
    .get_matches_from(["cmd", "-h"]);

currently produces this output:

Usage: cmd [multiple_options]... [last]

Arguments:
  [multiple_options]...  
  [last]                 

Options:
  -h, --help  Print help

For a user, it is not clear that the options before last must be delimited with : so the last argument is not assumed to be part of multiple_options.

Ideally, it should be included in both the usage itself and the Argument list in some way, mentioning it in the help message for each argument which may use this style would become tedious.

Describe the solution you'd like

I would expect the program to output something similar to this:

Usage: cmd [<multiple_options>... :] [last]

Arguments:
  [<multiple_options>... :]  
  [last]                 

Options:
  -h, --help  Print help

without any additional changes by default.

Alternatives, if applicable

An alternative to this is specifying the usage directly, but this falls flat as soon as a is turned into an option, as it's representation in the option list cannot be changed.

It could also be explained in the help message of the argument itself, but I feel like the automatically generated usage strings should include this.

Additional Context

The following program already produces includes the -- token for arguments specified as required(false) and last(true) (although only in the usage), which is why I believe my feature request falls inline with the current design philosophy of clap.

use clap::{Command, Arg};

fn main() {
    Command::new("cmd")
        .arg(Arg::new("multiple_options").num_args(1..))
        .arg(Arg::new("last").required(false).last(true))
        .get_matches_from(["cmd", "-h"]);
}
Usage: cmd [multiple_options]... [-- <last>]

Arguments:
  [multiple_options]...  
  [last]                 

Options:
  -h, --help  Print help
@epbuennig epbuennig added the C-enhancement Category: Raise on the bar on expectations label Mar 30, 2023
@epage epage added A-help Area: documentation, including docs.rs, readme, examples, etc... E-easy Call for participation: Experience needed to fix: Easy / not much labels Mar 30, 2023
@epage
Copy link
Member

epage commented Mar 30, 2023

I think your idea for having it in the argument list and in the usage like that works. My only concern is how much this increases the binary size as this is a less commonly used feature and users can provide custom usages. I'm open to at least an experimental implementation being made for us to evaluate.

@epbuennig
Copy link
Author

My main concern is that, if this is on one or multiple options instead of positional arguments, then trying to do it with a custom usage won't work quite so well. We can't currently overwrite the usage that is displayed in the Argument/Options list.

@toddATavail
Copy link

I like this proposal, @epbuennig; I've used the underlying feature of Clap before, and it would definitely be nice if the help generator would show you the stop delimiter without the developer having to write a custom usage message. I'm generally for anything that quickly improves documentation quality and usability, and this feels like an easy win. I'm busy tonight, but I have some dedicated time tomorrow to work on this. I'll see what it does to binary size (seems like it should be a small positive delta?), and then we can see if your team likes it, @epage.

@toddATavail
Copy link

Okay, my PR is in. Ended up thrashing against the CI for a bit, so sorry if that generated any annoying transient noise. Looks like CI is happy now, and all tests (including the 3 that I added to test this small feature) are passing. I only checked the binary delta on my M2, and it was negligible. I've used Clap for years, and this was a fun way to give something (admittedly small) back on a quiet evening. Thanks for the great tool!

@Aethelflaed
Copy link

I'm keen on working on that, what's the desired solution in the end?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-help Area: documentation, including docs.rs, readme, examples, etc... C-enhancement Category: Raise on the bar on expectations E-easy Call for participation: Experience needed to fix: Easy / not much
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants