All the current themes can be found in the
themes/ directory in the oh-my-zsh distribution. See list here.
In order to enable a theme, set
ZSH_THEME to the name of the theme in your
~/.zshrc, before sourcing Oh My Zsh; for example:
If you do not want any theme enabled, just set
ZSH_THEME to blank:
Here is a collection of screenshots and descriptions of themes that have been contributed to Oh My Zsh. There are some missing from this page. If you want to add or edit descriptions, see the format description at the bottom of this page.
the (default) that Robby uses
The rest of the themes, in alphabetical order:
~/.zshrcto your regular username to hide the “user@hostname” info when you’re logged in as yourself on your local machine.
To use: You might need to install one of the patched powerline fonts for it to look the same.
Additional setup: Set up Solarized.
To use: In the right prompt you see git status and (if you use nvm) the Node.js version. (I’m using the Solarized color scheme in this screenshot.)
a skinny, topless prompt
The fish shell prompt with git support
(As the name states, this only works on linux.)
also tells you when logged in over ssh
(Shown with Solarized Dark colorscheme.)
Lightweight prompt with exit status and
git status consistent mode line
git status, git branch, and RVM, all in a no muss, no fuss prompt! Screenshot uses 14 pt Inconsolata (antialiased).
username, host, directory, git branch and rvm gemset
There is a party every day.
Based on dst, plus a lightning bolt and return codes.
Instructions to further customize the theme are available as comments in the theme file.
Clean, simple, compatible and meaningful. (more info)
We have enough themes for the time being. Please fork the project and add on in there, you can let people know how to grab it from there.
The theme descriptions in this page should contain:
~/.zshrc** For example, font installation, terminal color scheme configuration, or optional environment variables that affect the theme
We use manually-constructed screenshots because some of the themes require additional terminal configuration to look their best, and so the code in example shell sessions can showcase the theme's features. There is also a separate collection of automatically-generated screenshots linked at the bottom of this page.
We host all the screenshot images on GitHub itself, to avoid external dependencies on other hosting services or URLs that might break. We use issue attachments which will get them in to githubusercontent.com. (It's also possible to store image files in a GitHub wiki itself, but this requires you to have Contributor permissions for the repo whose Wiki you're editing. The issue-attachment method can be done by anybody.)
To upload an image to GitHub, just drag and drop it into the text area on an issue you're editing. You can use issue #3619 for this to avoid spamming people with notifications about new issues. The uploaded image will turn in to a link in Markdown format. Edit that to use the special
[![name](image-url)](image-url) syntax to make the image link to itself, so people can open the image in a new tab to view it full size. (Images inside a wiki page may be displayed scaled down.)
If you have several uploaded screenshot links you need to convert to that self-linked syntax, you can use this
sed command on the markdown file to programmatically convert them.
sed 's/^!\[[a-zA-Z0-9 -]*\](\([^)]*\)) *$/[&](\1)/'
Screenshots of each theme (as of 2013-04-10), in OS X Terminal.app using Consolas 13pt and Pro color scheme, inside a folder containing both a git and a mercurial repo. Each screenshot displays the output of the
pwd command. It has shortcomings (plugins for some themes might be missing), but it offers a convenient and uniform overview of each theme. Plugins used were battery, rvm, hg prompt, among others.