GitLab

This seems like a simple oversight, everything else uses `$ZSH_CUSTOM`
rather than `$ZSH/custom`.

The addition of `(.N)` enables the `NULL_GLOB` option which suppresses
the error output in question.

Reference: http://www.zsh.org/mla/users/2004/msg00621.html

* also normalized style to match the guide.

Custom plugins weren't being added to the fpath correctly.

Fixes #549. Specify ZSH=$ZSH explicitly when invoking
the auto update scripts.

just set ZSH_CUSTOM in your .zshrc, if not set oh-my-zsh.sh will
use the default custom dir in the repository

    #395 broke oh-my-zsh for users who disable check-for-updates

 - themes array is 1-based

 - theme files names are located in indicies 1 through N inclusive

 - this resolves an issue where you would occasionally see: "no such
   file or directory. Random theme '' loaded..."

Feature: Random themes now supported. Just set your theme to 'random' and it'll load a different theme each time oh-my-zsh is started. Closes #309

Reorganizing plugins so that each plugin has it's own directory now so that any plugin-specific functions can be bundled within there.

Initial implementation of a new plugin system, so that people can managed which aliases/functions they want.

Instead of using the user's standard shell, this script should be run using zsh, since that was the shell it was written for.  On my machine changes to my default shell only take effect when I log out and then long in again.  Plus, it's nice for people to be able to try oh-my-zsh out even if zsh isn't their default shell right?  :-)

This means we are running it after $PATH has potentially been set up,
which means it's more likely that commands like "git" will be found

Moving all zsh config options into a lib/ subdirectory to make way for some upcoming changes to directory structure and configuration options

Moving the loading of all .zsh files into a different file so that we can remove zshrc from the repository