Fish (or 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.[4] Fish is considered an exotic shell since it does not adhere to POSIX shell standards, at the discretion of its maintainers.[5]
Fish displays incremental suggestions as the user types, based on command history and the current directory. This functions similarly to Bash's Ctrl+R 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.[6]
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.[7]
The syntax resembles a POSIX compatible shell (such as Bash), but deviates in many ways[8]
# Variable assignment## Set the variable 'foo' to the value 'bar'. # Fish doesn't use the = operator, which is inherently whitespace sensitive. # The 'set' command extends to work with arrays, scoping, etc.> set foo bar> echo $foobar # Command substitution## Assign the output of the command 'pwd' into the variable 'wd'. # Fish doesn't use backticks (``), which can't be nested and may be confused with single quotes (' '). > set wd (pwd)> set wd $(pwd) # since version 3.4> echo $wd~# Array variables. 'A' becomes an array with 5 values:> set A 3 5 7 9 12# Array slicing. 'B' becomes the first two elements of 'A':> set B $A[1 2]> echo $B3 5# You can index with other arrays and even command # substitution output:> echo $A[(seq 3)]3 5 7# Erase the third and fifth elements of 'A'> set --erase A[$B]> echo $A3 5 9# for-loop, convert jpegs to pngs> for i in *.jpg convert $i (basename $i .jpg).png end# fish supports multi-line history and editing.# Semicolons work like newlines:> for i in *.jpg; convert $i (basename $i .jpg).png; end# while-loop, read lines /etc/passwd and output the fifth # colon-separated field from the file. This should be# the user description.> while read line set arr (echo $line|tr : \n) echo $arr[5] end < /etc/passwd# String replacement (replacing all i by I)> string replace -a "i" "I" "Wikipedia"WIkIpedIaSome 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 in order 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.
# This will not work in many other shells, since the 'read' builtin# will run in its own subshell. In Bash, the right side of the pipe# can't have any side effects. In ksh, the below command works, but# the left side can't have any side effects. In fish and zsh, both# sides can have side effects.> cat *.txt | read lineThis Bash example doesn't do what it seems: because the loop body is a subshell, the update to $found is not persistent.
found=''cat /etc/fstab | while read dev mnt rest; do if test "$mnt" = "/"; then found="$dev" fidoneWorkaround:
found=''while read dev mnt rest; do if test "$mnt" = "/"; then found="$dev" fidone < /etc/fstabFish example:
set found ''cat /etc/fstab | while read dev mnt rest if test "$mnt" = "/" set found $dev endendFish 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.
# This will make emacs the default text editor. The '--universal' (or '-U') tells fish to# make this a universal variable.> set --universal EDITOR emacs# This command will make the current working directory part of the fish# prompt turn blue on all running fish instances.> set --universal fish_color_cwd bluethe Posix syntax has several missing or badly implemented features, including variable scoping, arrays, and functions. For this reason, fish strays from the Posix syntax in several important places.
This page shows common errors that Bash programmers make. (…) You will save yourself from many of these pitfalls if you simply always use quotes and never use word splitting for any reason! Word splitting is a broken legacy misfeature inherited from the Bourne shell that's stuck on by default if you don't quote expansions. The vast majority of pitfalls are in some way related to unquoted expansions, and the ensuing word splitting and globbing that result.
.svg/1280px-Free_and_open-source_software_logo_(2009).svg.png){kind=logo}