• prole@lemmy.blahaj.zone
    link
    fedilink
    arrow-up
    0
    ·
    11 days ago

    Fish is great if you can’t remember a specific command, or don’t want to type out long filenames/locations, but I dunno if I’d use it as the default.

    I just type “fish” in the terminal if I ever run into a situation where I might get some use from it.

    • Digit@lemmy.wtf
      link
      fedilink
      English
      arrow-up
      0
      ·
      11 days ago

      in my ~/.bashrc

      # if interactive, launch fish
      [[ $- != *i* ]] && return || fish
      

      and

      alias f='fish'
      

      So fish is my default, and if I ever need bash, it’s already there underneath, just a Ctrl-d keybind away to fall back on, and if I want to get back into fish, it’s just a f & RETURN away.

      Seems better to have all the convenience of fish up front. All the completion magic. I so rarely have to type much at all.

      • Ephera@lemmy.ml
        link
        fedilink
        English
        arrow-up
        0
        ·
        11 days ago

        I have that occasionally when I want to copy a complex bash command from somewhere. But yeah, I can then just run bash, run the command in there and then exit back out of there.

          • Ephera@lemmy.ml
            link
            fedilink
            English
            arrow-up
            0
            ·
            11 days ago

            I’m guessing, you mean this then: https://github.com/edc/bass

            But well, I was rather thinking of when it’s using Bash-scripting-syntax to combine multiple commands.
            Like, maybe there’s a for-loop in there. You just can’t paste that directly into Fish and have it work. Granted, you should probably put that into a script file, even if you’re using Bash, but yeah, just temporarily launching bash is also an option.