On 1/29/2015 6:23 PM, Ed Mullen wrote:
> David E. Ross wrote on 1/29/2015 3:46 PM:
>> On 1/29/2015 10:09 AM, Bill Spikowski wrote:
>>> David E. Ross wrote:
>>>>
>>>> I saw the same thing earlier this week. With SeaMonkey terminated, I
>>>> went to the file prefs.js in my profile, opened it in Wordpad, and
>>>> searched for "print.printer". I deleted blocks of preference variables
>>>> that related to obsolete printers and such pseudo printers as Adobe
>>>> Acrobat (for which the print-to-PDF function is not supported in Windows
>>>> 7) and doPDF 7 (an application that does print-to-PDF but has been
>>>> replaced with doPDF 8).
>>>>
>>>> If you have never edited prefs.js, I strongly recommend that you save
>>>> the file outside of your profile. Also, editing it will not work unless
>>>> SeaMonkey is not running.
>>>
>>>
>>> I've tried this for each active printer (after deleting the obsolete
>>> printers from prefs.js).
>>>
>>> Here's my new user.js file:
>>>
>>> # Mozilla User Preferences
>>>
>>> /* This file can be edited while Seamonkey is running; it will be copied
>>> into pref.js at next restart.
>>> *
>>>
>>> user_pref("print.printer_C2424_2x2.print_shrink_to_fit", true);
>>> user_pref("print.printer_C2424_double-sided.print_shrink_to_fit", true);
>>> user_pref("print.printer_C2424_plain.print_shrink_to_fit", true);
>>> user_pref("print.printer_C2424_recycled.print_shrink_to_fit", true);
>>> user_pref("print.printer_Samsung_CLP-550_Series.print_shrink_to_fit",
>>> true);
>>> user_pref("print.printer_WorkCentre_C2424_PS.print_shrink_to_fit",
>>> true);
>>>
>>> // default to "shrink to fit"
>>>
>>>
>>>
>>> Yet -- it doesn't work; selecting say 50% changes "true" to "false";
>>> restarting SM doesn't reset it to "true."
>>>
>>> Do you see anything in my user.js file that's wrong?
>>>
>>>
>>
>> The user.js file is applied only when SeaMonkey (or Firefox or
>> Thunderbird) is launched. If you change a settings via a user interface
>> (e.g., [File > Page Setup], [Edit > Preferences]), the default indicated
>> in user.js will be applied the next time SeaMonkey is launched (after it
>> is terminated).
>>
>
> And prefs in user.js are re-applied every time the app is launched.
>
> Whatever is in user.js is loaded into prefs.js. Hence, if you use the
> UI or about:config within the app to alter any pref contained in
> user.js, and you then close the app, the next time the app is launched
> specs in user.js will be loaded into prefs.js and over-ride any of those
> changes.
>
> So. If you do use user.js to alter your config, you should view using
> it as a permanent change. That is, until you delete user.js (or edit
> it), it will always over-ride anything else you do, either in the UI or
> even prefs.js.
>
> user.js, every time you run the app, re-writes those prefs in prefs.js.
>
> So, fine, use user.js. Just remember that any changes you make after
> that in prefs.js or the UI will be negated the next time you run the
> app. Unless you delete user.js or alter its contents.
>
>
That indeed is the point. The file user.js determines defaults to reset
temporary preference settings. The defaults are applied whenever
SeaMonkey is launched anew.
--
David E. Ross
I am sticking with SeaMonkey 2.26.1 until saved passwords can
be used when autocomplete=off. See
<https://bugzilla.mozilla.org/show_bug.cgi?id=433238>.
_______________________________________________
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey
