2w ago

Me, omw to needlessly waste my time

19 comments

bash

tldr
- 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.
  https://tldr.sh/
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.
  
  It gets complicated when using zsh.
- 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.

And then this happens:

    ~~~sh
$ 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.

19 comments