Relying on some external domain seems like a bad idea after so many
recurring issues. We're certainly better off with a slightly longer URL.

Fix #867

* Change to correct argument to report accurate error message

* Update pkg/omf/functions/cli/omf.cli.theme.fish
Co-authored-by: Pablo Aguiar <scorphus@gmail.com>
Co-authored-by: Pablo Aguiar <scorphus@gmail.com>

* As omf theme <name> won't install a theme per se, changing "install" to "activate" seems clearer. So omf theme will list installed and available themes, activate a installed one, but won't install one.

* As omf theme <name> won't install a theme per se, changing "install" to 
"activate" seems clearer. So omf theme will list installed and available 
themes, activate a installed one, but won't install one.

Ref.: joelwanner/theme-boxfish#1

* docs: fix links

fix es-ES links

fix nl-NL links

fix uk-UA links

fix zh-CN links

* docs: fix README link to FAQ in nl-NL

Fix the link that slip away.

Thanks @scorphus
Co-authored-by: Pablo Aguiar <scorphus@gmail.com>

- Add barracuda and solarfish

Update bobthefish readme contents

This is somehow useless as secrets are not passed to action runners when
the workflow is triggered from a forked repository (for obvious reasons)

Co-authored-by: Noa <146050u54@gmail.com>

I didn't have much time to invest in `tools/generate-themes.doc.fish`,
unfortuntely. It's far from perfect, but fairly usable. Please, refer
to instructions in the header.

Fix #795, #800, #771

Ref #707

* Install package according to branch information in repo

* Add branch information for update package

* add double quotes for $branch
Signed-off-by: Yang Keao <keao.yang@yahoo.com>

* Fix translation

* README(zh-CN): add url example

* Fix double slash in index path

Double slash might disturb comparison and make them false positive.

* Fix compatibility with older fish shell

Suggested by @faho [here](https://github.com/oh-my-fish/oh-my-fish/pull/775#issuecomment-736224485).

For example, "git diff" would print
"fatal: this operation must be run in a work tree"

We could still run git_branch_name in bare repositories in future.

Some git commands require to be run from inside the worktree (as opposed
    to the git dir, although it's usually in .git). This commit adds
a function git_is_worktree to check this. It is used for the commands
that need the worktree instead of git_is_repo.

An alternative solution might have been to find the git worktree in the
parent of the git directory, but this doesn't work for all cases.
Generally it's impossible to detect the location of the worktree (plus
    it's not unique).
Co-authored-by: Pablo Aguiar <scorphus@gmail.com>

Fix bug when creating new theme

Add missing links, reorder alphabetically, and fix spacing issues.

Note that this includes a little bit of manual deduplication, as we have several contributors who have used different names for the same email address (or different email addresses for the same name?). Future updates to this list will need to manually dedupe as well.