FAQ

This wiki is automatically published from ohmyzsh/wiki. To edit this page, go to ohmyzsh/wiki, make your changes and submit a Pull Request.

If you don't find what you're looking for, and you think it should be covered by the FAQ, please open a new issue with what you think should be here.

Definitions
How do I...?
Common problems
Other problems
- kill-word or backward-kill-word do / don't delete a symbol (WORDCHARS)
Why is PUSHD_IGNORE_DUPS set by default?
Why shouldn't I install Oh My Zsh as root?

Definitions

What is Oh My Zsh and what does it have to do with zsh?

Zsh is a shell, just like bash or fish, which interprets commands and runs them. Oh My Zsh is a framework built on top of zsh that is structured to allow it to have plugins and themes, as well as providing what we think are the best settings from the start. You can use zsh without Oh My Zsh, but you can't use Oh My Zsh if you don't have zsh.

What is a zsh plugin?

A zsh plugin is, on its most basic form, just a shell script that can be interpreted by Zsh. So, in its essence, it can do anything that you could do run line by line in your terminal. A plugin can also provide completion for certain commands and functions.

What is a zsh theme?

A zsh theme is a zsh script that changes the prompt. The prompt is the line (or lines, on multiline themes) that appear every time you want to run a command. This is ultimately accomplished by changing the $PROMPT variable. But a theme can do much more than that, like adding an automatic git status prompt that changes each time the prompt is redrawn, or a clock that is refreshed per-second, or many other functionalities like that. Browse the Themes page to find one that you like.

NOTE: a zsh theme can't change the appearance of your terminal emulator. This includes things like the color scheme or the character font. Those are separate settings that need to be configured in your terminal emulator settings.

What is the .zshrc file?

The .zshrc file (or just zshrc file) is a file that zsh reads when it starts. It can be found in your home directory, which will change depending on the system and platform you're using. On a terminal, the path to the home directory can be found by running echo $HOME.

What Oh My Zsh is not

Zsh
A Zsh replacement
A plugin/theme downloader (although a lot of plugins/themes are preinstalled)
The app that's called "Terminal"
A terminal shell
A Zsh theme
A Bash theme
A dead project

What Zsh is not

Oh My Zsh
A plugin engine
A reason to instantly uninstall Bash
Unusable without Oh My Zsh
The app that's called "Terminal"

How do I...?

How do I install Zsh?

Check first that you have it installed: run zsh. If you really don't have it installed, please see Installing Zsh for instructions on how to install it on multiple systems.

How do I install Zsh on Windows?

You can't install Zsh directly on Windows. As a reminder, Oh My Zsh needs Zsh installed to work - if you can't install Zsh, you can't install Oh My Zsh.

To use Zsh on Windows, you need Windows 10 2004 or 11, and one of the following:

Cygwin
WSL (note that this requires you to first install WSL)

If you're running earlier versions of Windows, you can't install it at all. You'll need a virtual machine, or a proper Linux install.

How do I install Oh My Zsh?

Please follow the project's README instructions for a basic installation, or the advanced instructions if you need to automate the installation or change some of the settings of the installer.

If you'd like to install Oh My Zsh for all the users in a system, you can read the next section.

How do I install Oh My Zsh globally?

Requirements for a global install:

The root of the folder needs to be installed somewhere globally accessible, like /usr/share/ohmyzsh or /opt/ohmyzsh, with root ownership without global write permissions.
Every user's .zshrc file needs to reference the global $ZSH installation, and add the settings there, see more below.
Automatic updates are already skipped if there's no write access to the global directory or it's not a git repository, so it is not needed to turn it off manually in every .zshrc file. Remember that the global installation will not be updated automatically. If you have installed it as a git repository, you can trigger a manual update by running the command below as the root user:
```
zsh /usr/share/ohmyzsh/tools/upgrade.sh  # or wherever you installed Oh My Zsh
```
ZSH_CACHE_DIR is needed for normal usage. This is automatically changed from $ZSH/cache to $HOME/.cache/oh-my-zsh if $ZSH/cache is not writable, so it is not needed to manually change it in every .zshrc file.
ZSH_CUSTOM is set as $ZSH/custom and this one is not changed. If the user wants to add custom files they should redefine it to a directory they have write access to.

