On 10/29/2016 8:58 AM, Felix Miata wrote: > NFN Smith composed on 2016-10-29 08:41 (UTC-0700): > >> Thus, your choices for that are either hard-coding into prefs.js (which >> you'll need to remove when you upgrade Seamonkey), or using one of the >> extensions noted here. > >> However, when you resort to spoofing you do have do a little maintenance >> work, because Firefox versions are a constantly moving target. If you >> hard-code into prefs.js, then you'll probably want to remove that >> setting, when the next version of Seamonkey is released. > > One should only ever manipulate prefs.js manually in the most extreme of > circumstances, and only with knowledge of the consequences. The right way to > automate inclusion of a prefs override is via user.js, a purely optional > profile file that SM will only read from, never write to. > > http://kb.mozillazine.org/User.js_file >
Another reason to use user.js is that comments can be inserted into the file to remind the user why a preference change has been inserted. Other than the standard comment -- warning users not to manually edit prefs.js -- comments cannot exist in prefs.js. -- David E. Ross Donald Trump claims everyone likes him. Does that include his ex-wives? How about the students who discovered that their education at Trump University was worthless? And how about the contractors, suppliers, and employees he stiffed in his several bankruptcies? _______________________________________________ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
