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.
Why? All the usual shell scripts don’t use Fish as interpreter.
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.
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
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.
Whatever you do, do not link /bin/sh to /bin/fish.
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
The fuck is an abbreviation? Is it a knock-off alias?
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
Been using fish for years and did not know this.