On 11/11/2009 8:49 PM, Hartmut Figge wrote:
David E. Ross:
[...]
Nice riddle. A challenge. *g*
Hm. MailNews doesn't matter for the about:config Display, so my first
step in examining this would be to rename the prefs.js, restart SM2 in
the browser with this profile and see, if the oddity
On 11/12/2009 7:10 AM, David E. Ross wrote:
On 11/11/2009 8:49 PM, Hartmut Figge wrote:
David E. Ross:
[...]
Nice riddle. A challenge. *g*
Hm. MailNews doesn't matter for the about:config Display, so my first
step in examining this would be to rename the prefs.js, restart SM2
I have four profiles in SeaMonkey 2, all of which I imported from
SeaMonkey 1.1.18. All four have the Default theme and the same set of
extensions.
When I request about:config for three of my profiles, the display is the
same as for SeaMonkey 1.1.18 with the Classic theme. For the fourth
David E. Ross:
What do I have to set for this fourth profile to have about:config the
same as the other three profiles?
Are there perhaps different userChrome.css in the chrome folder of the
profiles?
Or, you might have the same set of extensions, but are they also
configured equally?
And then
blocked by AdBlock Plus), I don't see them
affecting the about:config display.
And then there is the user.js. Hopefully, because changes to the
prefs.js via about:config are hard to remember. ;)
Except when testing the effects of changed preference variables, I
always use user.js if the [Edit
David E. Ross:
[...]
Nice riddle. A challenge. *g*
Hm. MailNews doesn't matter for the about:config Display, so my first
step in examining this would be to rename the prefs.js, restart SM2 in
the browser with this profile and see, if the oddity remains.
By the way, have you tested this profile
6 matches
Mail list logo
