ohmyzsh: complete:13: command not found: compdef

I am getting 2 instances of this error when I launch a new terminal window

complete:13: command not found: compdef
complete:13: command not found: compdef
complete:13: command not found: compdef
complete:13: command not found: compdef
jprice@xxx:pts/3-> /home » jprice  (0)

I found this: #2315 and I have commented out line 25 in the check_for_upgrades.sh.

I have also backed up all my dotfiles and removed them, and used a clean install of oh-my-zsh and I still seem to get it.

I’m lost as to what else to do? Any suggestions?

About this issue

Original URL
State: closed
Created 10 years ago
Comments: 21 (11 by maintainers)

Commits related to this issue

Completion insecurities handled on startup. Completion-dependent directories with insecure permissions or ownership (e.g., group or other writability) are now detected, reported, and sanitized on OMZ... — committed to leycec/oh-my-zsh by leycec 9 years ago
Completion insecurities handled on startup. Completion-dependent directories with insecure permissions or ownership (e.g., group or other writability) are now detected, reported, and sanitized on OMZ... — committed to kirb/oh-my-zsh by leycec 9 years ago
Completion insecurities handled on startup. Completion-dependent directories with insecure permissions or ownership (e.g., group or other writability) are now detected, reported, and sanitized on OMZ... — committed to Spirotot/oh-my-zsh by leycec 9 years ago
Fix: complete:13: command not found: compdef To prevent zsh bash completion compat feature from raising this kind of error we need to source zshell completion system before anything else that uses it... — committed to kibe88/dotfiles by kibe88 8 years ago
Completion insecurities handled on startup. Completion-dependent directories with insecure permissions or ownership (e.g., group or other writability) are now detected, reported, and sanitized on OMZ... — committed to NobbZ/oh-my-zsh by leycec 9 years ago
Completion insecurities handled on startup. Completion-dependent directories with insecure permissions or ownership (e.g., group or other writability) are now detected, reported, and sanitized on OMZ... — committed to DennisDenuto/oh-my-zsh by leycec 9 years ago

Most upvoted comments

I’m also getting the issue. I’ve tried removing ~/.zcompdump*, but they just generated again with every session.

Here is my latest file.

~/.zcompdump-5.2

barberj on Dec 17, 2016

Since this is the first hit for this error message on google: Just a little note to myself and others who run into this error while using zgen and loading OMZ modules: What you, and I, did wrong was not loading oh-my-zsh itself before its modules, as described in the readme of zgen: https://github.com/tarjoilija/zgen#load-oh-my-zsh-base

tofagerl on Apr 25, 2016

Today this message was shown. Can anybody help me? I’m on OS X, zsh 5.0.8 (x86_64-apple-darwin15.0).

UPD: I solve this problem. This problem was caused by nvm.

denysdovhan on Apr 23, 2016