PROVIDER Β· the friendly shell that works out of the box
Fish
Fish is the shell that is pleasant by default, with autosuggestions, highlighting, and searchable history on install plus a web config UI beating plugin-stacked zsh without setup, though its non-POSIX syntax confines it to interactive use.
Pros
Cons
Product Information
Detailed Notes
Overview
Fish, the Friendly Interactive Shell, launched in 2005 designed to be pleasant by default, with autosuggestions from history and completions, live syntax highlighting, searchable history, and colourised man pages all working without plugins like those zsh needs.
For Programming Languages & Frameworks work the value is high-quality interaction with zero configuration, since suggestions and highlighting appear on install for excellent newcomer experience, a web-based fish_config interface adjusts themes and functions, and scripting syntax reads closer to modern languages without $() and bracket tests.
Face the trade-offs, because syntax is incompatible with POSIX shells so most bash scripts cannot run and fish works only as an interactive shell, servers and CI do not install it by default, and plugin counts trail zsh.
Core Strengths
- Autosuggestions, highlighting, and searchable history work with no configuration
- fish_config offers a web interface for themes, functions, and variables
- Modern scripting syntax with intuitive conditionals and substitution
- Friendly error messages onboard newcomers and ops staff quickly
Product Ecosystem
Interaction
History and completion based suggestions, live highlighting, paged history search, and directory abbreviations.
Configuration
fish_config web UI, conf.d snippets, and autoloaded functions.
Scripting
begin and end blocks, set for variables, string builtins, and (cmd) substitution.
Drawbacks
- Syntax is incompatible with POSIX shells so bash scripts fail
- Not installed by default on servers or CI, suiting local interaction only
- Smaller plugin and theme ecosystem than zsh
- Teams need explicit notes about which shell runs scripts
Use Cases
- Newcomer and ops local terminals (β β β β β ) - Friendly with no setup
- Lightweight zsh alternative (β β β β ) - No plugins needed
- Server scripting (β ) - Incompatible syntax
- CI pipelines (β ) - Not available by default
Pricing
| Plan | Price | Scope |
|---|---|---|
| Fish and source | $0 | GPLv2, entirely free |
| Community themes and plugins | $0 | Open source and free |
| Commercial support | None official | Community and distribution maintained |
Entirely free with almost no cost beyond accepting it works only as an interactive shell, so teams with many bash scripts use fish locally rather than as the script runtime.
FAQ
-
Can Fish run bash scripts? Not directly due to incompatible syntax, though fish can call bash script.sh or scripts can declare their own shebang.
-
How does it beat zsh? Suggestions and highlighting come with no configuration while zsh needs frameworks and plugins for similar results.
-
Can it be used on servers? It installs manually, but most servers lack fish so long-term practice keeps bash as the scripting standard.
Code Examples
Abbreviations, variables, and functions
# ~/.config/fish/config.fish
set -gx EDITOR nvim
abbr -a gs 'git status'
function backup --description 'back up the site directory'
set dir /data/backup/(date +%F)
mkdir -p $dir
tar -czf $dir/www.tar.gz -C /var/www html
end
Fish uses set instead of export and parentheses for substitution rather than backticks.
Interactive completion
# fish shows history suggestions in grey; press β or Ctrl+F to accept
set -l hosts hk-1 us-1 jp-1
for h in $hosts
echo "checking $h"
end
Community & Resources
Communities and official channels
- fish Site β Downloads and feature overview
- GitHub fish-shell β Source, issues, and releases
- Stack Overflow #fish β Syntax migration and config answers
Learning resources and tools
- fish Documentation β Tutorial and command reference
- awsm.fish β Curated plugins and themes
- Fisher β Plugin manager