A reference of the minimal .zshrc file is below:

export ZSH="/usr/share/ohmyzsh"
ZSH_THEME=...
plugins=(...)
source "$ZSH/oh-my-zsh.sh"

How do I update Oh My Zsh?

Oh My Zsh automatically updates itself if left at the default settings. You can check out Settings for more information on how to change the update settings.

If you want to manually update Oh My Zsh, you have 2 options:

If running within your shell, you can use the CLI tool omz to force an update and restart the shell session:
```
omz update
```
If you want to update Oh My Zsh as part of an automated script, its better to use the upgrade.sh script directly. You can call it with any of these alternatives:
```
# $ZSH needs to be defined within the automated script you created
"$ZSH/tools/upgrade.sh"
zsh "$ZSH/tools/upgrade.sh"
/path/to/ohmyzsh/tools/upgrade.sh
```
This script also allows you to pass in 2 separate flags to control its behavior:
- -i: tells the script to upgrade interactively. In this mode, the only change is that the changelog will be displayed after the update.
- -v default|minimal|silent: control the verbosity of the script. This is equivalent to the verbosity settings.

Important

To upgrade Oh My Zsh, you need to have git installed and it needs to be installed as a git repository.
It is also required to be running with a user that has write access to the Oh My Zsh installation directory.

How do I manually update Oh My Zsh from a script?

See the section above.

How do I uninstall Oh My Zsh?

To remove Oh My Zsh, run uninstall_oh_my_zsh. The uninstaller will:

Delete the Oh My Zsh folder.
Back up your current .zshrc file to something like .zshrc.omz-uninstalled-<date>. This is so you can recover any settings you might have written in there. If you haven't, you can safely delete it afterwards.
If you had a .zshrc file previously to installing Oh My Zsh, the uninstaller will restore it back as the new .zshrc file.
It will attempt to switch back to the default shell you had before installing Oh My Zsh. This will be done by reading the file ~/.shell.pre-oh-my-zsh which should have been created by the installer; otherwise, it will use /bin/bash as the new default shell.

Alternatively, to manually remove OMZ do rm -rf $ZSH — you will also have to edit your .zshrc file. To manually set a new default shell, do chsh -s /my/new/shell, e.g. chsh -s /bin/bash. Then simply reopen your shells.

How do I change my locale?

The locale is used in a shell environment to define which language and character encoding (i.e. UTF-8) to use. This will change the language used by commands, as well as the encoding of the characters. Usually, you'll have set the language to use in the settings of your particular system. But sometimes you need to change the encoding used in the shell, most frequently to set it to use UTF-8.

First, to verify what locale you're using, run locale. You'll get something like this:

$ locale
LANG=en_US.utf8
LANGUAGE=
LC_CTYPE=en_US.utf8
LC_NUMERIC="en_US.utf8"
LC_TIME="en_US.utf8"
LC_COLLATE="en_US.utf8"
LC_MONETARY="en_US.utf8"
LC_MESSAGES="en_US.utf8"
LC_PAPER="en_US.utf8"
LC_NAME="en_US.utf8"
LC_ADDRESS="en_US.utf8"
LC_TELEPHONE="en_US.utf8"
LC_MEASUREMENT="en_US.utf8"
LC_IDENTIFICATION="en_US.utf8"
LC_ALL=

These are environment variables that each change one particular part of the messages that commands print. For example, LC_COLLATE changes the order in which strings are sorted. But you don't need to know them. We're only interested in LANG and LC_ALL.

LC_ALL defines the locale for all the rest of the locale environment variables. If it's not set, then LANG takes precedence. In the case above, it is set to use the English (United States) language, and a UTF-8 encoding.

If we need to change these, we need to see what available locales are installed, and we do that by running locale -a (locales ending in .UTF-8 or .utf8 all use UTF-8 as their encoding):

$ locale -a
C
C.UTF-8
en_US.utf8
POSIX

