Home/ Questions/Q 6860757
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-27T02:26:54+00:00

I’ve just discovered oh-my-zsh, but I can’t get it to work. While themes work

  • 0

I’ve just discovered oh-my-zsh, but I can’t get it to work. While themes work just perfectly, plugins do not. I have some plugins selected, eg. macports, but neither I get port command completion nor do appropriate aliases work. Here’s my ~/.zshrc:

# Path to your oh-my-zsh configuration.
export ZSH=$HOME/.oh-my-zsh

# Set name of the theme to load.
# Look in ~/.oh-my-zsh/themes/
# Optionally, if you set this to "random", it'll load a random theme each
# time that oh-my-zsh is loaded.
export ZSH_THEME="steeef"

# Set to this to use case-sensitive completion
# export CASE_SENSITIVE="true"

# Comment this out to disable weekly auto-update checks
# export DISABLE_AUTO_UPDATE="true"

# Uncomment following line if you want to disable colors in ls
# export DISABLE_LS_COLORS="true"

# Uncomment following line if you want to disable autosetting terminal title.
# export DISABLE_AUTO_TITLE="true"

# Which plugins would you like to load? (plugins can be found in ~/.oh-my-zsh/plugins/*)
# Example format: plugins=(rails git textmate ruby lighthouse)
plugins=(git osx github macports textmate svn)

source $ZSH/oh-my-zsh.sh

# Customize to your needs...
export
PATH=/opt/local/bin:/opt/local/sbin:/usr/local/bin:/usr/local/sbin/:/opt/local/bin:/opt/local/sbin:/usr/local/bin:/usr/local/sbin/:/usr/bin:/bin:/usr/sbin:/sbin:/usr/X11/bin:/usr/local/cuda/bin:/usr/local/cuda/bin:/opt/local/bin:/opt/local/sbin

textmate and osx plugins also do not seem to work. zsh complains about unknown command and stops. git and svn have some basic completion but I’m not sure whether it’s done by plugin or just a normal zsh completion. Do I have to export something to use those plugins? Or if not, what to do to have that fixed?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    I got bitten by this.

    What happened is you did a manual install and the instructions for the manual install don’t mention that you need to set the PATH yourself.

    So you end up with the default PATH. The source for the automatic setup code copies your current path and appends it to the .zshrc, which isn’t enough if you depend on non-standard PATH entries (e.g. you run Homebrew on a Mac).

    So the fix is simple:

    Fire up your old shell and its configuration file and then copy and paste the value of $PATH into the top of your ~/.zshrc file.

    Ciao!

    • 0