• That’s what I currently use but I’ve tested fsh a little and was potentially looking to move. I just have to pull the trigger and see if I regret it or not.

      • I went from bash to zsh to fish.

        1. I understood bash. Manual is good, searchable, understandable.
        2. I never understood zsh. Manual is split up in several different man pages, very annoying to find what you’re looking for. I never ever understood what I was doing, config wise. Just blindly following convoluted how-to’s.
        3. With fish, I finally understand every aspect of my shell again, and it’s like 10x simpler than bash. Can be learned completely within 30 minutes or so.

        Highly recommend the switch.

    • Fish isn’t POSIX…

      That said, I tried nushell a couple times and it’s pretty cool. Just a big hurdle for right now.

      • yeah, but they did reverse course on ; and vs && to be more POSIX compatible, which is a decision i understand but don’t agree with

        • Hmm, where did you hear that? I’m reading the manual through relevant parts but I can’t find anything regarding those combiners and POSIX compliancy.

          Do you have a link perhaps?

  • hisao@ani.socialdeleted by creatorEnglish
    11 months

    Fish looks cool, but I decided to settle on ble.sh for compatibility reasons. This one deserves some attention too. For me the main motivation was history-based autocomplete.

      • 11 months

        Blesh adds a lot of functionality that makes bash feel + act like a fancier neoshell, while keeping the same syntax. Also includes a pre-exec hook, which vanilla bash notably lacks.

        Highly recommend.

      • hisao@ani.socialdeleted by creatorEnglish
        11 months

        Yes, but “command line editor” is a confusing term. For me it’s “get features of a fancy shell in pure bash”.

    • Fish, so much simplicity you can keep the entire language in your head while scripting.