Colorize command output using grc and lscolors
Latest commit 8f675aa Nov 27, 2016 @unixorn committed on GitHub Merge pull request #4 from unixorn/add-travis-link-checker-config
Add travis configuration


Colorize command output using grc and lscolors



Add zgen load unixorn/warhol.plugin.zsh to your .zshrc with your other load commands.


Add antigen bundle unixorn/warhol.plugin.zsh to your .zshrc


If you're using oh-my-zsh:

  1. In the command line, change to oh-my-zsh's custom plugin directory :

    cd ~/.oh-my-zsh/custom/plugins/

  2. Clone the repository into a new warhol directory in your custom plugins:

    git clone warhol

  3. Edit your ~/.zshrc and add warhol.plugin.zsh – same as clone directory – to the list of plugins to enable:

    plugins=( ... warhol )

  4. Then, restart your terminal application to refresh context and use the plugin. Alternatively, you can source your current shell configuration:

    source ~/.zshrc

Without using any frameworks

  1. git clone
  2. Add its bin directory to your $PATH. Add source /path/to/here/warhol.plugin.zsh to your .zshrc file.

The scripts in here don't actually require you to be using ZSH as your login shell, they're being distributed as a zgen plugin because that's convenient.


Customizing LSCOLORS for OSX/*BSD and LS_COLORS for Linux is a hassle. It's even more of a hassle to keep them in sync across *BSD and Linux.

Fortunately, Geoff Greer made an online tool that makes it easy to customize your color scheme and keep them in sync across Linux and OS X/*BSD available online at lscolors. I've included my LSCOLORS and LS_COLORS settings in this plugin. The easiest way to change them is to redeclare the variables in your .zshrc after your framework loads your plugins.

Why functions instead of aliases?

If you use aliases to colorize your apps, it breaks ZSH completions. If you use functions instead, you still get to use the completions.