Antidote's position on the "Zsh Plugin Standard" doc
Closed this issue · 0 comments
A small number of other Zsh plugin managers have incorporated suggestions from this document: https://zdharma-continuum.github.io/Zsh-100-Commits-Club/Zsh-Plugin-Standard.html
It proposes the following conventions:
- Standardized $0 Handling
- Functions Directory
- Binaries Directory
- Unload Function
- @zsh-plugin-run-on-unload Call
- @zsh-plugin-run-on-update Call
- Plugin Manager Activity Indicator
- Global Parameter With PREFIX For Make, Configure, Etc.
- Global Parameter holding the plugin-manager’s capabilities
To cut to the chase, I don't see much value in many of these. Most of them are over-complicated, or handled in better ways (like reloading Zsh, or implemented within plugins themselves not the plugin manager). They also appear to represent the goals of zinit rather than the Zsh plugin community as a whole. I would like to keep antidote simple and focused on its own goals of speed, simplicity, and using a robust plugins file DSL that does the job and gets out of your way. Therefore, I am not inclined to implement many/any of these, but I want to invite community input in case there is a compelling reason for some of them that I've missed. Specifically, setting $PMSPEC
, handling $ZERO
, and setting $zsh_loaded_plugins
may have some value I've overlooked.