.zsh | zsh setup for revtel | Command Line Interface library

plugins is an array used by $ZSH/oh-my-zsh.sh. You need to initialize the former before calling the latter. Just initializing plugins by itself doesn't do anything in Zsh (apart from creating a plain old array).

zsh-syntax-highlighting and zsh-autosuggestions mention explicitly in their documentation that they should be sourced after any other plugins.

Finally, if you're going to manually source a plugin, then you do not need to add it to Oh-My-Zsh's plugins array.

So, therefore, for your setup, this is the correct way to do things:

%F and %f act more like 'start color' and 'stop color', so they need to surround the text and operators that you want to colorize. Also, very few named colors are supported (just black, red, green, yellow, blue, magenta, cyan and white); you'll have better luck with the numeric values from the xterm column of this table.

Try this:

Is there a standard place or way in zsh to install zsh custom completion scripts?

Yes, there is: Just create a symlink in /usr/local/share/zsh/site-functions that points to your completion function. That's all there is to it.

This dir is by default in every user's $fpath. So, when they (or whatever framework they're using) calls compinit, it will be picked up automatically.

Zsh comes with excellent Git completion out of the box. Just throw everything you posted away, except this:

This happens because ZSH_THEME_GIT_PROMPT_PREFIX="%{$fg[blue]%}$(git_current_user_email)[" uses double quotes, which causes $(git_current_user_email) to be evaluated only once when robbyrussell.zsh-theme gets sourced, not for every prompt.

You can confirm this by running echo "$ZSH_THEME_GIT_PROMPT_PREFIX", which should now contain the email address, instead of a literal $(git_current_user_email).

Unfortunately you can't use single quotes (which do not evaluate substitutions) either here. As then you'll see a literal $(git_current_user_email) in your prompt, as the git_prompt_info function (which uses ZSH_THEME_GIT_PROMPT_PREFIX internally) does not evaluate it.

What you can do however is to put $(git_current_user_email) directly into PROMPT, which does get evaluated on each new prompt.

But we'll need to disable it ourselves when not in a git repository and can't rely on the git plugin.

Something like this:

You're making two mistakes in your .zshrc file:

1. If you do source $ZSH/oh-my-zsh.sh, then you shouldn't also do autoload -U compinit && compinit, because the former includes the latter.
2. plugins=( ... ) should be done before doing source $ZSH/oh-my-zsh.sh. The former does not do anything by itself.

So, change the top of your .zshrc file to this:

Bash itself can export its functions to other bash shells. It does so by exporting a string environmental variable of the form:

That happens because the statement setopt promptsubst in your function is executed inside the prompt function, which does setopt localoptions. So, when prompt returns, the option gets reset to default.

Instead of setting shell options directly, promptinit themes are supposed to set the prompt_opts array:

The array prompt_opts may be assigned any of "bang", "cr", "percent", "sp", and/or "subst" as values. The corresponding setopts (promptbang, etc.) are turned on, all other prompt-related options are turned off.

So, for your prompt to use setopt promptsubst, you should do something like this in your setup function:

Most likely because the zip file was created with symlinks.

From the zip man page:

-y | --symlinks

For UNIX and VMS (V8.3 and later), store symbolic links as such in the zip archive, instead of compressing and storing the file referred to by the link. This can avoid multiple copies of files being included in the archive as zip recurses the directory trees and accesses files directly and by links.