Configurable paths for cache and data

[mdylanbell]

I know XDG is not technically for Mac, but I think there are a lot of people like myself that use XDG across Mac and Linux for consistency. In my experience, most XDG-aware tools support this rather than providing (option-less) defaults to ~/Library paths on mac.

Is it possible to provide a configuration directive in addition to the (technically correct, but IMO opinionated) cache and data paths? IMO providing this additional configuration is potentially useful regardless of OS, but especially for Mac.

I would propose simply providing a straightforwardly named env var per path to allow custom paths for datadir and cachedir, like ANTIDOTE_DATA_PATH and ANTIDOTE_CACHE_PATH (suffix alternative suggestions include DIR, or HOME to match repo conventions).

[mattmc3]

I prefer XDG paths too, despite being on a Mac. Currently, the two options to set are the following:

# Set to XDG_CACHE_HOME, XDG_DATA_HOME, or even XDG_STATE_HOME if you prefer
ANTIDOTE_HOME=${XDG_CACHE_HOME:-$HOME/.cache}/antidote
zstyle ':antidote:snapshot' dir ${XDG_STATE_HOME:-$HOME/.local/state}/antidote/shapshots

The reason ANTIDOTE_HOME exists as a variable is simply because antibody supported ANTIBODY_HOME and I stuck with it. But every other customization is done via zstyles so as not to clutter people's env with bunches of ANTIDOTE_* variables. That said, I'm open to adding additional zstyles, but I'm not sure adding another option for path selection is necessary since these settings already exist and are much more explicit about what things antidote stores and where.

[mdylanbell]

Thanks for the response! I actually just came back to close this since I realized setting ANTIDOTE_HOME basically achieved my goal and that I had missed this earlier. After figuring this out, I totally agree that this additional config is unnecessary.

Loving Antidote so far, please keep up the good work!