try
cli-guidelines
| try | cli-guidelines | |
|---|---|---|
| 12 | 47 | |
| 5,121 | 2,788 | |
| 0.6% | 0.9% | |
| 7.8 | 3.6 | |
| 5 days ago | about 1 month ago | |
| Shell | 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.
try
-
Command Line Interface Guidelines
"try" is not a prefix (like watch, nice, etc) uses an overlayfs in order to be able to see and accept or reject changes to your filesystem from a command
https://github.com/binpash/try
-
Show HN: Shelly: Write Terminal Commands in English
For any shell command where a minor mistake has the potential of ruining your day, take a look at “try”, which will allow you to inspect the effects before running it against a live system: https://github.com/binpash/try
- Try
- FLaNK Stack Weekly on 26 June 2023
-
Do, or do not. There is no try
he is not running a container, he is mounting an overlay file system for each root directory on the current system, then looking at what has been added as a new layer - that's what the command is supposed to add to the running system.
Pure genius.
See https://github.com/binpash/try/blob/b2df6b650cb2b58951563174...
- Do or do not. There is no try
- try: Run commands and inspect their impact before changing your live system
- Binpash/Try
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?
ai - Build AI-powered applications with React, Svelte, Vue, and Solid
redox - Mirror of https://gitlab.redox-os.org/redox-os/redox
top-cvpr-2023-papers - This repository is a curated collection of the most exciting and influential CVPR 2023 papers. 🔥 [Paper + Code]
nodejs-cli-apps-best-practices - The largest Node.js CLI Apps best practices list ✨
firejail - Linux namespaces and seccomp-bpf sandbox
bubblewrap - Low-level unprivileged sandboxing tool used by Flatpak and similar projects
ccat - Colorizing `cat`
typer - Typer, build great CLIs. Easy to code. Based on Python type hints.
FLiPStackWeekly - FLaNK AI Weekly covering Apache NiFi, Apache Flink, Apache Kafka, Apache Spark, Apache Iceberg, Apache Ozone, Apache Pulsar, and more...
argparse-benchmarks-rs - Collected benchmarks for arg parsing crates written in Rust [Moved to: https://github.com/rosetta-rs/argparse-rosetta-rs]
pygwalker - PyGWalker: Turn your pandas dataframe into an interactive UI for visual analysis
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.