Once we have selected a suitable locale (tip: always use a UTF-8 locale), we can set it in our zshrc file, preferably at the top:

export LANG=en_US.utf8

How do I reload the zshrc file?

You may have seen somewhere that when you make a change to your zshrc file, you need to reload it. The common wrong suggestion is to use "source ~/.zshrc". This may cause trouble because some things that are already in the zsh session haven't been removed (variables, functions, hooks...). It's also possible that you're repeatedly running an init script and causing more and more processes to start.

To properly reload the zshrc file, you need to restart the zsh session. You can either:

Restart the terminal.

or

Restart the zsh process by running: exec zsh.

How do I reset the completion cache?

The completion cache file (also known as zcompdump file) is a cache of the completion functions found when starting the zsh session. This file is written when calling compinit, and it is done automatically by Oh My Zsh when starting. It can be found at $ZSH_COMPDUMP, usually in your home directory and named .zcompdump-<host>-<zsh-version>.

If there is already a file at that location, compinit will read it, instead of recreating it, for better performance. This causes problems sometimes when some completion settings are changed but the completion cache wasn't, like when a plugin is enabled. That's why most completion problems are solved by resetting the cache and restarting the zsh session.

To reset it, you have to delete it and restart your zsh session so that it is recreated again:

# Delete the completion cache
rm "$ZSH_COMPDUMP"
# Restart the zsh session
exec zsh

Common problems

Installation

I can't access the installer / connection timed out

Some countries such as India and China block access to raw.githubusercontent.com, which is where the installer is hosted.

If you can't access it, you can use our mirror at install.ohmyz.sh instead. Using it is as simple as replacing the URL:

# instead of this URL
sh -c "$(curl -fsSL https://raw.githubusercontent.com/ohmyzsh/ohmyzsh/master/tools/install.sh)"
# use this URL
sh -c "$(curl -fsSL https://install.ohmyz.sh)"

The same applies for the other installation methods, which are documented in the README or in the Home page.

You might need this if you see any of these errors when running the install command:

failed: Connection timed out.
curl(7): Failed to connect to raw.githubusercontent.com port 443: Connection timed out
curl(28): Failed to connect to raw.githubusercontent.com port 443 after <time> ms: Connection timed out

Similar issues: #11720 #11818 #11908

My .zshrc file was deleted on install

The installer script is designed to back up your existing .zshrc file, and any previous backups are also preserved. This is the current behavior of the installer, so you can search for the backup file and restore it manually.

NOTE: ~ is the path to the home directory.

a. If a .zshrc file is not found, write and modify the template zshrc file to ~/.zshrc.

b. If otherwise the .zshrc exists, start the back up process:

If ~/.zshrc.pre-oh-my-zsh exists, back it up to ~/.zshrc.pre-oh-my-zsh-<current-datetime>, where <current-datetime> is in the format YYYY-mm-dd_HH-MM-SS. If this destination file exists, the installer is aborted.
After ~/.zshrc.pre-oh-my-zsh is backed up, back up the existing .zshrc file to ~/.zshrc.pre-oh-my-zsh.
Only then write the template zshrc file to ~/.zshrc.

As you can see, the installer is designed to never delete any existing files, even if the installer is ran multiple times. If you find that your .zshrc file was deleted, you can search for the backup file with the command below:

ls -l ~/.zshrc*

I can't check out a specific commit in the Oh My Zsh folder

This happens because Oh My Zsh installs itself as a shallow git repository, with parameter --depth=1, which only pulls the latest commit. This is done to reduce the amount of data downloaded, as the repository is quite large, and also to speed up the installation process. Most users don't need the full history of the repository, so this is a good trade-off.

If you need to check out a specific commit, you can convert the repository to a full one by running the following commands:

cd $ZSH
git fetch --unshallow

Font issues

I have a weird character in my prompt

It might look like this in iTerm2:

Example problem in iTerm2

Some themes like Agnoster require a special font to render certain characters. First, make sure you have read the theme's instructions written in the Themes section. Most of the time this issue is solved by installing a Powerline font, or a nerd font. Some themes may require the use of a nerd font over a powerline font, but nerd fonts do work wherever powerline fonts work.

