bpaf
cli-guidelines
| bpaf | cli-guidelines | |
|---|---|---|
| 21 | 47 | |
| 315 | 2,788 | |
| - | 0.9% | |
| 9.1 | 3.6 | |
| 6 days ago | about 1 month ago | |
| Rust | CSS | |
| - | 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.
bpaf
- bpaf – Command line parser with applicative interface
-
Crate to print tables in CLI in a lazy fashion?
If you want to make smart decisions depending on widths of the cells - you have to consume the whole iterator to see what is the widest cell out there, it could be the last one for example. During that iteration you'll want either to store the values somehow or store preformatted bits in a string - something like this https://github.com/pacak/bpaf/blob/master/src/buffer.rs
- The Icculus Microgrant is giving out 250 dollar grants to open source projects, please brag about your project(s) in this thread so I can see them!
-
Announcing clap-markdown — automatically generate Markdown docs for clap command-line tools
bpaf does it here, giving access to primitives like "dump names of this parser" or "dump help for this subparser": https://github.com/pacak/bpaf/blob/semantic/src/docugen.rs
-
Branching based on the return type of a function/closure argument
https://github.com/pacak/bpaf/blob/master/src/from_os_str.rs - a concrete example
- cargo + dynamic shell completion = cauwugo
-
Yet another command line argument parser: bpaf 0.6.0
https://github.com/pacak/bpaf/issues/50 - I would appreciate some feedback from a new user on naming conventions used - there or here is fine.
-
Design comparison of clap and bpaf (arg parsers)
Most of the code change is here: https://github.com/pacak/bpaf/pull/57 https://github.com/pacak/bpaf/pull/60
-
Yet another command line argument parser: bpaf 0.5.5
Something like this, handles example from the ticket at least (sans hex digits) https://github.com/pacak/bpaf/blob/master/examples/sensors.rs
-
Yet another command line argument parser: bpaf 0.5.2
see https://github.com/pacak/bpaf/blob/rc-0.5.5/examples/custom_usage.rs
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?
clap-rs - A full featured, fast Command Line Argument Parser for Rust
redox - Mirror of https://gitlab.redox-os.org/redox-os/redox
rustc-dev-guide - A guide to how rustc works and how to contribute to it.
nodejs-cli-apps-best-practices - The largest Node.js CLI Apps best practices list ✨
argparse-benchmarks-rs - Collected benchmarks for arg parsing crates written in Rust [Moved to: https://github.com/rosetta-rs/argparse-rosetta-rs]
bubblewrap - Low-level unprivileged sandboxing tool used by Flatpak and similar projects
cargo-supply-chain - Gather author, contributor and publisher data on crates in your dependency graph.
typer - Typer, build great CLIs. Easy to code. Based on Python type hints.
rust-argparse - The command-line argument parser library for rust
argparse-rosetta-rs - Comparing argparse APIs
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.