printing/storing about:config

[gNeandr]

Is there a methode/extension to print/store the "about:config" page or
part of it after filtering?

This relates to
Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:12.0) Gecko/20100101 Firefox/12.0

and
Mozilla/5.0 (X11; Linux x86_64; rv:11.0) Gecko/20120329 Thunderbird/11.0.1

[David E. Ross]

I do not know if the following is true in Linux.

For Windows, the complete "about:config" is the file prefs.js in your
profile. It is a plain ASCII text file that can be copied and printed.
You can edit a copy of the file (e.g., for printing), but users are
strongly urged not to edit the working base file.

--

David E. Ross
<http://www.rossde.com/>.

Anyone who thinks government owns a monopoly on inefficient, obstructive
bureaucracy has obviously never worked for a large corporation.
© 1997 by David E. Ross

[gNeandr]

On 06.05.2012 17:50, David E. Ross wrote:
> On 5/6/12 7:36 AM, gNeandr wrote:
>> > Is there a methode/extension to print/store the"about:config" page or
>> > part of it after filtering?
>> >
>> > This relates to
>> > Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:12.0) Gecko/20100101 Firefox/12.0
>> >
>> > and
>> > Mozilla/5.0 (X11; Linux x86_64; rv:11.0) Gecko/20120329 Thunderbird/11.0.1
>> >
> I do not know if the following is true in Linux.

Yes, it's true

> For Windows, the complete"about:config" is the file prefs.js in your
> profile. It is a plain ASCII text file that can be copied and printed.
> You can edit a copy of the file (e.g., for printing), but users are
> strongly urged not to edit the working base file.

AFAIK "about:config" can be different from the file prefs.js.
At least I see difference when I compare both. If I'm not wrong the
about:config may contain more items .. and those are important for me.

Any thoughts?

[Neil]

gNeandr wrote:

> AFAIK "about:config" can be different from the file prefs.js.
> At least I see difference when I compare both. If I'm not wrong the
> about:config may contain more items .. and those are important for me.

The bold items in about:config are saved in prefs.js, the other items
come from the application and possibly extensions. They may therefore
vary from version to version and user to user, however the bulk of them
can be found in all.js (in omni.ja).

--
Warning: May contain traces of nuts.

[David E. Ross]

Items not explicitly in prefs.js have default values. A preference
variable with a default value will generally not (will never?) appear in
prefs.js, but the Mozilla software detects its absence and assumes the
default value. For preference variables with default values,
"about:config" shows what the software will use.

You can "create" a preference variable with a non-default value. Then
it will appear in prefs.js. If you then change its value to the
default, it will be removed from prefs.js but still show in
"about:config".

If you wish to extract ALL preference variables shown by "about:config",
you need an extension that captures the "about:config" display. I just
tried, and the display cannot be printed. Thus, "printing" to a file
(e.g., PDF) will not work. Instead, you need something that will
capture the display as it is generated, not afterwards.

[gNeandr]

Am 07.05.2012 01:31, schrieb David E. Ross:
> If you wish to extract ALL preference variables shown by"about:config",

YES .. that's what I'm looking for!

> you need an extension that captures the"about:config" display.

That was my impression too ..

> I just tried, and the display cannot be printed. Thus, "printing" to a
> file (e.g., PDF) will not work. Instead, you need something that will
> capture the display as it is generated, not afterwards.

... and that finding was the reason why I asked .. and to find if there
is an extension already out.

Anyone knows about such an extension? Gives Mr.Tech such a support?