Split out of the roadmap (#51), where a config subcommand was proposed alongside the
configuration file.
The config file shipped in v0.5.0 (~/.config/asimov/config) and is edited by hand.
That's fine, but there's no way to check what Asimov actually parsed — a typo in a
section name silently does nothing.
Proposal: start with the read path, which is where the real value is:
$ asimov config
[scan]
extra = /Volumes/Work
[fixed_dirs]
enabled = true
Printing the effective config — defaults merged with the file, after parsing — turns
"why isn't my setting working?" into a one-command answer.
A write path (asimov config set ...) is possible later, but hand-editing an INI file is
not the painful part, so it's not the priority.
Split out of the roadmap (#51), where a
configsubcommand was proposed alongside theconfiguration file.
The config file shipped in v0.5.0 (
~/.config/asimov/config) and is edited by hand.That's fine, but there's no way to check what Asimov actually parsed — a typo in a
section name silently does nothing.
Proposal: start with the read path, which is where the real value is:
Printing the effective config — defaults merged with the file, after parsing — turns
"why isn't my setting working?" into a one-command answer.
A write path (
asimov config set ...) is possible later, but hand-editing an INI file isnot the painful part, so it's not the priority.