GitLab

Fixes #8545

Co-authored-by: Se De <Sede7473@gmail.com>

We have to assume that if people disabled the compfix system they really want
their completion to work, ignoring any permission issues.

Fixes #5651
Fixes #5957
Fixes #6461

 - Adding documentation
 - Note the effect empty array
 - Fix spelling
 - Using new test `[[...]]`

Revert "Move custon *.zsh file sourcing up so that they can load plugins and other things that come after."

This reverts commit a28dbc83.

Completion-dependent directories with insecure permissions or ownership (e.g.,
group or other writability) are now detected, reported, and sanitized on OMZ
startup rather than unsafely ignored -- which resulted in effectively empty
completion caches and obscure compdef() errors resembling
"compdef: unknown command or service: git".

This fixes long-standing issues #630, #3356, and #3455 and related Babun issues
159, 281, and 322 -- and probably numerous other duplicates.

We are running oh-my-zsh on a shared install and the only issue is each
user having a custom cache dir. This will allow us to set the cache dir
to ZSH_CACHE_DIR=~/oh-my-zsh/cache/ .

Some environments (such as Android) does not have /usr/bin.

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.