mattmc3
commented
10 months ago There's an annotation called conditional that lets you achieve something like this. I use it for loading macOS only plugins like so:
# .zshrc
# define a function
is-macos() {
[[ $OSTYPE == darwin* ]]
}
# now load antidote
source /path/to/antidote.zsh
antidote loadAnd then in your .zsh_plugins.txt
# .zsh_plugins.txt
sorin-ionescu/prezto path:modules/osx conditional:is-macosSo, let's apply this to your situation. Perhaps you are setting the ZSH_THEME variable to whatever prompt you want. You could do something like:
# .zshrc
# define a function
prompt-is-p10k() {
[[ $ZSH_THEME == 'p10k' ]]
}
# now load antidote
source /path/to/antidote.zsh
antidote load# .zsh_plugins.txt
romkatv/powerlevel10k conditional:prompt-is-p10kHowever, might I suggest a better alternative. Why don't you use Zsh's built in prompt mechanism? Pull themes into your fpath with the kind:fpath annotation. Then, you don't need to set variables - just call prompt powerlevel10k in your .zshrc.
# .zshrc
# load antidote plugins
source /path/to/antidote.zsh
antidote load
# now set your prompt - you can wrap in an `if` statement too if you want
autoload -Uz promptint && promptinit
prompt powerlevel10k# .zsh_plugins.txt
# kind:fpath will make any prompt you want available to Zsh's built-in prompt system
# as long as that prompt plugin defines a prompt_THEME_setup function
sindresorhus/pure kind:fpath
romkatv/powerlevel10k kind:fpathHope this helps. Ping me again if not.
farzadmf
Hi, I like the idea of antidote having its own file for plugins, but I have a use case which I'm not sure how to achieve using the "static" file.
Let's say I want to check if a variable is set, and only if that's the case, include a plugin in the list.
My original use case is for
powerlevel10k; I'm using different themes on my different computers, and the issue I get is that if I includepowerlevel10kin the file, it's loaded automatically, overwriting things.So, I want to load
powerlevel10kbased on a variable I set in my config