ohmyzsh/ohmyzsh path:lib
ohmyzsh/ohmyzsh path:plugins/brew
ohmyzsh/ohmyzsh path:plugins/command-not-found
ohmyzsh/ohmyzsh path:plugins/gh
ohmyzsh/ohmyzsh path:plugins/git
ohmyzsh/ohmyzsh path:plugins/sudo
ohmyzsh/ohmyzsh path:plugins/npm
ohmyzsh/ohmyzsh path:plugins/nvm
ohmyzsh/ohmyzsh path:plugins/rust
ohmyzsh/ohmyzsh path:plugins/yarn
/Users/xavier/Library/Caches/antidote/https-COLON--SLASH--SLASH-github.com-SLASH-ohmyzsh-SLASH-ohmyzsh/plugins/gh/gh.plugin.zsh:14: no such file or directory: /completions/_gh
/Users/xavier/Library/Caches/antidote/https-COLON--SLASH--SLASH-github.com-SLASH-ohmyzsh-SLASH-ohmyzsh/plugins/rust/rust.plugin.zsh:22: no such file or directory: /completions/_rustup
/Users/xavier/Library/Caches/antidote/https-COLON--SLASH--SLASH-github.com-SLASH-ohmyzsh-SLASH-ohmyzsh/plugins/rust/rust.plugin.zsh:23: no such file or directory: /completions/_cargo
@mikemykhaylov -
mattmc3/zephyr path:plugins/completion
also uses a 20 hour cache for completions. If you are having trouble with your completions, you’ll also want to addrm -i ~/.cache/zsh/*compdump*
to your cleanup.I’ve decided to relent and add a proper (optional) compinit call to an upcoming release of antidote (1.7.5?). Completions are tough, and there are enough users of OMZ that I’m now convinced. I need to wrap up the
use ohmyzsh
feature first.Glad you got it working. Antidote does’t do anything special with Oh-My-Zsh - it treats it like any other set of plugins, the same as antibody did. OMZ isn’t really a set of independent plugins. It’s a framework that’s a rats nest of interdependencies. If OMZ needed you to add that to your
fpath
, you could also have added it to your.zsh_plugins.txt
file like so: