-
Notifications
You must be signed in to change notification settings - Fork 717
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
autoload -U
in default ~/.oh-my-zsh/oh-my-zsh.sh
*runs* compinit
#1002
Comments
autoload -U
in default ~/.oh-my-zsh/oh-my-zsh.sh
**runs** compinit
autoload -U
in default ~/.oh-my-zsh/oh-my-zsh.sh
runscompinit
autoload -U
in default ~/.oh-my-zsh/oh-my-zsh.sh
runscompinit
autoload -U
in default ~/.oh-my-zsh/oh-my-zsh.sh
*runs* compinit
up |
This repo has nothing to do with Please, report |
It is true that I found this issue due to use of " I could of course be totally wrong and this is purely an |
Also, if there's a more appropriate place to discuss issues with |
It is my understanding that
autoload -U
should pull in function definitions for later use, hence the pattern (suggested inman zshcompsys
):However, (as determined by much manual testing with
~/.zshrc:1
:zmodload zsh/zprof
and~/.zshrc:-1
:zprof
, with no other calls,compinit
is called once per shell startup. Commenting outoh-my-zsh.sh:68
:autoload -U compaudit compinit zrecompile
brings this down to 0 and makes shell startup dramatically faster.The issue is that I further update the
fpath
afteromz
is loaded, which means that at every shell startupcompinit
is run twice: once byomz
because of the reduced count offpath
functions since last complete startup, and then again after my customizations.This is wildly annoying and should be resolved with
ZSH_DISABLE_COMPFIX
-- which preventsomz
's explicitcompinit
call. However, theautoload
line still runscompinit
for whatever reason.The text was updated successfully, but these errors were encountered: