fish, the friendly interactive shell, is a commandline shell intended to be interactive and user-friendly.

fish is intentionally not fully POSIX compliant, it aims at addressing POSIX inconsistencies (as perceived by the creators) with a simplified or a different syntax. This means that even simple POSIX compliant scripts may require some significant adaptation or even full rewriting to run with fish.

Source

  • Marafon@sh.itjust.works
    37·
    20 days ago

    I just switched to fish for the pretty colors and quality of life features. Anything I should keep in mind while using it as a Linux noob? I don’t even know who POSIX is lol.

    • RmDebArc_5@piefed.zipOPEnglish
      12·
      20 days ago

      Okay so first there was Unix. It was semi Open Source and a bunch of companies were making different versions that were becoming increasingly incompatible. That is why POSIX was created, it standardizes major parts of Unix. Linux is a Unix like operating system, meaning it functions similarly but doesn’t share any code. One thing that POSIX standardizes is the shell meaning there’s a standard how a loop works etc. Most shell on Linux like bash and zsh are POSIX compliant but some (like fish aren’t). This means a command that works one way in bash might work differently in fish. Basic stuff is mostly the same in my experience so if you’re not having any problems you shouldn’t worry about being POSIX compliant. If you want most of the same stuff but POSIX compliant checkout zsh. Fish provides documentation for adjusting your commands so I’d just ignore it until you run into a problem and then take a look at the docks

    • JackbyDev@programming.devEnglish
      9·
      19 days ago

      “POSIX compliant shells” means shells that work with… Fuck how do I even describe this simplistically? A lot of scripts are ran by a program named “sh”. Sometimes it is bash, sometimes dash, but they’re all POSIX compliant which means they’ve got some standard things that most people expect.

      Using a non POSIX compliant shells will be okay, because programs trying to use “sh” will still work (unless you set something up wrong, which you’d probably have to go out if your way to do, so you’re probably fine).

      Genuinely the only downside to using a non POSIX compliant shell is that you won’t learn the standard stuff so you won’t be as good at writing and reading scripts. It’s truly not too big of a deal. Fish (non POSIX compliant) is what Arch (or at least Cachy) used by default. It’s been great. The defaults are useful. To get a similar experience with POSIX shells I typically have to use zsh with oh-my-zsh and some plugins. Fish does it all out of the box.

      So don’t worry about it!

      • Marafon@sh.itjust.works
        2·
        19 days ago

        Hell yeah, I don’t really mess with scripts much yet but I do love to be non standard. Thanks for the run down!

    • Nalivai@lemmy.world
      5·
      19 days ago

      zsh with oh-my-zsh addon can do the same amount of pretty colours and qol stuff, with the addition of being POSIX compliant. Not that fish is bad or anything, but you don’t want additional troubles with random incompatibility on top of the usual learning curve.