Per conversation with @bpinto in Gitter.

There's no need for two separate directories. You don't have a `.git` and `.git-custom` folder, you just put your config in `.git` :)

The most straightforward interpretation of XDG basedir spec is that user configuration for omf would go in `~/.config/omf`, so let's put it there. The only question is whether omf-generated config (i.e. the `theme` file) should go there as well. By analogy with git, programmatically generated config should probably be merged in with user config. This also makes it so when a user clones their dotfiles to a new machine, both kinds of settings come with it.

Add local-config

Rename 'get' to 'install'

No def plus template

We already use 'install' on the command description: 'Install one or
more packages.'

Also call update using 'u' instead of 'p'.

Current in use theme should not be deletable

`default` was doing nothing.

Rename `omf use` to `omf theme`.

The first time I saw `use`, I thought I could use the command for
everything, including packages, but it's only used for themes. So, it's
better to have a clearer name.

United States of the Fish → Wahoo → Oh My Fish!

Only show deprecation warnings when omf is loaded.

Fix error handling when github API is unavailable.

The `exit` (instead of `return`) caused the shell to quit if there was
an error with github.

README: add title and foreign-env plugins

The oh-my-fish.fish startup file is sourced when changing themes after
the `fish_theme` variable is set.  The deprecation warning should only
be shown if the user sets the deprecated variables.

Add omf commands for listing available plugins/themes and for downloading a plugin/theme