And then this happens:
$ command -h Invalid argument Usage: command [subcommand] Available Subcommands: help version build etcmost of the time when i read man pages i come out even more clueless than before
Check
tldr
tldrFor those who didn’t know:
tldris an actual command:The tldr pages are a community effort to simplify the beloved man pages with practical examples.
That sign won’t stop me, because I can’t read!
$ man ls | spd-say -eEDIT: 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; donerunning for a bit to make it actually stop talking.It’s a bash builtin, so none of these work anyway.
FWIW, most if not all bash builtins turn up when searching in
man bashfor [four spaces]command-name[space], but as someone else points out, thehelpcommand also er, helps.Or you could read the info pages.
Maybe it’s the (default) configuration on my distro, but
info bashis the same information asman bashbut with no bold text for headings and things. Ironically, I think I’d have to sit down withman infoorinfo infofor an hour or two before I could figure out how to get that formatting to show up ininfo.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).
That’s what help command is for.
help cd
help while
helpOooh, 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
chshcommand.That probably wasn’t part of the upgrade process.
Ah that’s fair lmao
