pazi configuration

[euank]

There are a number of things people may want to configure, varying from the alias (e.g. 'j' vs 'z') to the database size.

Until now, I've intentionally punted on configurability, but I don't think it's something to be avoided forever.

One consideration is that I would like to avoid having pazi read configuration files frequently.

I think this can be accomplished by having pazi init read the config file and then output glue shell code that also gets those configuration items across.
This could be by passing the entire configuration as a string to pazi via flag or environment variable, or by creating a nicer serialization of it to pass as a flag or flags, or something else entirely.

I do think it should be reasonable to only read configuration files on init rather than on every shell prompt, and I think this is a reasonable approach to take initially.

Of course, if pazi ever has a long running user daemon, this could be a different discussion, but that's getting well ahead of ourselves.

[leotaku]

I think that just putting all configuration into environment variables is the most reasonable and performant approach.

Users of pazi will already need to have a custom .bashrc/.zshrc/init.fish, so putting configuration there will not be a challenge to them. Moreover it allows users to have "configuration-as-code".

This approach would also serve to keep pazi light and focused on just the task it needs to accomplish.