Slashdot Mirror
The Secrets of Firefox about:config
jcatcw writes "While Firefox is very customizable, many of its settings aren't in the Options. Each setting is named and stored as a string, integer, or Boolean in a file called prefs.js and accessed via about:config from the nav bar. Computerworld provides instructions on 20 tweaks for speeding up page loads, making tabs behave, reducing memory drain, and generally making the interface act the way you want it to. Customization also comes through the must-have FF extensions (but be sure to skip these)."
here
try this setting:
browser.xul.error_pages.enabled
set it to "true"
Did you know that "FTW" ("for the win") is a direct translation of "Sieg Heil"?
Well, a lot of these "tweaks" will have negative effects.
Example: nglayout.initialpaint.delay as 0. This will slow rendering of the page as it causes reflows. Fools.
http://kb.mozillazine.org/About:config_entries
Sigs are too short to say anything truly profound so read the above post instead.
...works really well if you first watch the video you want to download, putting it in your cache. Then going to video downloader, and regardless of the file size, takes just a few seconds and you are done. Apparently it can grab it from your cache and make it a file on you system (very little for it to really do - very low bandwidth to convert).
In fact, it seems to me that when it doesn't work, "service not available" only happens when I don't watch it first, not in my cache.
That's why I prefer Opera. If you think Firefox is bad, try it on OS X.
I think this is what you want:
http://www.firefoxtutor.com/39/loc-bar-search/
And really, they should have called Iceweasel IreOx, at least until mozilla.org asked them to stop.
Nerd rage is the funniest rage.
From RFC 2616 (HTTP/1.1) section 8.1.1:
You can configure many settings in Thunderbird using a similar interface. However, in Thunderbird you can get to the config section from the Options menu Advanced tab. I have reduced the size of the attachment icons this way. set mailnews.attachments.display.largeView to False.
#bookmarks-menu .bookmark-item .menu-iconic-left {
display: none !important;
}
Slashdot Classic
It isn't faster for everybody, it doesn't work with all servers...
Nerd rage is the funniest rage.
This is a tactic spammers use with mail servers. It's rude, annoying and breaks the rules/protocol.
RFC 2920 is the SMTP extension for pipelining. Pipelining is a perfectly valid strategy to reduce the time it takes to send mail by reducing the number of round-trips.
What's rude is violating the RFC that says that certain round-trips are required and the spammers tend to violate those rules (such as asking if a message body can be sent before actually sending it, and waiting for the server's introduction message before the client introduces itself). Pipelining itself is actually quite good.
I won't comment on HTTP pipelining because someone else did already.
Hee.
Too busy staying alive... ~ R.A.
Some, sort of. Example: network.http.pipelining.maxrequests has a maximum 8, if you set it to a higher value it will just use 8; and yet people will claim they see a difference in performance. Other "performance tweaks" lists floating around have settings that are no longer used or that don't do anything like what people seem to think they will. Of course, the same goes for windows tweaks, compiler options, linux kernel /proc settings, etc.
Set "keyword.enabled" to false.
about:config
change from true to false on the two following items:
browser.chrome.favicons
browser.chrome.site_icons
Politics is Treachery, Religion is Brainwashing
In Firefox 2.0.3, I opened up the DOM inspector, chose the main window, and started drilling down in to the element tree: I found the icons which you loathe.
Open up userChrome.css (in your profile: [profile dir]/chrome/).
In it, the following CSS rule should work to hide the icons:(This selector appears in chrome://browser/skin/browser.css, if you know where that is).
If it's valid behavior according to the protocol, and it's faster, and it's not bad nettiquette, then why, pray tell, isn't it on by default?
Because some servers violate the protocol by responding incorrectly to pipelined requests. At least, that was the reason 2 years ago.
The shareholder is always right.
"Scud Storm!" -- Jeremy of PurePwnage.com
Did you even bother to try it out? Camino's about:config page is almost identical to FF's page. Any options that are named the same in Camino as in FF will do the same thing. (Camino is just a different front end on Gecko, and about:config options are almost all Gecko options, not browser specific.)
opera:config
about:config options related to the Firefox UI (e.g. tabs, but also other features that necessarily have a different implementation) will generally have no effect in Camino. The reason they show up at all is that purging them would be a lot of work. However, most options dealing with page rendering, javascript, etc. work the same across all Mozilla browsers. As for the missing browser.tabs.closeButtons (and undoubtedly others), the latest Camino release is from a branch made long before the introduction of said options.
The list of about:config entries has lots of info on what the various options do, and some of the detail pages specify whether the pref has an effect in Camino. I can't vouch for the thoroughness of the "has an effect in" sections however, and AFAIK there's no list dealing just with Camino-compatible prefs.
Yes.
MozillaZine Knowledge Base Article on about:config entries
It is the first page Google finds when you search for "about:config". I'll let you decide whether that's easy to find.
If there wasn't, you'd be able to put it in the Knowledge Base yourself.What a fool believes, he sees, no wise man has the power to reason away.