pico-args
cli-guidelines
pico-args | cli-guidelines | |
---|---|---|
11 | 47 | |
547 | 2,788 | |
- | 0.9% | |
3.0 | 3.6 | |
7 months ago | about 1 month ago | |
Rust | CSS | |
MIT License | Creative Commons Attribution Share Alike 4.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
pico-args
- Improving build times for derive macros by 3x or more
-
Need a new args parser
That's because the maintainer does not consider it an issue but an implementation detail: https://github.com/RazrFalcon/pico-args/issues/15
-
An alternative to clap but with a stable API?
Maybe pico-args then?
-
Immediately off the top of your head what is the best Rust CLI library.
If I forget to get around to it, would you mind poking RazrFalcon/pico-args about adding it to the comparison chart? I really like using that thing as something I can link people to with just a quick explanation of that particular trade-off.
-
Best CLI arg parser for use in Rust to port from Perl with Getopt::Long?
If fewer dependencies is better, you can't get much fewer than pico-args, which has zero dependencies.
- What is the current proper way to get command line args ?
-
Creating an Argparse library [feedback would be appreciated]
You might also want to check out pico-args, Gumdrop, and lexopt to see if any of them meet your needs.
-
Can we please stop downvoting people who dislike Rust?
For example, The Rust compiler isn't slow; we are. and pico-args: Alternatives.
- pico-args: An ultra simple CLI arguments parser with 0 dependencies
-
New:`cargo-fuzzcheck` 0.5.0 and a series of decent, fast-to-compile crates to replace `syn`, `quote`, `serde-json`, and `toml-rs`
For example, I'd love to go from StructOpt to Gumdrop for parsing command-line arguments and cut my compile times and output size by an order of magnitude, but Gumdrop uses String internally, which means it'll panic if it encounters a Windows path with un-paired surrogates or a mojibake'd posix path... some of which I actually have.
cli-guidelines
- Ask HN: Where to read about terminal UIs?
-
Ask HN: Do you read Secrets from Environment Variables
The Command Line Interface Guidelines [1] says:
> Do not read secrets from environment variables
> Secrets should only be accepted via credential files, pipes, `AF_UNIX` sockets, secret management services, or another IPC mechanism
Which one of these do you use? On github it seems common for projects to use environment variables for secrets.
[1] https://clig.dev/#environment-variables
-
Command Line Interface Guidelines
Seems they took a small step back from their previous "don't bother with man pages" stance. Now it's "Consider providing man pages."
I still find it a rather shocking order of priority, honestly.
https://clig.dev/#documentation
-
Ask HN: Best way to do scoped commands in a CLI app
- E. `blah project foo --edit`
Wondering if there was any guidance on this from the UNIX people. Perhaps scoping should be done using the file system. `cd path/to/project && blah edit`. Like git does with `git --cwd=path/to/project`. Maybe a virtual FS could even be used. Then you wouldn't have to continuously type in the scope with each command. Interesting thinking about how to maintain state in the terminal...thinking about how Python's virtual env bin/activate modifies the shell.
Found an interesting guide here: https://clig.dev/
-
CLI user experience case study
Capturing these guidelines is one of the primary reasons that https://clig.dev/ exists.
-
Introducing my Password Manager project - Seeking Feedback and Contributions
You may want to take a look at various existing CLIs to get inspiration on how they operate, the user feedback loop and the ergonomics on using them. Here is a great website on some CLI structing guidance https://clig.dev/
What are some alternatives?
lexopt - Minimalist pedantic command line parser
redox - Mirror of https://gitlab.redox-os.org/redox-os/redox
xflags
nodejs-cli-apps-best-practices - The largest Node.js CLI Apps best practices list ✨
command-line-rust - Code for Command-Line Rust (O'Reilly, 2022, ISBN 9781098109417) https://learning.oreilly.com/library/view/command-line-rust/9781098109424/
bubblewrap - Low-level unprivileged sandboxing tool used by Flatpak and similar projects
thiserror - derive(Error) for struct and enum error types
typer - Typer, build great CLIs. Easy to code. Based on Python type hints.
argh - Rust derive-based argument parsing optimized for code size
argparse-benchmarks-rs - Collected benchmarks for arg parsing crates written in Rust [Moved to: https://github.com/rosetta-rs/argparse-rosetta-rs]
rust - Rust for the xtensa architecture. Built in targets for the ESP32 and ESP8266
picocli - Picocli is a modern framework for building powerful, user-friendly, GraalVM-enabled command line apps with ease. It supports colors, autocompletion, subcommands, and more. In 1 source file so apps can include as source & avoid adding a dependency. Written in Java, usable from Groovy, Kotlin, Scala, etc.