friendly interactive shell

fish

The friendly interactive shell
Original author(s)	Axel Liljencrantz
Developer(s)	ridiculousfish, siteshwar, JanKanis[1]
Initial release	13 February 2005 (2005-02-13)
Stable release	2.4.0 / 8 November 2016 (2016-11-08)[2]
Repository	github.com/fish-shell/fish-shell
Operating system	Unix-like
Type	Unix shell
License	GPL v2[3]
Website	fishshell.com

The friendly interactive shell (fish) is a Unix shell that attempts to be more interactive and user-friendly than former shells. The design goal of fish is to give the user a rich set of powerful features in a way that is easy to discover, remember, and use.^[4] fish is considered an "exotic shell", in that its syntax derives from neither the Bourne shell (ksh, bash, zsh) nor the C shell (csh, tcsh). Also unlike previous shells, which disable certain features by default to save system resources, fish enables all features by default.

Highlights

fish has "search as you type" automatic suggestions based on history and current directory. This is essentially like bash's Ctrl+R history search, but because it is always on instead of being a separate mode, the user gets continuous feedback while writing the command line, and can select suggestions with the arrow keys, or as in bash, press Tab ↹ for a tab completion instead. Tab-completion is feature-rich, expanding file paths (with wildcards and brace expansion), variables, and many command specific completions. Command-specific completions, including options with descriptions, can to some extent be generated from the commands' manpages.

Fish has few syntactic rules, preferring features as commands rather than syntax. This makes features discoverable in terms of commands with options and help texts. Functions can also carry a human readable description. A special help command gives access to all the fish documentation in the user's web browser.^[5]

Syntax

The syntax resembles a POSIX compatible shell (such as bash), but deviates in important ways where the creators believe the POSIX shell was badly designed.^[6]

# Variable assignment, set the variable 'foo' to the 
# value 'bar'.  Fish doesn't use the = operator, since 
# it is inherently whitespace sensitive.  Also, the set 
# command easily extends to work with arrays, scoping, etc.
> set foo bar
> echo $foo
bar
 
# Command substitution, assign the output of the command 
# 'pwd' into the variable 'wd'.  Fish doesn't use `` 
# since they can't be nested and look too much like ' '. 
# Don't use $() since $ is only used for variable 
# expansion in fish.
> set wd (pwd)
> 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 $B
3 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 $A
3 5 9

# for-loop, convert jpegs to pngs
> for i in *.jpg
      convert $i (basename $i .jpg).png
  end
# Semicolons work like newlines:
> for i in *.jpg; convert $i (basename $i .jpg).png; end
# but the multi-line form is comfortable to use because 
# fish supports multi-line history and editing.

# while-loop, read lines /etc/passwd and output the fifth 
# colon-separated field from the file. This should be
# the user description.
> cat /etc/passwd | while read line
      set arr (echo $line|tr : \n)
      echo $arr[5]
  end

No implicit subshell

Some language constructs, like pipelines, functions and loops, have been implemented using so called subshells in other shell languages. Subshells are simply child programs that run a few commands for the shell and then exit. Unfortunately, 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, which may surprise the user. Fish never forks off so-called subshells; all builtins are always fully functional.

# 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 line

Variable assignment example

This bash example does not do what it looks like: 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"
  fi
done

Workaround:

found=''
while read dev mnt rest; do
  if test "$mnt" = "/"; then
    found="$dev"
  fi
done < /etc/fstab

Fish needs no workaround:

set found ''
cat /etc/fstab | while read dev mnt rest
  if test "$mnt" = "/"
    set found $dev
  end
end

Helpful error messages

Error messages in fish are designed to actually tell the user what went wrong and what can be done about it.^[7]

> foo=bar
fish: Unknown command “foo=bar”. Did you mean “set VARIABLE VALUE”?
For information on setting variable values, see the help section on
the set command by typing “help set”.

> echo ${foo}bar
fish: Did you mean {$VARIABLE}? The '$' character begins a variable
name. A bracket, which directly followed a '$', is not allowed as a
part of a variable name, and variable names may not be zero characters
long. To learn more about variable expansion in fish, type “help
expand-variable”.

> echo $(pwd)
fish: Did you mean (COMMAND)? In fish, the '$' character is only used
for accessing variables. To learn more about command substitution in
fish, type “help expand-command-substitution”.

Universal variables

Fish has a feature known as universal variables, which allow 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 '-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 blue

Other features

• Advanced tab completion.
• Syntax highlighting with extensive error checking.
• Support for the X clipboard.
• Smart terminal handling based on terminfo.
• Searchable command history.

Version 2 adds:

• Autosuggestions
• 256 terminal colors
• Web-based configuration
• Improved performance (by having more builtins).

bash/fish Translation table

$var

${var[@]}

${var[*]}

"$var"

"${var[@]}"

$var

"${var[*]}"

"$var"

sudo !! 

(expression) 

"$(expression)" 

(expression) 

<(expression)

(expression | psub)

!cmd && echo FAIL || echo OK

not command
and echo FAIL
or echo OK

var=value 

set var value

"${HOME/alice/bob}"

string replace alice bob $HOME

var=a.b.c
"${var#*.}"  #b.c
"${var##*.}" #c
"${var%.*}"  #a.b
"${var%%.*}" #a

string replace --regex '.*?\.(.*)' '$1' a.b.c #b.c
string replace --regex '.*\.(.*)' '$1' a.b.c  #c
string replace --regex '(.*)\..*' '$1' a.b.c  #a.b
string replace --regex '(.*?)\..*' '$1' a.b.c #a

export var 

set --export var 

local var

set --local var

unset var 

set --erase var 

[ ! -z ${var+x} ]

set --query var

var=( a b c ) 

set var a b c

for i in "${var[@]}"; do
  echo "$i"
done

for i in $var
  echo $i
end

"$@" 

$argv 

"$1" 

$argv[1] 

$#

(count $argv)

shift

set argv $argv[2..-1]

PATH="$PATH:$HOME/.local/bin"

set PATH $PATH $HOME/.local/bin

LANG=C.UTF-8 python3 

 begin
   set --export --local LANG C.UTF-8
   python3
 end

$((10/3))

math '10/3'

$'\e'

\e 

'mom'\''s final backslash: \'

'mom\'s final backslash: \\'

See also

• Comparison of command shells

References

External links

• Official website – containing documentation and downloads
• fish on GitHub (active)
• fish on Gitorious (obsolete)
• fish on SourceForge (obsolete)
• Fish-users – general discussion list for fish users
• Shell Translation Dictionary - another Bash/Fish translation table