dash
linuxmemes
Hint: :q!
Sister communities:
Community rules (click to expand)
1. Follow the site-wide rules
- Instance-wide TOS: https://legal.lemmy.world/tos/
- Lemmy code of conduct: https://join-lemmy.org/docs/code_of_conduct.html
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 of any kind will not be tolerated. This is an LGBTQ+-friendly community -- if that is a problem for you, you should leave.
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
sudoin Windows. - No porn, no politics, no trolling or ragebaiting.
- Don't come looking for advice, this is not the right community.
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 figures
We 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.

i am using ZSH cause Fish is not POSIX compliant,which made it annoying to run scripts without rewriting them.
#!/bin/sh
Hope this helps
how about if its not in a sh file,its common for scripts to use sh or bash instead. but am just gonna stick to ZSH anyways
Linux doesnโt generally use extensions to decide what shell to use, so it doesnโt matter if itโs an sh file or not.
If it uses bash of course you can substitute #!/bin/bash
And of course you can use whatever shell you want, just saying that POSIX-compliance is not really relevant since the script can specify what shell it needs.
The file extension doesn't matter much on Linux. If you've got a shebang at the top, the shell you're running from will invoke the correct shell according to the shebang.
In some situations, you may want to use something like bash <your-script>, but that would only be when you've got a script that doesn't have a shebang, but not having one is bad practice and you really should be using them. Fish isn't the only non-POSIX shell you're going to encounter on a Linux system. Python, Perl, and probably some others will be there, and using a shebang ensures no shenanigans. So whether or not you use Fish, you should always use shebangs.
When is this a problem? What scripts don't use a shebang and/or why does using sh call fish instead of bash or dash?
I have a mild dislike of fish because a few substitutions are different enough that my muscle memory isn't there. (But I also haven't put in serious effort to learn them.)
I use fish because it was the default in cachyos and decided to give it a fair shake. I like the built in syntax highlighting and fancy autocomplete but I miss bash scripting and built in commands that replace standard commands can be weird sometimes. I have not tried scripting fish, to lazy to learn yet another scripting language, especially if bash is the (almost) de-facto standard.
You can always just continue using bash scripting, with a bash shebang in your scripts, if you miss it
That's what I do. Fish is great as interactive shell, scripts don't benefit that much from it and I can use what's familiar.
I've been using it for awhile now for the same reason, and think I'm going to switch back to sh as it has too many suggestions which I read and it interrupts my thoughts and slows me down.
I like having fish as an option, but don't think I'd ever use it as my default.
If I have a long command that uses long filenames, or I don't remember the syntax of something, I can just type "fish" and it'll open up a fish shell.
I've never understood the need for fish. The shell experience is basically the same as zsh, and although it's much more pleasant to script for, you miss out on compatibility with POSIX-compliant snippets, and besides, if you're writing long and complicated scripts that need anything more than a handful of scalar variables you should probably be using Python (or Perl if you're an old-school masochist).
telnet
โฐ๏ธ
friend brought me some seashells

When I installed freeBSD for the first time, I was so confused when !! didn't work.
Heh. Good stuff.
More! ;D I want to see all the shells, characterised so.
... Fish [over[1]]user here. Ooh, good burn. LOL.
[1: Not just user. Overuser. I do most of my scripting in fish. Think that's not overuse yet? ... I even wrote my own text editor in fish.]
