I think I've found myself wishing manpages were more detailed far more often than I've found myself wishing they were shorter. In any case a man page or help text should put the most important info/FAQs at the top.
Me too, I sometimes wish to read a larger wall of text, BUT only if there are proper categories and examples. Not just hypothetical and abstract ideas and ruminations.
I don't understand why people think this is such a useful thing. Sure it has some good summaries but you can't find all info there whereas man pages should have everything. It's also good that tldr has examples but I think it's something man should more often have too. So why would people rather use this than man?
For example I often forget the order of pattern and file in grep. I can look it up easily in both man and tldr. I also forget what was the short option for recursion. Was it -r, -R or either or something else entirely? I can easily do a search on my pager to find the option in man but there's only long option available in tldr. That's Too Long Don't Want to Type.
Would you agree that man page with good example section of common use cases would better serve the purpose or do you think there has to be separate tool to show only a short summary of the manual?
For most programs, manpage or -h is more than a whole screen of text.... 99% of the time i'm just looking for a common usuage example in one line. Tldr provides that very quickly
I (not who you are asking) responded to your original comment about cheat.sh, but feot kinda fitting here too,
in the case if cheat.sh it does so much more than the manpages that I would definitely say that manpages should keep doing it's thing, because these tools strive to do more, which both makes them valuable and makes the manpages the right tool for it's thing.
I think cheat.sh has the upper hand over tldr, it retrieves the DBs from tldr and others, gives far better results imo.
rsync is a decent exampøe where cheat.sh does better than tldr imo: https://cheat.sh/rsync
as for cheat.sh vs manpages:
each has their uses. As someone who uses rsync once every .. two months, maybe, cheat.sh gives me the info i need much quicker.
ie: -avz, but maybe -c if you want to verify file integrity, that's 8 lines/2 examples in, but reading the manpage of rsync then checksumming is almost something you need to know to look for, which is fine for what the manpages are intended for.
these cheatsheets gives you common use cases, and are more of a quick reference.
also cheat.sh gives a lot more functionality than man, I can recommended skimming over the github page https://github.com/chubin/cheat.sh
Well, you know. There is more than one tldr project. Debian repositories offer the Haskell and Python based tldr ones. But, yeah, it is awesome. https://packages.debian.org/search?keywords=tldr
They really could allow more short options in the help text though. I know that --six-word-option-that-is-really-long does what I want. I need to know if it's -p, -o, -f or whatever!
I cant believe i only learned about tldr two weeks ago....
It's been a total gamechanger for me. I have such shitty memory for options flags. I'm pretty comfortable with the terminal and i've been full time linux for 15 years now
But i STILL cant remember common options for basic stuff like tar and curl....
curl output to file.... -O or -o??? Have to look it up every time
Sometimes v is verbose and sometimes it's version MAKE UP YOUR MIND
and then V is version to differentiate it from v for verbose but then sometimes V is equivalent to five vs for some reason,
