Feature: Project Config File

[mathias-ewald]

If I understand it correctly, presenterm's order of precedence for configs is

1. --config-file
2. PRESENTEM_CONFIG_FILE
3. $HOME/.config/presenterm/config.yaml

I am not sure, why user-level / system-level configs for presentations are a thing but there probably are reasons. To me, it's much more presentation specific and I solve this with direnv and the environment variable to load a config file from the project folder. My suggestion is to add a presenterm.config file to the list above to support this natively.

[mfontanini]

This is because the config file allows overriding configs like "enable automatic code execution". Making presenterm load a file in the current directory creates an attack vector where someone could share a git repo with a presentation on it + a file that has execution.enable: true or whatever config, you open it, and you get pwned.