docopt.rs
tealdeer
docopt.rs | tealdeer | |
---|---|---|
4 | 48 | |
752 | 3,903 | |
- | - | |
0.0 | 6.3 | |
about 3 years ago | about 1 month ago | |
Rust | Rust | |
The Unlicense | Apache License 2.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.
docopt.rs
-
Docopt.sh – Command-Line Argument Parser for Bash 3.2, 4, and 5
Consider using clap or possibly structopt instead.
It's a lovely way to internalize the CLI argument cultural norms, decrease confusing and verbose argument parsing, make argument parsing work-free for the developer, and make argument parsing a copy-paste across languages. There's no greater pleasure than iteratively adding options to your program by just adding a line of text
-n, --new-option Do something new
I honestly think making a docopt parser is just very hard, which may limit its future prospects.
[the docopt rust repo.]: https://github.com/docopt/docopt.rs
-
Fedora to disallow CC0-licensed code
Ditto, I guess? :P (But obviously with the position on the Unlicense flipped.)
To address your indictment head-on: you suggesting the 0BSD as a better alternative is really missing my point. The 0BSD is not an alternative for my use case. The Unlicense is one of the very few overt "political" acts that I inject into the software I produce. Its purpose is to make a statement. The 0BSD doesn't do that IMO, so it's not actually an alternative that meets my advocacy goal.
You and Rick Moen seem to have the same apparent blind spot for this. See my conversation with him that started here (which might also clarify some aspects of my own position): https://github.com/docopt/docopt.rs/issues/1#issuecomment-42...
And finally, note that my dual licensing scheme is exactly a response to the "problems pointed out by quite a few people": https://github.com/BurntSushi/byteorder/issues/26
-
Docopt
I like Docopt for quick scripts, used it both in Python and Rust projects. It is quite unflexible though.
The Rust Docopt implementation¹ was deprecated this year, which is probably good because clap v3 (https://github.com/clap-rs/clap) is so awesome. In a project of mine (tealdeer), I noticed that docopt.rs was responsible for the huge majority of CPU instructions when running the binary: https://github.com/dbrgn/tealdeer/issues/106#issuecomment-59... I then switched² to clap and shaved off almost a megabyte from the release binary³. Performance improved as well, time required for rendering a tldr page went down from ~15.9 ms to ~12.4 ms⁴. With the migration, we also managed to reduce a lot of custom validation logic and move this logic into the derive macro attributes.
¹ https://github.com/docopt/docopt.rs
- clap 3.0.0-rc.7
tealdeer
- Googling for answers costs you time
-
What is your expectation of a senior dev?
Not really. 😉
-
229 Linux Commands with Examples
There's also a cli program called tealdeer that does this kind of thing and uses a local cache. And there's a fuzzy search interactive cli cheatsheet program called navi that's also pretty cool (and you can write your own cheatsheets).
-
I like flatpaks, have a few dozen of them installed, but damn those updates are massive
man command & -h/--help flags & tealdear
-
bashrc inspiration - your favorit trick
My new found love is tealdeer + fzf and this alias:
-
man sed
This is a nice tool for shortened man pages.
-
Which tldr client should I use
I use the rust implementation since I have cargo installed anyway. https://github.com/dbrgn/tealdeer
-
Secret of getting good with Linux, I made this for my channel once.
TeelDeer Github & Docs
-
Example-based cheat sheets from the command line
tealdeer (loosely pronounced TLDR) provides example-based and community-driven man pages https://github.com/dbrgn/tealdeer
-
FFmpeg cheat sheet
tealdeer for commandline cheatsheets
What are some alternatives?
clap-rs - A full featured, fast Command Line Argument Parser for Rust
tldr - 📚 Collaborative cheatsheets for console commands
structopt - Parse command line arguments by defining a struct.
cheat - cheat allows you to create and view interactive cheatsheets on the command-line. It was designed to help remind *nix system administrators of options for commands that they use frequently, but not frequently enough to remember.
easy_flag - Simple command line flag parser for rust.
grub-btrfs - Include btrfs snapshots at boot options. (Grub menu)
byteorder - Rust library for reading/writing numbers in big-endian and little-endian.
cheat.sh - the only cheat sheet you need
docopt-ng - Humane command line arguments parser. Now with maintenance, typehints, and complete test coverage.
updog - Updog is a replacement for Python's SimpleHTTPServer. It allows uploading and downloading via HTTP/S, can set ad hoc SSL certificates and use http basic auth.
argc - A Bash CLI framework, also a Bash-based command runner.
outfieldr