Skip to main content

Linux: fish: The Friendly, Interactive Shell

I'm trying out a new shell called fish. Here are some screen shots and here is a great article to help you get started.

Usually, I'm a zsh user. fish aims to be as powerful as, say, zsh, but a heck of a lot easier to use and a lot easier to learn. So far, that's proven true. The shell provides intelligent tab completion, syntax highlighting, helpful error reporting, integrated documentation, etc.

Fish is inspired by Bourne shell syntax, but is not compatible with it. Specifically, a lot of ugly things have been cleaned up and made more regular. I do think that the syntax is nicer, although it takes a while to get the hang of if you're already a shell expert. About the only inconvenient part of switching to fish is that I can no longer copy and paste complicated bash one-liners from various places online.

The documentation is excellent. However, you might find this cheat sheet helpful for getting started:
: Get help with using fish.
Searching through history:
: Type in the search string, and press the up arrow.
: Open a file using the proper application.
if true; echo hello; end
for i in a b c; echo $i; end
switch $you; case '*'; echo hi; end
function hi; echo hello; end
rm $file:
: You don't have to quote $file, even if it has spaces.
: Double quotes do variable substitution. Single quotes don't.
: Nesting doubles in singles or singles in doubles doesn't hurt
: anything. Both forms allow a minimal escaping, such as \', \\,
: or \$.
set smurf blue
: This is variable assignment. They didn't use the "=" syntax
: because in fish, *everything* is a command. Use -e to erase a
: variable, -l to set a variable locally, -g to set a variable
: globally, and -u to set a variable universally. Setting a
: variable universally applies to all fish sessions and will
: even survive a reboot. Use -x when setting a variable to export
: the value of that variable. It is convention that exported
: variables are in uppercase and unexported variables are in
: lowercase.
echo (ls)
: Use parenthesis for subshells.
f1; and f2
: This is like f1 && f2 in bash.
ls **.as
: Find all the .as files recursively.
: Redirect standard error to a file. ^^ is used for appending to
: a file.
function ll; ls -l $argv; end
: This is the replacement for aliasing and "$@".
: This is $! in bash.
: This is the directory for all your functions. They must use a
: .fish extension.
echo input.{c,h,txt}
: Echoes: input.c input.h input.txt
echo {$USER}meister
for i in (seq 10); echo $i; end
: Counts to 10. Actually, so does "seq 10" ;)
set my_array a b c; echo $my_array[1]
: Prints "a". Note, arrays are 1-based, just like seq.
count $my_array
: Returns the number of items in the array.
for i in (seq (count $my_array)); echo $my_array[$i]; end
: Here's how to loop over an array.
for i in $PATH; echo $i; end
: This is the easier way to loop over an array.
The startup file is ~/.config/fish/
: Quickly lists the current directory, or the directory your
: cursor is over.
: Adds "| less". Think "pager".
Fish supports even more Emacs-like commands--even a killring.


Unknown said…
Thanks, mate.

I really think Bash is ugly. It's even uglier to write scripts longer than 50 lines. I'd rather use something Python, Perl or Ruby for such scripts.

Now Fish looks really... delicious. :-)

Thanks, for writing about it.
jjinux said…
I still prefer Python or Ruby for long scripts, but sometimes, a short shell script really hits the spot ;)

Yes, Fish's syntax does look and feel nice.
Unknown said…
I toyed with it a bit. Very nice ideas went into that one but there are a few things that make it clumsier than BASH in places where it really matters:
- typing expr, test -lt, -ge and so on like crazy is no fun at all. BASH addressed this with $(( )) and [[ ]]
- getting the return code of the last command in BASH is as easy as $?. Here I have to type $status and subtract 128 if needed
- I write a cool script and send it to a friend "oh yeah, by the way install fish to run it"

The last point could be addressed by writing a program to do the translation but the other two make me not like it so much as to invest that time.

Popular posts from this blog

Drawing Sierpinski's Triangle in Minecraft Using Python

In his keynote at PyCon, Eben Upton, the Executive Director of the Rasberry Pi Foundation, mentioned that not only has Minecraft been ported to the Rasberry Pi, but you can even control it with Python. Since four of my kids are avid Minecraft fans, I figured this might be a good time to teach them to program using Python. So I started yesterday with the goal of programming something cool for Minecraft and then showing it off at the San Francisco Python Meetup in the evening.

The first problem that I faced was that I didn't have a Rasberry Pi. You can't hack Minecraft by just installing the Minecraft client. Speaking of which, I didn't have the Minecraft client installed either ;) My kids always play it on their Nexus 7s. I found an open source Minecraft server called Bukkit that "provides the means to extend the popular Minecraft multiplayer server." Then I found a plugin called RaspberryJuice that implements a subset of the Minecraft Pi modding API for Bukkit s…

Apple: iPad and Emacs

Someone asked my boss's buddy Art Medlar if he was going to buy an iPad. He said, "I figure as soon as it runs Emacs, that will be the sign to buy." I think he was just trying to be funny, but his statement is actually fairly profound.

It's well known that submitting iPhone and iPad applications for sale on Apple's store is a huge pain--even if they're free and open source. Apple is acting as a gatekeeper for what is and isn't allowed on your device. I heard that Apple would never allow a scripting language to be installed on your iPad because it would allow end users to run code that they hadn't verified. (I don't have a reference for this, but if you do, please post it below.) Emacs is mostly written in Emacs Lisp. Per Apple's policy, I don't think it'll ever be possible to run Emacs on the iPad.

Emacs was written by Richard Stallman, and it practically defines the Free Software movement (in a manner of speaking at least). Stal…

JavaScript: Porting from react-css-modules to babel-plugin-react-css-modules (with Less)

I recently found a bug in react-css-modules that prevented me from upgrading react-mobx which prevented us from upgrading to React 16. Then, I found out that react-css-modules is "no longer actively maintained". Hence, whether I wanted to or not, I was kind of forced into moving from react-css-modules to babel-plugin-react-css-modules. Doing the port is mostly straightforward. Once I switched libraries, the rest of the port was basically:
Get ESLint to pass now that react-css-modules is no longer available.Get babel-plugin-react-css-modules working with Less.Get my Karma tests to at least build.Get the Karma tests to pass.Test things thoroughly.Fight off merge conflicts from the rest of engineering every 10 minutes ;) There were a few things that resulted in difficult code changes. That's what the rest of this blog post is about. I don't think you can fix all of these things ahead of time. Just read through them and keep them in mind as you follow the approach above.…