gflags
tldr
| gflags | tldr | |
|---|---|---|
| 4 | 262 | |
| 2,804 | 48,494 | |
| 0.6% | 1.0% | |
| 0.0 | 10.0 | |
| 5 months ago | 2 days ago | |
| C++ | Markdown | |
| BSD 3-clause "New" or "Revised" License | GNU General Public License v3.0 or later |
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.
gflags
- All 1,400 Google Chrome CLI flags
-
Resolved an issue in gflags which has been opened for about 7 years
Someone opened an issue at https://github.com/gflags/gflags/issues/76, to request for a feature of flag alias, and it has been opened for about 7 years.
-
New to photogrammetry, getting started?
git clone https://github.com/gflags/gflags.git
-
Why Do Long Options Start with Two Dashes?
Google's command line flags library, known to the public as absl::Flags and formerly gflags, does not distinguish between --foo and -foo, these are both the flag "foo". Each flag has a unique name so there is never a short -f equivalent to --foo, and -foo can never mean -f -o -o.
The main design motivation of absl::Flags is that the flag definitions can appear in any module, not just main. Go inherits this. A quirk that Go did not inherit is gflags --nofoo alternate form of --foo=false.
This is all documented at https://gflags.github.io/gflags/#commandline, which is pretty much a literal export of the flags package documentation that a Google engineer would see internally.
tldr
-
Ask HN: Is there a GUI for bash shell?
Maybe this already helps: https://github.com/tldr-pages/tldr
-
Try / Ripgrep in Y Minutes
A bit of an aside, but I really like "guides to things we otherwise take for granted". So few man pages are built around example use cases, but those are often what make the case for a tool!
A similar spirit to projects like https://github.com/tldr-pages/tldr/ , but this has a lot more useful detail.
The ripgrep author has a blog post on performance and benchmarking that is an interesting read in itself: https://blog.burntsushi.net/ripgrep/
- Serving my blog posts as Linux manual pages
- Tldr: Simplified and community-driven man pages
- Tell HN: My Favorite Tools
-
Should you add screenshots to documentation?
Looks like bro pages is archived and they recommend https://github.com/tldr-pages/tldr or https://github.com/cheat/cheat
-
Have i made my own linux distro? ^_^
a very excellent tool to grab is TLDR https://tldr.sh/
- fixedIt
-
Day 2 - Basic navigation
And that's why tldr is such a powerful tool! You can easily install it with sudo apt install tldr or follow this demo.
- Tldr Pages
What are some alternatives?
Boost.Program_options - Boost.org program_options module
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.
jarro2783/cxxopts - Lightweight C++ command line option parser
tealdeer - A very fast implementation of tldr in Rust.
CLI11 - CLI11 is a command line parser for C++11 and beyond that provides a rich feature set with a simple and intuitive interface.
cheat.sh - the only cheat sheet you need
args - A simple header-only C++ argument parser library. Supposed to be flexible and powerful, and attempts to be compatible with the functionality of the Python standard argparse library (though not necessarily the API).
zsh-autosuggestions - Fish-like autosuggestions for zsh
conan - Conan - The open-source C and C++ package manager
navi - An interactive cheatsheet tool for the command-line
Vcpkg - C++ Library Manager for Windows, Linux, and MacOS
fish-shell - The user-friendly command line shell.