Open ghoomfrog opened 5 years ago
At the moment this is just the way this is implemented in Tilda. Fixing this will require to change the configuration system in Tilda to not write the values into the config files during start. If we do that, then we also need to change any access to those config values to also check the values of CLI options. I am thinking to do that, but one design aspect that I am not sure about yet is how to handle the modified values in the configuration wizard. If you start Tilda with a custom command by passing the -c
option and then you go to the Preferences and modify the custom command, should that be possible and should it take preference over the CLI option?
forward explanation:
<command>
is the last command given to '-c' as argument.I enter
tilda -c <command>
, tilda opens, then I close it. After, I enter justtilda
, and this time, it opens but executes<command>
. It runs the last passed custom command through "-c". Actually, when I check that instance's configuration file, I find that the second line is overwritten tocommand="<command>"
.How can I fix that? I don't want tilda to permanently overwrite the second line.