After installing it, you need to enable the font in the settings of your terminal emulator. Just installing the font isn't enough, as the terminal doesn't know to use that font for the symbols. Also note that the font has to be set anywhere you display the themes - this may include editors and IDEs.

Completion issues

Most completion issues are due to an old completion cache file (also called zcompdump file). Before attempting anything else, try to reset it following the instructions above. If that doesn't make the completion work, look at the other completion issue sections.

I have enabled a completion plugin but the completion doesn't work

NOTE: a recent update checks whether the plugin list has changed (more accurately, $fpath) and resets the zcompdump file, so the solution below isn't needed anymore. If you don't have that yet, update Oh My Zsh with omz update.

As of right now, after enabling or disabling a plugin that provides completion, you have to reset the cached completion file. Follow the instructions above to delete the completion file.

If this doesn't solve the problem, you might have found a bug in the plugin. Search for issues with the plugin in question, and if there isn't one already (open or closed), open a new bug report.

I see duplicate typed characters after I complete a command

This usually happens because your theme uses UTF-8 characters but your locale is not set up to handle them. Make sure that you're running a locale ending in .UTF-8 or .utf8. See How do I change my locale for instructions.

Similar issues: #6985, #3932, #4529, #4632.

Completions are not loaded when using a plugin manager

Some of the plugins in Oh My Zsh generate completion files dynamically, and puts them in the cache directory under $ZSH_CACHE_DIR/completions.

Oh My Zsh already sets this up for you, as part of the init script. However, plugin managers don't run this script automatically as they do some internal optimizations.

To check that you are affected by this, try:

echo $ZSH_CACHE_DIR

It should return something like /path/to/oh-my-zsh-folder/cache or $HOME/.cache/oh-my-zsh.
If not, add ZSH_CACHE_DIR="$HOME/.cache/oh-my-zsh" in your .zshrc file, before the plugin manager code.

Then, also check that the directories exist:

ls -l "$ZSH_CACHE_DIR"
ls -l "$ZSH_CACHE_DIR/completions"

If they don't exist, run mkdir -p $ZSH_CACHE_DIR/completions once, or add this command in the .zshrc file after defining ZSH_CACHE_DIR.

Finally, you should check whether this directory is also added to $fpath:

print -l $fpath | grep "$ZSH_CACHE_DIR/completions"

A line should appear with the path to the $ZSH_CACHE_DIR/completions folder. If not, you should also add this directory to $fpath in your .zshrc file.

Here's what you should add to your .zshrc file to fix this, before any lines loading Oh My Zsh or its plugins:

ZSH_CACHE_DIR="$HOME/.cache/oh-my-zsh"      # or any other directory you want
mkdir -p "$ZSH_CACHE_DIR/completions"
fpath=("$ZSH_CACHE_DIR/completions" $fpath)

After that everything should work again.

Note

This is a workaround when using plugin managers. Ideally we want to make this so that it works out of the box with any plugin manager you use. If you encounter an issue related to this, please +1 Feature Request #12583 and add a comment with the plugin manager affected if not already in the list.

Zsh errors

zsh: no matches found

This error happens when you used a wildcard character (also called glob operators or globbing characters), which indicate to the zsh interpreter to look for files matching that wildcard pattern (see Filename generation for the full documentation). The most common examples of these are * (star) and ? (question mark), when used in anything from apt, git or even curl commands (? is usually part of a URL).

There are many solutions, some temporary, some permanent:

Temporary: wrap the arguments containing wildcards in quotes (double quotes or single quotes, both are OK). For example:

$ apt install linux-*
zsh: no matches found: linux-*
$ apt install 'linux-*'
# the command continues successfully

Temporary: prepend noglob to the command, such that any wildcards will be ignored.

$ noglob apt install linux-*
# has the same effect as
$ apt install 'linux-*'

