tldr
this post was submitted on 22 Oct 2025
283 points (98.3% liked)
linuxmemes
28051 readers
1089 users here now
Hint: :q!
Sister communities:
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 users for any reason. This includes using blanket terms, like "every user of thing".
- Don't get baited into back-and-forth insults. We are not animals.
- 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.
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, no politics, no trolling or ragebaiting.
4. No recent reposts
- Everybody uses Arch btw, can't quit Vim, <loves/tolerates/hates> systemd, and wants to interject for a moment. You can stop now.
5. π¬π§ Language/ΡΠ·ΡΠΊ/Sprache
- This is primarily an English-speaking community. π¬π§π¦πΊπΊπΈ
- Comments written in other languages are allowed.
- The substance of a post should be comprehensible for people who only speak English.
- Titles and post bodies written in other languages will be allowed, but only as long as the above rule is observed.
6. (NEW!) Regarding public figures
We all have our opinions, and certain public figures can be divisive. Keep in mind that this is a community for memes and light-hearted fun, not for airing grievances or leveling accusations. - Keep discussions polite and free of disparagement.
- We are never in possession of all of the facts. Defamatory comments will not be tolerated.
- Discussions that get too heated will be locked and offending comments removed. Β
Please report posts and comments that break these rules!
Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't remove France.
founded 2 years ago
MODERATORS
For those who didn't know: tldr is an actual command:
The tldr pages are a community effort to simplify the beloved man pages with practical examples.
most of the time when i read man pages i come out even more clueless than before
Check tldr
It's a bash builtin, so none of these work anyway.
That's what help command is for.
help cd
help while
help
Oooh, neat. I didn't know about that. Thanks. That better not have been around since the 1990s or something, with me always searching the bash(1) man page to find builtin information.
$ help help|head -n2
help: help [-dms] [pattern ...]
Display information about builtin commands.
$ git clone https://git.savannah.gnu.org/git/bash.git
$ cd bash
$ git log -S "Display information about builtin commands."|grep ^commit|tail -n1
commit 3185942a5234e26ab13fa02f9c51d340cec514f8
$ git show 3185942a5234e26ab13fa02f9c51d340cec514f8|grep ^Date
Date: Mon Jan 12 13:36:28 2009 +0000
$
Well, it's not the 1990s, but still. Dammit.
LMAO actual madlad going in to check personally.
Also damn that was 16 years ago.
It gets complicated when using zsh.
I'm not complaining, much, but when my distro switched from bash to zsh and I didn't know until I reinstalled it for shins and gargles... that was a bad day for my remembered commands.
If you're not familiar, there's a chsh command.
That probably wasn't part of the upgrade process.
Ah that's fair lmao
FWIW, most if not all bash builtins turn up when searching in man bash for [four spaces]command-name[space], but as someone else points out, the help command also er, helps.
Or you could read the info pages.
Maybe it's the (default) configuration on my distro, but info bash is the same information as man bash but with no bold text for headings and things. Ironically, I think I'd have to sit down with man info or info info for an hour or two before I could figure out how to get that formatting to show up in info.
Info pages are supposed to be way way more comprehensive than man pages. At least for the Gnu stuff since nobody else ever bothered with info (which can be painful to use for newcomers with the cli browser, although the kde help browser integrates info files flawlessly, of course).
And then this happens:
$ command -h
Invalid argument
Usage:
command [subcommand]
Available Subcommands:
help
version
build
etc
That sign won't stop me, because I can't read!
$ man ls | spd-say -e
EDIT: If you run the above, it looks like speech-dispatcher splits the thing up into a bunch of different consecutive blocking requests, which means that it's a pain in the neck to stop with a single command. You might want to leave $ while true; do spd-say -S; done running for a bit to make it actually stop talking.