New features in the fish shell
New features in the fish shell
Posted Sep 29, 2020 22:15 UTC (Tue) by areilly (subscriber, #87829)Parent article: New features in the fish shell
Posted Sep 30, 2020 5:21 UTC (Wed)
by johannes (guest, #116140)
[Link] (1 responses)
> All of the UI stuff was lovely, but I don't see that that has to imply a different shell language
True but it's much easier to implement consistent highlighting, indentation, completion and error messages if the language is syntactically simple. Other shells don't indent or highlight at all.
> I couldn't get it to behave sensibly around remote ssh commands (with fish as the login shell on the remote machine).
Yeah, that's one of the places where setting fish as login shell can backfire. It's often better to launch it in a different way.
Posted Sep 30, 2020 10:31 UTC (Wed)
by mathstuf (subscriber, #69389)
[Link]
I agree. I use zsh almost exclusively, but my login shell is bash. I configure my terminal-launching keybindings and tmux to use zsh by default instead.
New features in the fish shell
The use case is different, so different tools are justified. The most used interactive commands work the same way in fish.
There are easy-to-learn fish equivalents for constructs that are commonly used interactively. If something is missing it can usually be implemented in a small function.
Supporting obscure features from other shells yields diminishing returns, but widely used features are happily added, like && and var=value.
Likewise, humans use different constructs in oral and written language, both languages co-evolve and adopt useful features from each other.
New features in the fish shell
