boredsquirrel, 25 days ago In this specific case it is not how this works. It modifies lines searching for unique strings. If the string is not found, then it was maybe removed. (The user.js handles removals normally by commenting things out, so I might actually use a single command). If something was not found then it doesnt need to be changed, everything fine. The result is a user.js from a good template, with all the settings applied that I knew. Maybe something new was added and that is unchanged. The alternative would be not updating the config at all, which means no response to Mozilla adding weird stuff to it. Firefox is a more moving target here. I will implement a persistent GUI error message if something failed.
In this specific case it is not how this works.
It modifies lines searching for unique strings. If the string is not found, then it was maybe removed.
(The user.js handles removals normally by commenting things out, so I might actually use a single command).
If something was not found then it doesnt need to be changed, everything fine.
The result is a user.js from a good template, with all the settings applied that I knew. Maybe something new was added and that is unchanged.
The alternative would be not updating the config at all, which means no response to Mozilla adding weird stuff to it.
Firefox is a more moving target here.
I will implement a persistent GUI error message if something failed.