GitLab

Apparently, it is possible to set up a Mac such that
`scutil --get ComputerName` hasn't been set.

This change checks if that fails and falls back to the original
mechanism.

Closes #2155
Closes #2183

This allows customization via .zshenv if wanted. This is helpful
for zsh developers and people who want to move it out of $HOME

This will prevent lots of subtle problems that happen when
people upgrade ZSH or use NFS mounted home directories.

The ZSH_COMPDUMP variable can also be used to implement `zcompile`
and other fun features in the future.

oh-my-zsh.sh now also checks for $ZSH_CUSTOM/themes/$ZSH_THEME.zsh-theme when attempting to load a theme. This way custom themes can be a bit more organized in the 'custom' dir

`config_file` variable will mess up with `cd` auto-complete command.

eg. I have a local dir named `Code`, and when I type `cd co<Tab>`,
config_file will show up, and doesn't make any sense...

    `(.)` search only real files.
    The deletion of it enables searching symlink *.zsh files

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?  :-)