Support `antidote use` syntax like antigen does

[mattmc3]

Antigen allows you to use antigen use for frameworks like Oh-My-Zsh. Antibody abandoned this in favor of not treating frameworks in any special way, but I think this can easily be implemented in Antidote without framework specific code. Simply, antidote use ohmyzsh/ohmyzsh and have it then let you bundle plugin_name with an implementation of:

• Clone repo as normal if it's a repo
• No need to do anything yet if it's a dir
• Source anything in the repo's lib dir
• Add the repo's plugins dir to a list of use paths
• Future bundle statements will look for single word bundles in the list of use paths

[mattmc3]

The problem implementing this remains the static file. If you use ohmyzsh/ohmyzsh and also use myprojects/zsh_custom, overriding what plugin is used gets tricky since a user could add/remove a plugin in zsh_custom at any time and the static file wouldn't know it. Adding logic to the static file would slow down the load. The complexity outweighs the convenience, but I may still revisit this if I ever come up with a clever way around this problem.

[mattmc3]

This one's been tumbling around in my brain for awhile because I don't want to implement this wrong and then regret it later and have features I'm stuck with. I think the simple solution to use ohmyzsh/ohmyzsh followed by use $ZSH_CUSTOM is simply that only one is in effect at a time, so you can only override, not have fallbacks. That also gets messy if load order matters because you might have to flip-flop between use statements.

Another option is to support :command statements, which then becomes a shortcut for something other than antidote-script.

Examples might be:

• :custom - load plugin from $ZSH_CUSTOM
• :prezto - load plugin from sorin-ionescu/prezto
• :ohmyzsh - load plugin from ohmyzsh/ohmyzsh
• :zephyr - load plugin from mattmc3/zephyr
• And allow user-defined ones.

So instead of...

### .zsh_plugins.txt
:use ohmyzsh/ohmyzsh
extract
git
history

...you could also do...

### .zsh_plugins.txt
:ohmyzsh extract
:ohmyzsh git
:ohmyzsh history

Or, we just leave things as-is, which is a working setup. None of these options feels clean, and it all adds (perhaps unnecessary) complexity. Not ready yet to implement this.

Regardless, the important callout is the static file would need to operate without any reliance on antidote functions being loaded - these :commands would just change how bundling works.

[vamsiampolu]

If I add a .zsh file in a directory, how do I load it into antidote. It does not recognise my .config/antidote/plugins/fnm.plugin.zsh directory despite doing this in my .zshenv:

fpath=(~/.config/antidote/plugins $fpath)

I tried adding my plugin as:

fnm kind:zsh

and also:

fnm kind:fpath

The former says it could not find any plugin named fnm/fnm.plugin.zsh while the latter has no error but does not list the plugin when I run:

$ antidote list | grep fnm

I understand how to resolve plugins from a repository as documented but I am not sure how to do this? I am copying over some of these things from my other machine's .oh-my-zsh/custom/plugins