Nit: Please "bracket" Antidote install-added sections to common config files with identifier comments.

[jwiede]

Minor nit, but it'd be useful to bracket the sections added to .zshrc and any other install-edited common config files with something like:

# === BEGIN Antidote
# Added (date) by Antidote install process

...

# See getantidote.sh/whatever for uninstall instructions
# === END Antidote

[mattmc3]

I'm not sure I understand what you're asking for, since Antidote doesn't modify your .zshrc at all. It generates a .zsh_plugins.zsh from a .zsh_plugins.txt. You have to load antidote from your .zshrc, but that's simply adding:

source /path/to/antidote.zsh
antidote load /path/to/.zsh_plugins.txt

If you want to make that have BEGIN and END, nothing's stopping you:

# === BEGIN code manually added to .zshrc for Antidote
source /path/to/antidote.zsh
antidote load /path/to/.zsh_plugins.txt
# === END code manually added to .zshrc for Antidote

But since you add that code yourself and not antidote, I'm not sure what you're hoping antidote will do for you here, but perhaps I don't understand what you're asking for??

[jwiede]

It's more about identifying which parts of zshrc belong to which components. And yes, though the user adds them, the clips are provided by antidote -- I'm just suggesting bracketing the provided clips (both "standard" and "performance" versions). The user is likely to simply copy and paste from the getantidote.sh-provided text, so just add them to the text there.

The user could add them, no question, but many users won't recognize the value of that info years down the road when they need to change or debug a problem with their .zshrc and only then realize how handy such bracketing would have been to their task. You also have cases like users using "canned ZSH configs/dotfiles" where they ,may not understand the fine details of what is what in their own .zshrc files, so every little bit of added indentification/clarification is helpful to them.