this post was submitted on 08 Sep 2025
294 points (98.0% liked)

linuxmemes

27199 readers
176 users here now

Hint: :q!


Sister communities:


Community rules (click to expand)

1. Follow the site-wide rules

2. Be civil
  • Understand the difference between a joke and an insult.
  • Do not harrass or attack users for any reason. This includes using blanket terms, like "every user of thing".
  • Don't get baited into back-and-forth insults. We are not animals.
  • Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
  • Bigotry will not be tolerated.
  • 3. Post Linux-related content
  • Including Unix and BSD.
  • Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of sudo in Windows.
  • No porn, no politics, no trolling or ragebaiting.
  • 4. No recent reposts
  • Everybody uses Arch btw, can't quit Vim, <loves/tolerates/hates> systemd, and wants to interject for a moment. You can stop now.
  • 5. 🇬🇧 Language/язык/Sprache
  • This is primarily an English-speaking community. 🇬🇧🇦🇺🇺🇸
  • Comments written in other languages are allowed.
  • The substance of a post should be comprehensible for people who only speak English.
  • Titles and post bodies written in other languages will be allowed, but only as long as the above rule is observed.
  • 6. (NEW!) Regarding public figuresWe all have our opinions, and certain public figures can be divisive. Keep in mind that this is a community for memes and light-hearted fun, not for airing grievances or leveling accusations.
  • Keep discussions polite and free of disparagement.
  • We are never in possession of all of the facts. Defamatory comments will not be tolerated.
  • Discussions that get too heated will be locked and offending comments removed.
  •  

    Please report posts and comments that break these rules!


    Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't remove France.

    founded 2 years ago
    MODERATORS
    294
    Fish rules (piefedimages.s3.eu-central-003.backblazeb2.com)
     

    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

    you are viewing a single comment's thread
    view the rest of the comments
    [–] Marafon@sh.itjust.works 37 points 1 day ago (4 children)

    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.

    [–] Nalivai@lemmy.world 5 points 1 day 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.

    [–] somerandomperson@lemmy.dbzer0.com 28 points 1 day ago (1 children)

    I HIGHLY recommend using bash and zsh as posix-compliant shells at the beginning, then if you want something different; you can use whatever the hell you want. Nushell, fish, etc.

    [–] woelkchen@lemmy.world 14 points 1 day ago (1 children)

    I HIGHLY recommend using bash and zsh as posix-compliant shells at the beginning

    Why? All the usual shell scripts don't use Fish as interpreter.

    [–] somerandomperson@lemmy.dbzer0.com 3 points 1 day ago (3 children)

    No posix compliance is a headache. (Where the hell are my aliases!?) And also most scripts need to be executed in a posix-compliant shell.

    [–] Zozano@aussie.zone 12 points 1 day ago* (last edited 1 day ago) (1 children)

    Most scripts need to be executed in a posix-compliant shell

    Simple. Just add #!/bin/bash to the start of your script and call it a day.

    Or use #!/usr/bin/env bash if you're goated with the sauce. This won't work if you're not goated with the sauce.

    Those who are goated with the sauce know what's up.

    [–] joyjoy@lemmy.zip 5 points 1 day ago

    Whatever you do, do not link /bin/sh to /bin/fish.

    [–] woelkchen@lemmy.world 3 points 1 day ago

    And also most scripts need to be executed in a posix-compliant shell.

    That's why there is that shebang thingie in first line. Distributions like Debian use an entire different shell from bash for scripts: https://manpages.debian.org/buster/dash/dash.1.en.html

    [–] dreadbeef@lemmy.dbzer0.com 2 points 1 day ago* (last edited 1 day ago) (1 children)

    why use aliases (they exist in fish) when you can use abbreviations and your history isnt determined by whatever you set your aliases up as? If you change an alias, your history does not reflect that. If you use abbreviations, your history is perfectly usable

    [–] somerandomperson@lemmy.dbzer0.com 1 points 1 day ago (1 children)

    The fuck is an abbreviation? Is it a knock-off alias?

    [–] dreadbeef@lemmy.dbzer0.com 6 points 1 day ago* (last edited 1 day ago) (1 children)

    basically a text expansion. I have g=git, so when I type "g push" after I hit space after g, it expands it to git in the terminal as if i just typed out git myself. My history doesnt show "g push" it shows "git push" before I push enter

    https://fishshell.com/docs/current/cmds/abbr.html

    [–] fleet@lemmy.ca 2 points 1 day ago

    Been using fish for years and did not know this.

    [–] JackbyDev@programming.dev 11 points 1 day ago (1 children)

    "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 points 1 day 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!

    [–] RmDebArc_5@piefed.zip 13 points 1 day ago (1 children)

    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

    [–] Marafon@sh.itjust.works 1 points 1 day ago

    Hell yeah! Thanks for the background info and the link to the documentation!