The pipe dream would be something like the avbility to change config values and add machines to the inventory from the CLI/REPL, but:
I really do not want to handle full serialization/deserialization of the configuration structure, especially in all supported formats, since it inherently involves crappy auto reformatting of config files on save -- which I loathe as a user, 98% of the time.
I WOULD however be ok with something like:
exosphere> config edit
Which launches a (configurable, with sane default) editor against the current configuration file across platforms.
This could also be in the TUI under the palette tools, which are underused currently.
It's not exactly a high priority feature, but I edit my config file infrequently enough that remembering where it is (or running 'exosphere config paths' to find out) across platforms is causing enough friction to the process to make this have Some Value, at least to me, personally.
The pipe dream would be something like the avbility to change config values and add machines to the inventory from the CLI/REPL, but:
I really do not want to handle full serialization/deserialization of the configuration structure, especially in all supported formats, since it inherently involves crappy auto reformatting of config files on save -- which I loathe as a user, 98% of the time.
I WOULD however be ok with something like:
exosphere> config editWhich launches a (configurable, with sane default) editor against the current configuration file across platforms.
This could also be in the TUI under the palette tools, which are underused currently.
It's not exactly a high priority feature, but I edit my config file infrequently enough that remembering where it is (or running 'exosphere config paths' to find out) across platforms is causing enough friction to the process to make this have Some Value, at least to me, personally.