Permanent: disable globbing (aka wildcard expansion) at all, using unsetopt glob. Put it somewhere in your zshrc file after Oh My Zsh is sourced so that it's applied on every zsh session. NOTE: this will mean that you won't be able to use wildcards anywhere in your zsh session.
```
$ unsetopt glob
$ ls -d .* #
ls: cannot access '.*': No such file or directory
```
Permanent: another option is using the solution in (2) but making it stick with an alias so that you don't need to do this every time you run that particular command. This is much more fine-grained than (3) because you can still use wildcards in other commands.
```
$ alias apt='noglob apt'
$ apt install linux-*
# the command continues successfully
```

Some commands no longer work after installing Oh My Zsh

If you installed software from outside the default system package manager, and therefore made changes to the PATH variable to be able to use them, you need to re-add those PATH changes to ~/.zshrc to get the commands to work. This is required as the PATH variable determines where the shell looks for binaries, and without the changes from your previous shell(s), it can't find the commands. The software this affects includes, but is not limited to, nvm, rustup, Anaconda, and many others. If it works in bash, or worked before you installed Oh My Zsh, it's probably a path issue.

This might result in errors such as this:

zsh: command not found: npm

This applies even if you were using zsh, and not some other shell, prior to installing Oh My Zsh, as your original zshrc is not modified; it's replaced, but backed up before it's installed. If you used zsh prior to installing Oh My Zsh, you can retrieve your old zshrc from ~/.zshrc.pre-oh-my-zsh, and copy the changes you made from there.

If you weren't using zsh before, you need to copy over any changes to the PATH from the config file for your previous shell. Note that certain programs, such as Anaconda, may have initialisation functions that are shell-dependent, and that cannot be copied directly. For these, it's recommended you try to re-initialise the config using the software's own installation/initialisation system. For example, for Anaconda, you can use conda init zsh to regenerate the initialisation block correctly. See the documentation for the specific software you're using for more details about your alternatives when changing shells.

However, in most cases, it's enough to look at your old config files, find any and all export PATH="some string here" (where "some string here" is a placeholder for actual PATH changes), and copy those back into your current .zshrc.

Why is `PUSHD_IGNORE_DUPS` set by default?

PUSHD_IGNORE_DUPS is a setting that tells pushd to ignore duplicates in the directory stack. This means that if you try to push a directory that is already in the stack, it will not be added again. This is useful because it avoids having the same directory multiple times in the stack, which can be confusing and make it harder to navigate the stack.

This behavior makes sense when in an interactive session, especially paired with plugins such as dircycle or dirhistory, which allow you to cycle the directory stack with a simple keyboard shortcut. Having duplicates in there would make the UX worse and more confusing.

However, this behavior is not recommended when you are using pushd and popd in a script, as it can lead to unexpected behavior, as documented in the official Zsh guide:

Setting PUSHD_IGNORE_DUPS means that if you pushd to a directory which is already somewhere in the list, the duplicate entry will be silently removed. This is useful for most human operations --- however, if you are using pushd in a function or script to remember previous directories for a future matching popd, this can be dangerous and you probably want to turn it off locally inside the function.

If you are running a script non-interactively, i.e. spawning a new zsh process (via ./script.sh or zsh script.sh), you should not encounter this issue, as Oh My Zsh does not get loaded at all. However, if you are running it via source, which is not recommended, you will have this issue. If so, the solution is to unset the option locally in the script within a function:

#!/usr/bin/env zsh

function main() {
  emulate -L zsh # sets all options to their zsh default
  # or
  setopt localoptions nopushdignoredups

  # your script here
}

main # run main

Why shouldn't I install Oh My Zsh as root?

If something goes wrong with your config or Oh My Zsh, you risk breaking your system without a way to get back in, at least not without spinning up a live environment or doing a clean install. While this is rare, rare it's far more likely than with an OS stock config for the root user.

In general, it's a good idea to leave the root user's config as untouched as possible, to help avoid error recovery and security problems. This includes leaving its shell as the system default (usually bash on Linux), and not installing Oh My Zsh for the root user.

You can still install Oh My Zsh for the root user, but it isn't a good idea.

See also: Why is it bad to log in as root?

Homepage — Website — Twitter — Merchandise — Discord

Get a t-shirt!

Get stickers!

We have other stuff, have a look!

FAQ