• alecsargent@lemmy.zip
    0·
    7 days ago

    And then this happens:

    $ command -h
Invalid argument
Usage:
    command [subcommand]
Available Subcommands:
    help
    version
    build
    etc
  • tal@lemmy.todayEnglish
    0·
    8 days ago

    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.

    • palordrolap@fedia.io
      0·
      8 days ago

      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.

        • palordrolap@fedia.io
          0·
          7 days ago

          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.

      • tal@lemmy.todayEnglish
        0·
        8 days ago

        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.