this post was submitted on 07 Apr 2026
26 points (100.0% liked)
linux4noobs
4061 readers
57 users here now
linux4noobs
Noob Friendly, Expert Enabling
Whether you're a seasoned pro or the noobiest of noobs, you've found the right place for Linux support and information. With a dedication to supporting free and open source software, this community aims to ensure Linux fits your needs and works for you. From troubleshooting to tutorials, practical tips, news and more, all aspects of Linux are warmly welcomed. Join a community of like-minded enthusiasts and professionals driving Linux's ongoing evolution.
Seeking Support?
- Mention your Linux distro and relevant system details.
- Describe what you've tried so far.
- Share your solution even if you found it yourself.
- Do not delete your post. This allows other people to see possible solutions if they have a similar problem.
- Properly format any scripts, code, logs, or error messages.
- Be mindful to omit any sensitive information such as usernames, passwords, IP addresses, etc.
Community Rules
- Keep discussions respectful and amiable. This community is a space where individuals may freely inquire, exchange thoughts, express viewpoints, and extend help without encountering belittlement. We were all a noob at one point. Differing opinions and ideas is a normal part of discourse, but it must remain civil. Offenders will be warned and/or removed.
- Posts must be Linux oriented
- Spam or affiliate links will not be tolerated.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
fish - Ever since I've made the switch to Linux, the terminal has been part of the experience. And, honestly, I wouldn't want it any other way. Besides its efficiency, I also very much enjoy how it automatically keeps track of everything I do within. I don't get that functionality whenever I do something within a GUI. But bash left a lot to be desired in that regard; its history simply didn't record everything. It was also pretty bare-bones; no syntax highlighting, no auto suggestions etc. Thus, after trying to bend bash (and later zsh) to my will and ultimately being dissatisfied with the janky mess I was left with, I finally gave in to at least give fish a honest try. The rest is history. Heck, it's the very first thing I install on a machine.
yeah Fish along with DOOM Emacs are the first two things I install on my machine.
I used to use zsh with oh my zsh and various plugins and it would totally slow down my nixos system so then I decided to give fish a try and surprise surprise it had all the stuff I had to add on to zsh already baked in.
easily the best shell out there.
I saw fish recommended for new users in openSUSE's documentation. I want to try that. There is a way to switch to Bash for a particular script, right? I know that file-based scripts have the shebang line, so that's a non-issue, but what if I have a Bash command I copied from the Internet and my default shell is fish?
As I suppose the other user already went over your main query, I'll instead focus on what might have felt rather innocuous.
I subscribe to the school of thought that one should not change their default shell^[I suppose it could be fine~ish as long as it's POSIX compliant AND compatible with bash. Which, unfortunately, fish happens to be neither of the two.] through invoking
chsh(or whatever other method that applies changes to/etc/passwd). This article does an excellent job at laying down the reasoning (and the recommended alternative). FWIW, the alternative's day-to-day experience provides all of the pros without any of the cons.Just prepend the command with "bash". If the script changes environment variables and you need that to happen in your fish environment there is https://github.com/edc/bass