about:support old printers, etc. not removed from preferences
Ran Garoo
In this case, PDFCreator has been removed as a printer months ago,
but all the following persists.
How does one (elegantly) delete all this stuff?
excerpt from about:support page
> Modified Preferences
>
> print.printer_PDFCreator.print_bgcolor FALSE
> print.printer_PDFCreator.print_bgimages FALSE
> print.printer_PDFCreator.print_command
> print.printer_PDFCreator.print_downloadfonts FALSE
> print.printer_PDFCreator.print_edge_bottom 0
> print.printer_PDFCreator.print_edge_left 0
> print.printer_PDFCreator.print_edge_right 0
> print.printer_PDFCreator.print_edge_top 0
> print.printer_PDFCreator.print_evenpages TRUE
> print.printer_PDFCreator.print_footercenter
> print.printer_PDFCreator.print_footerleft
> print.printer_PDFCreator.print_footerright
> print.printer_PDFCreator.print_headercenter
> print.printer_PDFCreator.print_headerleft
> print.printer_PDFCreator.print_headerright
> print.printer_PDFCreator.print_in_color TRUE
> print.printer_PDFCreator.print_margin_bottom 0.5
> print.printer_PDFCreator.print_margin_left 0.5
> print.printer_PDFCreator.print_margin_right 0.5
> print.printer_PDFCreator.print_margin_top 0.5
> print.printer_PDFCreator.print_oddpages TRUE
> print.printer_PDFCreator.print_orientation 0
> print.printer_PDFCreator.print_pagedelay 500
> print.printer_PDFCreator.print_paper_data 1
> print.printer_PDFCreator.print_paper_height 11
> print.printer_PDFCreator.print_paper_size_type 0
> print.printer_PDFCreator.print_paper_size_unit 0
> print.printer_PDFCreator.print_paper_width 8.5
> print.printer_PDFCreator.print_reversed FALSE
> print.printer_PDFCreator.print_scaling 0.3
> print.printer_PDFCreator.print_shrink_to_fit TRUE
> print.printer_PDFCreator.print_to_file FALSE
> print.printer_PDFCreator.print_unwriteable_margin_bottom 0
> print.printer_PDFCreator.print_unwriteable_margin_left 0
> print.printer_PDFCreator.print_unwriteable_margin_right 0
> print.printer_PDFCreator.print_unwriteable_margin_top 0
Ran Garoo
from prefs.js sufficient? Is there a better way?
Jay Garcia
--- Original Message ---
> I can see that prefs.js is editable. Is deleting this old stuff
> from prefs.js sufficient? Is there a better way?
>
Bottom posting is the preferred method here, thanks.
Removing the printer(s) from prefs.js is one way as long as you're
comfortable with editing the prefs.js fine - FF must be closed when
doing this.
However, the safest way is to do about:config and in the filter window
type "printer". All printers, past and present will be listed. Select
each line of old printers, right-click on the line and select "reset".
The next time you visit about:config, those lines will be gone.
--
*Jay Garcia - Netscape Champion*
www.ufaq.org
Netscape - Firefox - SeaMonkey - Thunderbird
Ron Hunter
The prefs.js file, like the Windows Registry, eventually becomes a
'dump' for things no longer needed. Obviously, a printer driver, when
uninstalled, has no interest in, or knowledge of, the Firefox prefs.js
file. In addition, many extensions put data there, and they also never
seem to delete anything. This is another reason to make a new profile
now and then. I used to recommend it every major version, but with the
rapid release program, that would be a bit of a nuisance.
There is effort being made to allow Firefox to clean up the prefs.js
file, but it is a few releases away, the last time I checked on it.
Ron Hunter
checks'.
Ron Hunter
> On 17.07.2011 08:54, Ran Garoo wrote:
>
> --- Original Message ---
>
>> I can see that prefs.js is editable. Is deleting this old stuff
>> from prefs.js sufficient? Is there a better way?
>>
>
> Bottom posting is the preferred method here, thanks.
>
> Removing the printer(s) from prefs.js is one way as long as you're
> comfortable with editing the prefs.js fine - FF must be closed when
> doing this.
>
> However, the safest way is to do about:config and in the filter window
> type "printer". All printers, past and present will be listed. Select
> each line of old printers, right-click on the line and select "reset".
> The next time you visit about:config, those lines will be gone.
>
Jay Garcia
--- Original Message ---
Tedious yes, but safer than messing with the prefs.js file if you're not
comfortable with editing it.
Jay Garcia
--- Original Message ---
> Actually, with Firefox closed, you can rename the prefs.js file, restart
> Firefox and it recreate a default version of the prefs.js file. This
> will insure that old cruft is removed but, perhaps unwantedly, remove
> preference overrides you or other existing add-ons may have set.
The implementation of user.js will more or less prevent the inadvertent
loss of prefs.js customizations.
Jay Garcia
--- Original Message ---
> My bloviated meandering follows what Jay Garcia graced us with on
> 7/17/2011 8:40 AM:
>> On 17.07.2011 10:38, Sailfish wrote:
>>
>> --- Original Message ---
>>
>>> Actually, with Firefox closed, you can rename the prefs.js file, restart
>>> Firefox and it recreate a default version of the prefs.js file. This
>>> will insure that old cruft is removed but, perhaps unwantedly, remove
>>> preference overrides you or other existing add-ons may have set.
>>
>> The implementation of user.js will more or less prevent the inadvertent
>> loss of prefs.js customizations.
>>
> Agreed, for personal preference overrides but maybe not so for unaware
> of add-on preferences?
>
AdBlock Plus, for example, adds several lines to prefs.js
Ran Garoo
I'm thinking that it is FF that puts the preferences in place during or
after some check of system devices that FF has an interest in. If so,
then it would make sense for FF to be able tp 'reverse' anything it
includes or, maybe, do a periodic check of system devices and revise
itself thusly.
do a line by line revisio of aabout:config is error-prone and more than
tedious.
Editing prefs.js seems simple enough as a temporary work around.
New profiles? Wouldn't that mean having to line by line prefs.js for the
mods I want?
Sort of a damned if I do, don't situation. I like your analogy to the
window registry dump. That's why I generally prefer portable apps that
are never allowed to touch the resitry. I would do portable FF except
that some extensions and plugins don't play noice unless they a resistry
to abuse.
I'll settle for editing prefs.js for now.
btw I bottom posted the addendum because it was an addendum meant to
save some less than useful replies. If only that ever worked.
Ron Hunter
The difference is that there are any number of good registry cleaners,
and no Firefox profile cleaners, that I know of.
Ron Hunter
> My bloviated meandering follows what Jay Garcia graced us with on
>> On 17.07.2011 10:52, Sailfish wrote:
>>
>> --- Original Message ---
>>
>>> My bloviated meandering follows what Jay Garcia graced us with on
>>> 7/17/2011 8:40 AM:
>>>> On 17.07.2011 10:38, Sailfish wrote:
>>>>
>>>> --- Original Message ---
>>>>
>>>>> Actually, with Firefox closed, you can rename the prefs.js file,
>>>>> restart
>>>>> Firefox and it recreate a default version of the prefs.js file. This
>>>>> will insure that old cruft is removed but, perhaps unwantedly, remove
>>>>> preference overrides you or other existing add-ons may have set.
>>>> The implementation of user.js will more or less prevent the inadvertent
>>>> loss of prefs.js customizations.
>>>>
>>> Agreed, for personal preference overrides but maybe not so for unaware
>>> of add-on preferences?
>>>
>>
>> AdBlock Plus, for example, adds several lines to prefs.js
>>
>
You should see the raft of prefs that WOT adds!