Slowly trying to learn sh while using mostly bash. Convenience is nice and all, but when I encounter something like OpenWRT or Android, I don't like the feeling of speaking a foreign language. Maybe if I can get super familiar with sh, then I might explore prettier or more convenient options, but I really want to know how to deal with the most universal shell.
Linux
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
This is a good approach. I've always found it beneficial to learn "the standard things" than relying on a customized setup.
I've seen some people absolutely lost when they login to a system without 500 custom aliases on it..
I've recently migrated to nushell, I don't straight up recommend it because it's not POSIX compliant, so unless you're already familiar with some other she'll I would not use it.
That being said, it's an awesome shell if you deal with structured data constantly, and that's something I do quite often so for me it's a great tool.
Just looking at it briefly it looks a lot like PowerShell, any reason to use it over PowerShell?
Never used PowerShell, so I didn't know that it was available for Linux nor open source, since from a quick search both of them seem to be true I guess there's no real reason since both are described very similarly.
Bash. By default it might seem less featureful than zsh.. but bash is a lot more powerful and extensible than some give it credit for. It might be more complex to set it up the way you like it, but once you do it, that configuration can be ported over wherever bash exists (ie. almost everywhere).
Bash is my favourite one, second to it being Fish
Bash, zshell, BusyBox....you don't really need anything else
I use mainly fish and occasionally nushell.
oksh
Nushell
I have been enjoying fish a lot over the last few months, but I generally try to use Bash, it makes cross-*NIX administration that much easier.
Bash as it is what I'm most familiar with. Having an eye out on the https://amber-lang.com/ that compiles to bash for future scripting purposes.
Zsh with powerlevel10k + a few plugins
zsh because I've been using it since college and I don't like change
Bash, just because everything else already uses it. That and bashisms have infected nearly all of my scripts as I clumsily bump into the limitations of POSIX string manipulation.
I have found some very fun things with sed branching patterns as a result of these limitations though...
https://www.gnu.org/software/sed/manual/html_node/Branching-and-flow-control.html
zsh with grml config because I'm too lazy to make my own config.
POSIX on servers, thinking of switching to POSIX on desktop but that's a bit awkward
PowerShell, with zsh being a close second
Feeling risky today, eh? Mind sharing the reasoning behind your extravagant choice?
xterm+zsh
Bash is my login shell, but I have fish set as the default shell for alacritty
Zsh on workstations. Bash on servers.
I used zsh, urxvt and konsole. I do prefer zsh. Urxvt is nice too.
I have customized ZSH to be very similar to Fish