James G. Sack (jim) wrote: > Carl Lowenstein wrote: >> On 7/21/06, Michael O'Keefe <[EMAIL PROTECTED]> wrote: >>>>> network.http.max-persistent-connections-per-server >>>> Where do I find/change this? >>> about:config >>> >> OK, now we have found "about:config" again. Is there any way to edit >> it with a _real_ editor rather than whatever is built into >> Firefox/Mozilla. This file seems to accumulate values, and they never >> leave. So I have about 30 or 40 lines relating to a printer that is >> no longer part of my network. I can find them by searching "dj1600" >> but I don't seem to be able to select them all so as to perform a mass >> deletion. > > I'm guessing that about:config may be showing the union of factory > defaults, (possibly) system-wide defaults, and user overrides. > > There is a directory > ~/.mozilla/firefox/XXXXXXXX.default/ > which contains the user overrides in prefs.js > > There is also a directory > ~/.mozilla/default/YYYYYYYY.slt > which I suspect applies to the "mozilla" browser as opposed to firefox. > > Perhaps you can find satisfaction by closing firefox, and editing the > prefs.js file.
More info found at: http://kb.mozillazine.org/Firefox_:_FAQs_:_About:config_Entries Follow the link about user.js, where it talks about prefs.js I don't see any user.js in my system, but there is a prefs.js that contains items which firefox about.config displays with a status of 'user set'. OK, after a couple of experiments: 1. the recipe of creating a user.js file which will be applied to extend/replace prefs.js on firefox startup seems to work as advertised. I guess this means that changes to about:config settings provided by user.js would only apply to the current session, since applying user.js would revert those changes on next startup (not tested -- but I did verify that firefox seems not to touch user.js). 2. these files are javascript and must be valid (eg don't drop the ';') 3. editing prefs.js does work (if done while firefox is not running). Presumeably this is the only way to remove stuff. Removed stuff may then re-appear (with default values and status of 'default'), for those which are _required_, it seems. 4. Evidently 1,2,3 are subject to some sanity checking operations which may fix anything that is invalid of conflicts with a more inclusive setting. ..jim -- [email protected] http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-newbie
