368
Thanks to the tldr devs
(lemmy.world)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 30 Mar 2024
368 points (96.5% liked)
linuxmemes
21032 readers
451 users here now
Hint: :q!
Sister communities:
- LemmyMemes: Memes
- LemmyShitpost: Anything and everything goes.
- RISA: Star Trek memes and shitposts
Community rules (click to expand)
1. Follow the site-wide rules
- Instance-wide TOS: https://legal.lemmy.world/tos/
- Lemmy code of conduct: https://join-lemmy.org/docs/code_of_conduct.html
2. Be civil
- Understand the difference between a joke and an insult.
- Do not harrass or attack members of the community for any reason.
- Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
- Bigotry will not be tolerated.
- These rules are somewhat loosened when the subject is a public figure. Still, do not attack their person or incite harrassment.
3. Post Linux-related content
- Including Unix and BSD.
- Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of
sudoin Windows. - No porn. Even if you watch it on a Linux machine.
4. No recent reposts
- Everybody uses Arch btw, can't quit Vim, and wants to interject for a moment. You can stop now.
Please report posts and comments that break these rules!
founded 1 year ago
MODERATORS
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.
I think most people use only the main functions of the program and not all of them
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?
I agree that the first option is better because it doesn't need the support of a third party.
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