• mumblerfish@lemmy.world
      link
      fedilink
      arrow-up
      13
      ·
      edit-2
      10 months ago

      Was working on a server where I did not want to put some dumb command into the history, so I add a space like you do. Press up. The command is there. The fucking insult I felt.

      • PoolloverNathan@programming.dev
        link
        fedilink
        arrow-up
        2
        ·
        edit-2
        10 months ago

        It’s disabled by default, but you can enable it in .bashrc and then delete that edit session using a spaced command.

        Edit: brain fart

      • superbirra@lemmy.world
        link
        fedilink
        arrow-up
        2
        arrow-down
        1
        ·
        10 months ago

        it also depends on the shell, in zsh it persists on local history but does not get written to history file

    • survivalmachine@beehaw.org
      link
      fedilink
      arrow-up
      9
      ·
      10 months ago

      history displays a list of all commands you have run on the terminal since the history list was last cleared. It is invaluable for referring back to a big complex command or set of commands you ran at some point in the past. The -c flag clears that history.

      • umbrella@lemmy.ml
        link
        fedilink
        arrow-up
        4
        ·
        10 months ago

        dont you also need history -w to save it?

        on ubuntu -c doesnt actually clear it unless you also use -w

        • survivalmachine@beehaw.org
          link
          fedilink
          arrow-up
          1
          ·
          edit-2
          10 months ago

          Yes, my comment only applies to the shell history in memory. -c clears history immediately, but you can still reload it from disk if you haven’t overwritten that with -w. If you tend to close your terminal windows frequently and rely on the history feature between sessions, it would benefit you to learn about the intricacies of the on-disk copy of history and how its affected by writes, appends, clears, crashes, etc. I tend to leave my terminal windows open a long time and copy any complex commands out to my PKM if I need to save them for future sessions, so I generally try not to rely on .bash_history, but it has saved my bacon on more than one occasion.

    • akdas@lemmy.world
      link
      fedilink
      arrow-up
      6
      ·
      edit-2
      10 months ago

      It lets you clear the bash command history, either completely or selectively. Here’s the GNU docs for the history builtin: https://www.gnu.org/software/bash/manual/html_node/Bash-History-Builtins.html#index-history

      (I’m not too familiar, someone else can clarify: is this available outside bash?)

      What’s interesting to me is the -a option, which lets you “flush” the history for the current session without ending the session. I can see that being useful!