> ampersand-nobg-in-token, which means that & will not create a background job if it occurs in the middle of a word. For example, echo foo&bar will print “foo&bar” instead of running echo foo in the background and then starting bar as a second job.<p>Yes! This has been annoying with curl for a long time.
Fish is fantastic. Some people worry about posix compatibility and stuff, but that only matters if you are copy pasting bash snippets directly to the command line. If you are using bash or zsh as a programming language then you put the code in a file, and run it with that shell - so it doesn't matter what shell you are running.<p>If you love bash or zsh, and are in the habit of building long complex commands on the command line, then stick with bash or zsh. But if you are just running commands fish is far superior. If you are not a bash/zsh/posix expert fish is a cleaner language and you'll learn it more easily. A fully tricked out zsh might do everything that fish does, but it is very slow compared to fish.
> Added completions for:<p>> archlinux-java (#8911)<p>> apk (#8951)<p>> brightnessctl (#8758)<p>> efibootmgr (#9010)<p>> fastboot (#8904)<p>> optimus-manager (#8913)<p>> rclone (#8819)<p>> sops (#8821)<p>> tuned-adm (#8760)<p>> wg-quick (#8687)<p>One of my favorite things about fish is that it bundles completions for a huge number of packages. My experience with bash was that completion support was very spotty
Great! Love the new Astronaut prompt. I dabbled with starship.rs, and really liked the prompt, but ultimately didn't want to deal with an extra moving part in my terminal setup. I'm so happy that some of it is available in stock fish shell, now.
I really love fish and used it daily for many years. Then I started work at a new company that had an existing library of internal shell tools that weren't compatible with Fish and the effort to port them was too much.<p>I found that ZSH managed with OhMyZSH plugins gets me similar functionality without the syntax incompatibilities. Unfortunately unless Fish moves back towards compatibility I don't see myself ever going back, it's just too much hassle dealing with little syntax issues all the time.
Been meaning to move fully to Fish, was just dreading the amount of zsh functions I'd have to rewrite.<p>Is there any reason to use Zsh at this point over Fish?
This killed all shell interaction within my tmux setup, somehow, and I had to downgrade in osx/brew [1] back to v3.4.1 [2]. I'm still wondering what part of my (probably outdated) tmux config caused it, but the most suspicious part is the run-shell/if-shell stuff.<p>Anyway, have things to do before I can try again and dig in. Thought I'd post in case someone else ran into this.<p>[Edit] Tip: swap to a different shell before uninstalling your current shell. Sigh...lol<p>[1] <a href="https://github.com/fish-shell/fish-shell/issues/5497" rel="nofollow">https://github.com/fish-shell/fish-shell/issues/5497</a>
[2] <a href="https://raw.githubusercontent.com/Homebrew/homebrew-core/ad5d542a28f634a9b65a5a7f6dbacab335aff92d/Formula/fish.rb" rel="nofollow">https://raw.githubusercontent.com/Homebrew/homebrew-core/ad5...</a>
If I'm not a "power user" (learned rudimentary bash as teenager, stuck with it on MacOS through college) is it worth it to learn a new shell?<p>I respect the craftmanship, but if I'm more of a "software carpenter" why should I invest the time?
I'm running fish for at least 8 years now and I'm very happy with the out of the box experience. It's one of the first things I install on new machines.