Add to Chrome
Add to Edge
Add to Firefox
Add to Opera
Add to Brave
Add to Safari
Join our community
Top Pro
•••
Top Con
•••
Ken Goad's Experience
Top Con
•••
Top Pro
•••
Top Pro
•••Top Con
•••
Top Pro
•••
Zsh will take you through a procedure which is roughly 30 minutes in length before during install. Through this procedure it asks you to set different options and customize the shell the way you want it to. Most of these settings are also found in other shells, but to customize them you have to go dig configuration files while zsh allows you to do it in the beginning. See More
Although fish tries not to break POSIX compatibility without a good reason, and despite efforts to implement a compatibility mechanism, you can face some issues if POSIX compatibility is expected/required. Though, enthusiasts fix these cases. For example, add set shell=sh in your .vimrc to solve the issue for vim. See More
Fish blows the others out of the water, there's no comparison. The top two cons I'm seeing writing this: "no undo support" which is just like every other shell so invalid complaint. And "weird syntax". Whatever that means. I implore you to completely ignore them. Zsh is at the top because it's just bash but better, and bash is above fish because it's the default and people hate trying new things even though technical jobs tend to involve having to learn new things every week anyways. What's more, you can actually still use bash and/or zsh and use fish. Fish automatically reads your config profiles and works with them, and you can run bash commands right from fish with bash -c, or install the replay plugin. I can't live without it anymore, and I feel pity for those haters who've so briskly brushed into the garbage. See More
Fish has no support for !!, but you can use Oh My Fish shell framework and install bang-bang plugin to have this shortcut in Fish shell. The downside of using bang-bang is that it takes over ones default key bindings, for those that don't use them it should not be an issue but for those that do it is an annoyance to be considered. For sudo !!, this can also be achieved by making this custom function: function sudo
if test "$argv" = !!
eval command sudo $history[1]
else
command sudo $argv
end
end See More
While other shells require a lot of set up to act the way you want them to and to have some useful features, fish works perfectly out of the box. It has all the most widely used features baked in and are there out of the box without having the need to install plugins or tweak any configuration files. See More
Here is a sample. Notice that there are 2 files with spaces in names. ls produces a valid list, and for loop correctly iterated through its values. ➤ for a in (ls); ls -l $a; end
-rw-rw-r-- 1 sashka sashka 0 Apr 19 03:16 alma mater.txt
-rw-rw-r-- 1 sashka sashka 0 Apr 19 03:16 whatever i want.txt sh scripts tend to be fragile when there are lists containing values with spaces. Also: ➤ echo $PATH
/usr/bin /bin /usr/sbin /sbin /usr/local/bin
➤ echo $PATH[1]
/usr/bin
➤ echo $PATH[-1]
/usr/local/bin See More
What it is mostly used for are file system operations. Guess what it is bad at? Operating on files. It automatically splits and carries out filename expansion on every single string resulting from variable expansion and command substitution unless quoted, by default on whitespace, whilst spaces are very common in filenames. Before that, it even does pathname expansion, so woe to anywone who does not want to actually operate on files, but has a globbing metacharacter stored anywhere in a variable. This means what you store in a variable is not going to be what will ACTUALLY be accessed. If an empty variable is unquoted, it disappears completely due to word splitting, sometimes leading to applications signalling a missing parameter at a wrong position. If quoted however, said variables cannot be iterated over in a loop, no matter what character one uses for word splitting. If you use any globbing pattern with a command, be sure to use -- after the option arguments or if none are present, before starting the pattern with a mandatory ./ Otherwise, another Bash script run gone wrong or a hacker can create files named like an option ("-f", for instance) and your program will happily accept it as such, if it results from globbing. For interactive use, it is convenient. For programming, it is a no-go. See More
Want to run something 5 times? Write a throw-away loop: for i in 1 2 3 4 5; do date; done If you need it 100 times? Not a problem: for i in {1..100}; do date; done or: for ((i=0; i<100; ++i)); do date; done How about emailing yourself when remote server is back online? Sure thing: while ! ping -c1 example.com &>/dev/null; do date; sleep 5; done && mailx -s 'server is back!' me@myself.com See More