fish shell

“ghostty + fish = just works out of the box, no plugins or dotfiles needed.”

“No implicit word splitting : spaces in variables won't unexpectedly become separate arguments.”

“If I'm manually running commands on a server it means I'll likely use it interactively a lot, might as well not suffer”

“I just type a part of the command and press up few times to get to where I want”

“Fish shell autocompletes branches sorted by last commit date when writing out git commands”

“I continue to be annoyed by its refusal to implement this feature.”

“fish + starship prompt has been my choice for years now. Very little customisation needed”

“Fish doesn't let you put redirections at the beginning like that (though I wish it did)”

“There's just so much less magic to learn and remember with fish that I don't want to go back.”

“That's a ridiculously low number. Wow! I don't think my personal mac has such speed either.”

“where they don't, the fish version is nearly always more pleasant and obviously correct for interactive use”

“fish was the first shell to break out of that and actually get noticed and gain a following”

“fish shell provides the same with abbreviations, smart autocompletion, and fuzzy history search all baked right in”

“I don't feel fish (or zsh) offer an advantage big enough to bother learning that language”

“I find fish’s vi mode more ergonomically complete for things like editing multi-line commands”

“My biggest complaint about the fish shell is the lack of true vi mode.”

“The default fish install Just Works so well that I don't bother with trying to schlep my dotfiles around.”

“Things are so much easier. No need to a massive amount of plugins and configs, mostly works out of the box.”

“I've been using Fish as my default shell for over a year now, and it's so pleasant.”

“Fish gets part of the way there, but having it modeled at the parser level feels like the missing piece”

“immediately had to find community plugins for both `z` and `!!`/`!$`”

“If I use fish, I want to make use of it, and that means I will want to convert scripts”

“Fish out of the box is super performant, lots of tools ship completions for it, and the UX is just great.”

“Biggest problem being not being able to paste much of the complicated code found online.”

“you can also quite easily install fish on any host and it won't need any configuration to match what you're already used to”

“I just grew accustomed to fish defaults and have no trouble with it now, and no longer give any thought to shell configuration.”

“I have been using fish for 10 years now as my main shell and it is just perfect.”

“I like its architecture (defining functions to change its look-and-feel - great idea!) and of course its 32 ms startup time.”

“an inability to “copy this command from stackoverflow” (or in the modern day, it’ll be copy this from ChatGPT) into your shell”

“Issue is the cognitive overhead to know 2 distinct shell languages”

“More than 5 years with fish and it’s been like 5 times when not-POSIX was an “issue””

“Fish has autocomplete and syntax highlighting out of the box which is quite neat”

“it's much better out of the box than any configuration I've ever had”

“It's a lovely interactive experience out of the box with colors, completions, a great prompt”

“fish-shell has everything you want from an interactive shell included”

“These are often ecosystem which always becomes "all or nothing", you see this in all big languages Javascript, Java and even fish”

“I like using fish as my shell, if you want to try it out make sure you read the tutorial”

“they will be very confused copy-pasting commands meant for bash from the internet and them not working”

“zsh and fish becoming powerful and way more popular/well-supported than they were before”

“nushell and fish, which have nicer syntax but I've had compatibility issues in the past”