| fish | |
| Screenshot Size: | 300px |
| Author: | Axel Liljencrantz |
| Developer: | Fish-shell developers[1] |
| Programming Language: | Rust since v4.0,[2] C++ up to v3.7.1[3] |
| Operating System: | Unix-like |
| Genre: | Unix shell |
| License: | GPL-2.0-only[4] |
fish (friendly interactive shell; stylized in lowercase) is a Unix-like shell with a focus on interactivity and usability. fish is designed to be feature-rich by default, rather than highly configurable,[5] and does not adhere to POSIX shell standards by design.[6]
fish displays incremental suggestions as the user types, based on command history and the current directory. This functions similarly to Bash's history search, but is always on, giving the user continuous feedback while typing commands. fish also includes feature-rich tab completion, with support for expanding file paths (with wildcards and brace expansion), environment variables, and command-specific completions. Command-specific completions, including options with descriptions, can be to some extent generated from the commands' man pages, but custom completions can also be included with software or written by users of the shell.[7]
The creator of fish preferred to add new features as commands rather than syntax. This made features more discoverable, as the built-in features allow searching commands with options and help texts. Functions can also include human readable descriptions. A special help command gives access to all the fish documentation in the user's web browser.[8]
The syntax resembles a POSIX compatible shell (such as Bash), but deviates in many ways[9]
> set foo bar> echo $foobar
> set wd (pwd)> set wd $(pwd) # since version 3.4> echo $wd~
> set A 3 5 7 9 12
> set B $A[1 2]> echo $B3 5
> echo $A[(seq 3)]3 5 7
> set --erase A[$B]> echo $A3 5 9
> for i in *.jpg convert $i (basename $i .jpg).png end
> for i in *.jpg; convert $i (basename $i .jpg).png; end
> while read line set arr (echo $line|tr : \n) echo $arr[5] end < /etc/passwd
> string replace -a "i" "I" "Wikipedia"WIkIpedIa
Some language constructs, like pipelines, functions and loops, have been implemented using so called subshells in other shell languages. Subshells are child programs that run a few commands to perform a task, then exit back to the parent shell. This implementation detail typically has the side effect that any state changes made in the subshell, such as variable assignments, do not propagate to the main shell. fish never creates subshells for language features; all builtins happen within the parent shell.
> cat *.txt | read line
This Bash example doesn't do what it seems: because the loop body is a subshell, the update to $found is not persistent.
Workaround:
Fish example:
fish has a feature known as universal variables, which allows a user to permanently assign a value to a variable across all the user's running fish shells. The variable value is remembered across logouts and reboots, and updates are immediately propagated to all running shells.
> set --universal EDITOR emacs
> set --universal fish_color_cwd blue
| Feature | Bash syntax | fish syntax | Comment | |
|---|---|---|---|---|
| variable expansion: with word splitting and glob interpretation | $varor $or $ | Identified as a primary cause of bugs in posix compatible shell languages | ||
| variable expansion: scalar | "$var" | Every variable is an array | ||
| variable expansion: array | "$" | $var | Quoting not necessary to suppress word splitting and glob interpretation. Instead, quoting signifies serialization. | |
| variable expansion: as a space separated string | "$" | "$var" | ||
| edit line in text editor | , | Upon invocation, moves line input to a text editor | ||
| evaluate line input | [11] | Evaluates expressions in-place on the line editor | ||
| history completion | ||||
| history substitution | ! | Not discoverable | ||
| explicit subshell | (expression) | fish -c expression | ||
| command substitution | "$(expression)" | "$(expression)" or (expression | string collect) | |
| process substitution | <(expression) | (expression | psub) | Command, not syntax |
| logical operators | cmd && echo FAIL | echo OK | ||
| variable assignment | var=value | |||
| string processing: replace | "$" | string replace alice bob $HOME | ||
| string processing: remove prefix or suffix pattern, non-greedily or greedily | ||||
| export variable | export var | set --export var | Options discoverable via tab completion | |
| function-local variable | local var | |||
| scope-local variable | set --local var | |||
| remove variable | unset var | set --erase var | ||
| check if a variable exists | test -v var | set --query var | ||
| array initialization | var=(a b c) | Every variable is an array | ||
| array iteration | ||||
| argument vector: all arguments | "$@" | $argv | ||
| argument vector: indexing | "$1" | $argv[1] | ||
| argument vector: length | $# | (count $argv) | ||
| argument vector: shift | ||||
| array representation in environment variables | fish assumes colon as array delimiter for translating variables to and from the environment. This aligns with many array-like environment variables, like $PATH and $LS_COLORS. | |||
| export and run | LANG=C.UTF-8 python3 | |||
| arithmetic | $((10/3)) | math '10/3' | ||
| \e | printf builtins are both compatible with the GNU printf standalone program.[12] | |||
| single quoted string: escape sequences | Bash only requires replacement of the single quote itself in single quoted strings, but the replacement is 4 characters long. The same replacement works in fish, but fish supports a regular escape sequence for this, thus requires escaping backslashes too (except permits single backslashes that don't precede another backslash or single quote). |
