kbs2: Use KBS2_CONFIG_DIR as a default config dir value #61
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This establishes the following precedence:
--config-dir DIR
KBS2_CONFIG_DIR
~/.config/kbs2
This has the nice consequence of ensuring that custom subcommands use the right configuration directory when invoking
kbs2
on their own without requiring them to do something ugly like:$ kbs2 -c "${KBS2_CONFIG_DIR}" whatever -a -b -c
Hooks are not guaranteed to receive
KBS2_CONFIG_DIR
in their environment. This probably needs to be fixed and will require a more involved change (since aConfig
doesn't know the directory that produced it).