Allow for config instead of ENV

[hoshsadiq]

Having everything in ENV variables is very muddying and even our bashrc/zshrc becomes very muddy. It would be nice to be able to read config from a yaml file. Since this is go, it shouldn't be hard or slow to parse a YAML file that reads all the information.

[jtyr]

Thanks or your suggestion. You can always create a file with all the env variables and source that file in your .bashrc file. For now I have no intention to support any other configuration.

[hoshsadiq]

My point was that it muddies the environment, typing env will give you a million variables. Imo these are unnecessary. If I were to raise a PR, would it be accepted (providing you're happy with the implementation)?

[jtyr]

I'm personally not convinced that such feature is useful but if you are going to invest your time to implement it, I'm wiling to merge it if it fulfills the following criteria:

1. It must support multiple config files which will override each others variables in the order the files are specified on the command line.
2. Variables from the config file are merged with env vars the way that env vars have always the highest priority.
3. Use TOML as the configuration format.

Example:

$ export GBT_CAR_DIR_PRECISSION=9999
$ cat /path/to/file1
# Global variables
separator = ""
# Dir car variables
[dir]
fg = "yellow"
$ cat /path/to/file2
# Dir car variables
[dir]
fg = "red"
depth = 3
$ gbt --config /path/to/file1 --config /path/to/file2

As a result of the above, the Dir car will end up with red foreground and depth of 9999.