argh
argh copied to clipboard
google
Rust derive-based argument parsing optimized for code size
It should be an error to have multiple options/switches with same short name. Currently it compiles without even a warning! E.g. if you have two options using the same short...
There are some changes to the library (as well as increasing usage!) and I'd like to prevent size regressions. We should check binary output on a slew of targets/configs on...
A convenient feature of clap is the support for [generating shell completion scripts](https://docs.rs/clap/2.33.0/clap/struct.App.html#method.gen_completions) from build.rs (i.e. during build of the application, thus without overhead on the application). I don't know...
It should be possible to use an `enum` as the possible value of an option, without wrapping it in an `Option` when and if the `enum` implements `Default`. Current example...
Currently the usage prints positional args in snake_case, e.g.: ``` Usage: D:\foo.exe [] [-t ] [] [] ``` It should also print positional args in kebab-case for consistency (`project-file` in...
Is there a way to specify that a positional arg need at least one value? ```rust #[derive(FromArgs)] /// MyCMD struct Opt { #[argh(positional)] /// script files to run test_file: Vec,...
Hello, I was working on a crate and found inconsistent newlines when argh prints help for a binary when using different forms of doc comments. When fields within a `FromArgs`...
If Argh is "optimized for code size", then it only makes sense to show a comparison with other existing parsers, similar to the chart in the README for [pico-args](https://lib.rs/crates/pico-args). (Though,...
Can it be used for implementing programs like `xargs` or `nice` where it is important to pass around command line unmodified, even if it contains invalid UTF-8?
While initially written for Fuchsia. this is a generally useful library. References could be confusing