Slashdot Mirror

Undoubtably MathML support is there because it is in Mozilla. Between Mozilla, Netscape, and IE (with MathPlayer), all of the major browsers will support MathML. That together with support from math programs such as Mathematica, it really looks like MathML will finally become real this year.

There's a conference on MathML at the end of June this year. Leslie Lamport (LaTeX fame) and Roger Sidje (who did the MathML support in Mozilla) are among the invited speakers.

Undoubtably MathML support is there because it is in Mozilla. Between Mozilla, Netscape, and IE (with MathPlayer), all of the major browsers will support MathML. That together with support from math programs such as Mathematica, it really looks like MathML will finally become real this year.

There's a conference on MathML at the end of June this year. Leslie Lamport (LaTeX fame) and Roger Sidje (who did the MathML support in Mozilla) are among the invited speakers.

would not letting Aqua draw the interface make Netscape/mozilla pop-up more quickly?

A browser with an MDI interface is nothing new. Mozilla has had it for what seems like years, as has Opera. I don't use Mozilla much (read:ever) but I'm a big fan of Opera. It has a raft of nice touches besides the MDI interface, such as Mouse Gestures, a saved window setup (loads the pages you want on startup), popup blocking, browser impersonation, privacy options, etc. Not to mention web sites actually look identical to IE in most cases as opposed to Netscape's we-screwed-it-up-in-version-4-and-are-too-lazy-to- fix-it-now CSS implementation.

Ummm.... Try downloading the Netscape version (at least not the IE version) of the plugin. Run that, and point out the Mozilla directory for the install.

As for the java, why don't you just read the Release Notes?

"If Java doesn't work, make sure the following is true:
On Windows:
Copy the NPOJI610.DLL from C:\JDK*\jre\bin to "\plugins" directory of your installation."

Remember... it's not Mozilla that's installing the plugins. It's you. Make sure you're installing them correctly.

Agreed. Have you looked to see if anyone requested this already in bugzilla?

Some other useful customizations can be found at http://www.mozilla.org/unix/customizing.html

For example, this is also good vs popups:
user_pref("dom.disable_open_click_delay", 1000);

Try Ctrl+PgUp and Ctrl+PgDn. You can find other shortcuts here:
http://www.mozilla.org/projects/ui/accessibility/m ozkeylist.html

Of special interest (to me) are:
Ctrl+T - New tab with focus in location entry box
Ctrl+W - Close Tab

Regards,
Stephen

It's a simple matter of creating a bookmark for a URL with the 'variable' section of the URL replaced with '%s' - so the URL for a google search would be: 'google.com/search?q=%s'.

(And a google newsgroup would be: 'groups.google.com/groups?group=%s').

Using the bookmark manager, right-click upon the bookmark and select properties. Choose 'Keyword' - and enter 'gg'

Now you can use 'gg foo' to go search for foo.

There's good documentation online here

And for those that haven't found it yet, enigmail should allow you to use GNU Privacy Guard with Mozilla, even under Windows. Haven't tried it myself yet.

If you are looking for cheap, maintainable, stable software to replace your current Windows environment, then look into this :

Slackware Linux.
KDE.
OpenOffice (maybe StarOffice or Hancom Office or KOffice).
Mozilla (or maybe Netscape 6 or Opera).
The GIMP.
XMMS.
MPlayer.
GNUCash (or maybe Kapital).
Evolution.
NEdit.

Or if you need anything else, check out Freshmeat.

Plan ahead. Change MS Office default file formats to friendly open formats now. Setup all servers to linux. Test users interest with Knoppix bootCD-OS. If Knoppix goes well with users install Win32 versions of favorite Open Source apps. Run your own audit of the company's win32 systems. Duplicate and convert propietary data files to open files (e.g., .doc to .rtf) by hand if you have to, but some folks may have automated it. Find special case win32 software needs, and see if wine will support. Then convert several users at a time, starting with the tech savy, and see if you can avoid mutiny. People have invested a lot of time learning one way, they hate upgrades, (remember the last of many Microsoft and Adobe upgrades?) so be patient when you upgrade your users to Linux desktop.

Changing MS Word users default Save file format to .rtf is easy. It will make all upgrades to OpenOffice much easier, and allow several version of MS Office to play nice, even if you don't upgrade. Years later you will be able to read old MS Office files, hooray!

As many have said:
Setup servers for windows file and print, web hosting, DNS, DHCP, and SMTP (samba, apache, bind, DHCPd and sendmail) in the back office. LEAF, LRP and CoyoteLinux firewalls are an easy place to start the conversion.

Try Knoppix BootCD-OS (debian) on every box, see if users can deal. It is complete Desktop with OpenOffice, Xmms, ogg-vorbis, Gimp, FreeCiv, and tons more on 700Mb CD-R. It auto-detects a ton of hardware, such as sound at each boot, and does not get installed to harddisk. It needs 128Mb Ram, or pagefile/swapfile/scratch disk on a box with less ram. If the user can't deal, eject the CD, and reboot back to MS Windows.

Setup each Win32 computers to run a script stored on a central server, at each boot. It saves a ton of work later.

Getting Win32 users into the OpenSource thing by installing Win32 OpenOffice and Mozilla on your current MS Windows install base. See how that goes with the users.

Convert your existing data from .rtf to .doc is critical. The user is a tease, no email or code! But it is an idea that should be packaged.

Run an audit on your Win32 systems. Get a file dump e.g., "dir /AH /ON /S > m:\filetreedump\box2tree.txt" on Win98, and goto to regedit and dump the registry to text file e.g., m:\filetreedump\box2reg.txt. Someone needs to write a nice perl based evaluation tool to audit what apps and software keys everyone in the Windows network is running.

Converting data is essential. Collecting data from users computer and registry, and inserting it into new email client, and Office apps should be automated, but no one has done it yet.

Wine testing for special apps is important.

After careful planning start rolling out conversions. This way you can convert data, support all the apps, and not loose users.

-Nathaniel

As reported on The Register, which was really a repost of an article from Compuwire, AOL has announced that in its next upgrade to their AOL client for Apple's OS X, it will use Netscape by default. (And just for those who want another link, Spider-Man is cool).

Most people (well, me) assume this means that AOL is using the Macintosh crowd as a testing base, then will make the same move on the Windows side of things by changing their PC client's default from IE to Netscape. The move won't really hurt Microsoft - it will still own 80% of the browser market, and since both Netscape and Internet Explorer are free, neither company will start having shifts of money.

But this isn't so much about money, as it is about control. AOL knows that their are two reasons Microsoft pushes Internet Explorer. Control of standards, and control of eyeballs. With every Windows computer that ships, it has Internet Explorer on it. And it's home page is MSN, Microsoft's media system.

Control the Eyeballs!

Netscape, by comparison, points to Netscape.com - which contains the collective linked knowledge to all things AOL/Time Warner. Links to news articles on CNN, Cartoon Network, and all else.

It's about the eyeballs. AOL wants you to see Time/Warner stuff, Microsoft wants those eyeballs to check out MSN. Both companies have a lot to gain by keeping your attention. AOL/Time Warner wants you to know all about their movies (like the upcoming Power Puff Girls movie, or their cable channels, or their electronic entertainment partnerships, or, just as important, keeping you signed up with AOL.

MSN has its wants, with its line of cable shows, plus all of the other Microsoft goodies, like Gamezone, Hotmail, Expedia and other services - which keep you plugged into the Microsoft system, and keeps those dollars coming in.

Control the browser, control the world

Just as important as the eyeballs is the technology that drives what they see. At last year's E3 (Electronic Entertainment Expo), AOl and Sony demonstrated using AOL on the Playstation 2 system, at the same time that Sony talked about running Linux on the Playstation 2. Now, almost a year later, Sony is getting ready to start shipping their hard drive/Ethernet/modem combo unit for $150. And AOL sees a large market place - one where there are more TV's than computers, and a $200 Playstation 2 in plenty of homes.

Odds are, Microsoft isn't going to make Internet Explorer for the Playstation system (not with their own Xbox on the market) - let alone for Linux. But since AOL has been sponsoring the creation of Mozilla, the Open Source browser Netscape is based on. Mozilla has been ported to nearly every operating system in existence - Linux, Macintosh, Solaris, and, of course, Windows. And across all operating systems, it provides the same look and feel - so now it doesn't matter what operating system you're using to surf the web/check your mail/chat with your friends on - Netscape looks the same. And you can bet it will be easy enough to develop and port to the Playstation 2 as well.

The implications could drive a shift of development. Suppose you're a web developer at this second, and you want to make sure people visiting your web page see all the whiz bang stuff. Right now, you spend most of your time making sure that Internet Explorer sees the page perfectly - then concentrate on the other browsers out there. Microsoft is happy, because to make sure IE looks the best, odds are you'll use Microsoft technology, which means you're spending Microsoft money (note: not Microsoft Money - different thing).

Netscape, being built on Mozilla, is HTML 4.0 standards compliant. That means that anything written for Netscape is certain to work with every other browser out there - including Internet Explorer (as long as Microsoft codes IE to be fully HTML compliant).

So now the web developer, in a post AOL-switching-to-Netscape time, has a new choice. Program your web site for IE, then for all the others - or make your web site HTML 4.0 standards compliant, and know that all browsers will render it correct the first time. There will still be questions about plug-ins (like those who like to use Flash enabled web sites, but by changing that over to Java, which runs on as many operating systems as Mozilla, developers can code around that hurdle. HTML 4.0 standards mean that anyone's tools can be used - Open Source, proprietary, or otherwise. Which means less money to Microsoft, and more power everyone else.

Maybe the move to Netscape won't change the world overnight, or drive subscribers to AOL. But it keeps the competition between the two companies alive.

And for most of us, competition is a good thing.

As always, I'm John "Dark Paladin" Hummel. And that's my opinion.

I have an iBook running OS X, and I've run at least all Mozilla versions 0.9.6 through 0.9.9, and I haven't seen Mozilla crash once in all that time. I also used multiple versions of Mozilla in OS 9 without many crashes (none that I can remember off hand, but that's been a while). Now that's not to say that Mozilla doesn't crash , I have seen it crash (mostly in Windows), just not on my iBook. I occasionally quit Mozilla due to its memory leaks it swells to use a large amount of swap space, but luckily with OS X's great VM it generally causes no problems, and doesn't slow down too much, so I leave Mozilla running constantly so I don't have to wait for it to start. I generally quit and reopen once a month. I leave my laptop on all the time, and just put it to sleep when I don't need it. The only problem that I have currently with Mozilla in OS X is that Java stopped working.(Bug 8337) I think that happened in 0.9.8. Prior to that Java had been working fine. I even downloaded the special beta plugin for Java, but I couldn't get it to work. It's probably my problem since I didn't try that hard, and I don't go to many sites that use Java anyway, but occasionally I find sometime that I need it. So that's only a minor annoyance for me.

Fixed from Mozilla 1.0RC2 upwards. Security advisory on www.mozila.org. I ignore Netscape but it is the same codebase - to be fixed already or at least soon.

Free Software needs you!

Download Mozilla NOW!

Why not eliminate those ActiveX problems altogether and use a browser other than IE?

... at least with OmniWeb (and presumably other browsers) where I can set up my own keywords

Mozilla has this, too. :) Works quite nicely, especially since I can just type "g something" to search Google, or "jargon something" to look up a word on Jargon File, etc.

Take a look at The nightly directory. Inside it you will find mozilla-i686-pc-linux-gnu-sea.tar.gz which is a nightly build with talkback enabled and it's not stripped. I'm guessing you haven't seen it because of the strange filename...

You should take a look a the Mozilla C++ Portability Guide. It's quite depressing.

Look at this: http://bugzilla.mozilla.org/show_bug.cgi?id=38488

I have been using it happily for ages.

RC1 has been causing the BSOD on my machine. There's a discussion in the group news://news.mozilla.org/netscape.public.mozilla.wi n32 - look for a thread started on the 4th May entitled "Win2000 system crashes with 2002050306-1.0 branch?". My contribution is here: news://news.mozilla.org/3CD6E0F6.C4C33025%40yahoo. com

There is also a bug on it. The bug has been marked as INVALID because the powers that be deemed it impossible for Mozilla to crash Win2K. If it's valid to your situatiom, please comment on it, and perhaps it will get re-opened.

Is anyone else using the same image acceptance settings and seeing anything similar?

Ah, my old pal the rcm-images freeze. Bugzilla is an awesomely useful community service -- see http://bugzilla.mozilla.org/show_bug.cgi?id=107806

There is a workaround: edit your permissions file manually to block (or enable if you want) rcm-images.amazon.com, which is the site that sends the malformed javascripted image code which causes the crash.

New stuff include support for "HTTP pipelining"

Not really. Pipelining has been sitting in Preferences --> Advanced --> HTTP since at least 0.9.8 (that's when I started using it). Pipelining definitely speeds things up, but it's a little bit buggy, which is why it's disabled by default.

I had this problem too. Got mine to work by uninstalling completeley and reinstalling. Checking out the first line in the Installation Notes does tell you to install into an empty directory and not over an old installation.

The easiest way to grab the nightlies is to go to Mozilla.org, scroll down to the bottom, look on the right hand side where it says:

"Nightly Builds Created most weekdays from the previous day's work, these will probably work, but maybe not. Use them to verify whether a bug you're tracking has been fixed. MacOS 9, MacOS X, i386 Linux, Windows, Linux PPC, Solaris, FreeBSD, Irix, BeOS, HPUX, OS/2, BSD/OS, etc"

and click on the link for the OS you are using. Or, you can look straight at the ftp directory here[ http://ftp.mozilla.org/pub/mozilla/nightly/latest/ ]

For the RC2 and Talkback enabled builds go to the releases page.[ http://www.mozilla.org/releases/ ]

The easiest way to grab the nightlies is to go to Mozilla.org, scroll down to the bottom, look on the right hand side where it says:

"Nightly Builds Created most weekdays from the previous day's work, these will probably work, but maybe not. Use them to verify whether a bug you're tracking has been fixed. MacOS 9, MacOS X, i386 Linux, Windows, Linux PPC, Solaris, FreeBSD, Irix, BeOS, HPUX, OS/2, BSD/OS, etc"

and click on the link for the OS you are using. Or, you can look straight at the ftp directory here[ http://ftp.mozilla.org/pub/mozilla/nightly/latest/ ]

For the RC2 and Talkback enabled builds go to the releases page.[ http://www.mozilla.org/releases/ ]

There was bug that can read local files, it is corrected in recent (read since 2002-05-02) builds.

See http://bugzilla.mozilla.org/show_bug.cgi?id=141061 for more.

Here are my thoughts:

By now I am sure most people have seen that Mozilla RC1 has been released .
The press has picked this up and now there are a number of reviews .



They all fail to compare RC1 to the last release (0.99) which leads to almost
all positive feedback.


The truth is that Mozilla really screwed up their release process. This is the
worst stable Mozilla build I have tested in the last year. They litterally
broke every rule in the book:


- They introduced major UI changes which are incompatible with all of the builds
since 0.80 or so.


- Saving files locally (at least on my system) is totally broken. Want to save
a PDF file locally? ... Too bad!


- They have completely changed around a lot of the preferences. Where did
these come from?


There are also numerous other small bugs.


RC1 should have been 0.99 with *only* patches to fix critical bugs. How many
release candidates do they expect to have?


Will there every be a Mozilla 1.0 or is it just going to be asymptotic to 1.0?

AFAIK, there is no talkback nightly for linux. There's no unstripped linux nightly either.

The place to report/suggest stuff like that is Mozilla's excellent Bugzilla.

There's actually a filed bug for seperate icons for the different components (Bug 47779). Sign up for Mozilla and vote for this bug. The more votes for a bug, the more "important" it is considered.
My guess is that this will only be fixed in 1.0.

Regarding your 'oingo' problem: I suggest you report it and see if that's a problem with the browser or something in the configuration.

The place to report/suggest stuff like that is Mozilla's excellent Bugzilla.

There's actually a filed bug for seperate icons for the different components (Bug 47779). Sign up for Mozilla and vote for this bug. The more votes for a bug, the more "important" it is considered.
My guess is that this will only be fixed in 1.0.

Regarding your 'oingo' problem: I suggest you report it and see if that's a problem with the browser or something in the configuration.

The place to report/suggest stuff like that is Mozilla's excellent Bugzilla.

There's actually a filed bug for seperate icons for the different components (Bug 47779). Sign up for Mozilla and vote for this bug. The more votes for a bug, the more "important" it is considered.
My guess is that this will only be fixed in 1.0.

Regarding your 'oingo' problem: I suggest you report it and see if that's a problem with the browser or something in the configuration.

From the release notes: "xxxxxxxx.slt is a randomly generated directory name. It's an important security feature."

Especially obnoxious are bugs like trashing the preference files on upgrades from Netscape. If they can't do that right, they shouldn't try to do it at all.

Especially obnoxious are bugs like trashing the preference files on upgrades from Netscape. If they can't do that right, they shouldn't try to do it at all.

I am not sure if you have tried this but there is a section in the release notes about using Mozilla with Junkbuster at www.mozilla.org/releases/mozilla1.0/#general

And here is the text for those too lazy to scroll down....

Mozilla needs to be configured to work properly with proxies such as Junkbuster that do not support the most recent HTTP specification. By default, Mozilla tries to use HTTP 1.1. To use Mozilla with a proxy that only supports HTTP 1.0, edit the HTTP Version from 1.1 to 1.0 in Edit | Preferences | Debug | Networking. (Bug 38488)

I had this problem a long, long time ago. If I recall correctly (which I might not) the problem is with junkbuster and not mozilla. I stoped using junkbuster a while ago, so I wouldn't know if your problem is the same as what was discussed. But read Bug report for bug 38488 for more information. As I recall, there was a way around it.

I think mozilla rules. Go mozilla.

Did you install on top of a previous install? If you did then remove that install and start fresh (you won't lose your profile, it's stored in a different location).
--Asa

Mozilla 1.0 RC 2 has just been released and is already available for download. This is what has changed from the previous RC. New stuff include support for "HTTP pipelining", something which can increase performance by 50%! (disabled by default, check the releases notes).

This was the story I have submitted, Slashdot staff is weird, really.. =)

Mozilla 1.0 RC 2 has just been released and is already available for download. This is what has changed from the previous RC. New stuff include support for "HTTP pipelining", something which can increase performance by 50%! (disabled by default, check the releases notes).

This was the story I have submitted, Slashdot staff is weird, really.. =)

Mozilla 1.0 RC 2 has just been released and is already available for download. This is what has changed from the previous RC. New stuff include support for "HTTP pipelining", something which can increase performance by 50%! (disabled by default, check the releases notes).

This was the story I have submitted, Slashdot staff is weird, really.. =)

There was no link on the release page, so I thought I would provide one...

We're going to get an RC3 too.

Site doesn't work in my zilla 0.9 installation, time to go to 1.01 on this machine.

But, I'm guessing there are a lot more machines reporting from the US of A, and I wonder how many of them are getting feeds with chinese hosts blocked out.

I'm having a Hank Senior moment.

Sure. Just about any UNIX desktop environment is as flexible as LiteStep. Roll your own...don't feel like you just need to use KDE or GNOME or something like that. I've got a rather nice desktop with sawfish, the sawfish pager, all status information being shown via gkrellm, and programs launched via the keyboard using xbindkeys. No GNOME or KDE flavoring necessary.

AfterStep is probably the closest in functionality to LiteStep, but I personally prefer Enlightenment if you're looking for flash, Sawfish if you're looking for functionality, and Black Box if you're looking for speed.

Steps in roll-your-own:

Choose a base desktop environment (keep in mind that you can just mix and match bits of them...I used to use the GNOME panel without the rest of GNOME, and a roommate uses GNOME apps with the KDE environment):
None
GNOME
KDE
ROX
foXdesktop
Perltop
Equinox
XFce
Once you've chosen a desktop environment (or the lack of one), and possibly removed the parts of it that you don't like (with GNOME, I wholeheartedly suggest trying it without Nautilus, possibly without anything but the panel), then you get to choose a dock. Your current desktop may or may not include a dock/panel/wharf.

If it doesn't, icedock provides an environment-independent wharf for the afterstep-style wharf system -- swallowing apps.
gkrellm (seems to be currently down) makes for a nice status-monitor style dock.
Or you can make your own impromptu dock...I've built them before by starting xload and xlock with proper geometry arguments to stack them on top of each other, and having sawfish make the windows sticky and slap 'em at the edge of the screen.
Now a window manager. There are so many of these that I'm not going to list them all. I'll mention a few notables:
sawfish is a fairly fast, *extremely* flexible (everything's written in lisp, much like emacs) window manager that uses gtk. Currently GNOME's default. I love this thing, but it doesn't come with a pager, so you either need to use a base desktop environment with a pager or use spager.
enlightenment is, at least until the next major release, still a window manager and not a desktop environment. Lots of emphasis on eye candy.
ion, a novel window manager that's designed to be managed entirely with the keyboard and never overlap windows.
blackbox is what I'd suggest if you needed a fast environment that still looked nice.

Most WMs support launching programs with given key combinations. I'd advise against this. The excellent XBindKeys is window-manager independent, quite capable, allows you to kill off your window manager and still use keys to start programs, etc. Plus, there's a nice benefit to using a different program than your window manager to launch programs. If you never launch external programs with your WM, you can renice -10 `pidof sawfish` or whatever your window manager is. Making your window manager (and X) meaner with respect to CPU scheduling makes for a much more snappy environment when edge flipping or the like. Sure, it might take a sec for the mozilla windows in the background to finish redrawing when I flip to a new desktop, but in the meantime I can do my work without waiting around for them.

The reason you don't want to make your WM meaner if you use it to launch programs is that then all the programs will also be equally mean.

Decide on the Big Four applications of any X desktop. Text editor, web browser, file manager, and terminal emulator.

Text editor:
I can't possibly cover this holy war here. My personal preference is xemacs, which is a bit of a learning curve for new users from Windows, but well worth it in power in the long run. You may want something that meshes more with the rest of your chosen desktop environment.

Web browser:
Just because KDE uses Konqueror and GNOME uses galeon by default is no reason to stick with those. Of course, you also can use either Konq without KDE or galeon without GNOME. You're rolling your own environment!
mozilla is now (after years of work) a good web browser. Big, still slow and still RAM-hungry, but usably so.
dillo Lightweight, very fast, pretty stable, very screen-space efficient...I can't say enough good things about dillo. If you use dillo as your primary browser, be aware of the fact that it has fewer features than the large browsers, that it doesn't currently (without a patch) support SSL, that it uses a UNIXish config-file preferences interface, and that it doesn't lay out nested tables or wrap text around images the same way Mozilla does. I keep Mozilla around as a backup browser, but dillo is so freakishly fast that it's hard to want to use anything else.
There are a few other browsers, but Konqueror, Mozilla, and dillo are (IMHO) the big GUI players on Linux. Amaya is a specialty browser, Opera (thanks to its MDI interface) doesn't seem to have caught on much in the Linux world, and Navigator 4.x is definitely on its way out the door.

File manager:
You may choose to simply use a command-line shell and the standard file utilities (cp, rm, ls) to do your file management -- I do, and I've tried hard to give other things a chance. But if you prefer to use a specalized GUI tool:
Konqueror can be used, even if you aren't using KDE (you do, of course, need the KDE libraries installed). Faster than gecko (the engine in mozilla and galeon) and almost as standards compliant, Konqueror has a lot of fans.
GMC is no longer being developed, but it's a reasonable lightweight interface.
Nautilus, the current official GNOME file manager is big, slow, RAM-hungry, and pretty. Not sure how well Nautilus works outside of GNOME (given that Konqueror can work outside of KDE, I would expect this capability of Nautilus).
ROX filer is a very fast little gtk file manager.
There are a lot of file managers out there, so I won't list them all, especially as I'm happy with just bash and the POSIX tools.

Terminal emulator:
GNOME and KDE both come with terminal emulators -- gnome-terminal and Konsole. I'm not very impressed with either -- they're both very slow and aren't available apart from their associated desktop environment. Konsole supports tabbed terminals, which some people may like. Both of them are fairly easy to configure, and are suitable for newbies to work with.
Multi Gnome Terminal extends gnome-terminal significantly with Konsole-style tabs and a set of other features. If you like gnome-terminal, you should probably consider using this instead.
Eterm is a RAM-heavy terminal emulator that was designed to look nice. For all the tinting and blending it can do, reasonably fast.
Aterm seems to be basically a less featureful, less memory-hungry Eterm-like terminal.
xterm is the reasonably fast not-so-pretty fairly RAM-hungry terminal that's used all over the world.
rxvt is easily my favorite terminal emulator. rxvt uses less RAM than anything else out there, and is incredibly fast. You can compile in only the features you want to use (which can, of course, also be disabled at runtime). Background images are supported, but emphasis is not much on eye candy. Very configurable. The biggest drawback is that configuration is through traditional UNIX methods, which may scare away some -- X resources, command line options, compile-time options.

Whatever you do, choose a set of software that you like, and remember -- your desktop environment is based on Linux, which means it should composed of exactly the parts that you like most. Have fun!

This keywords feature under Mozilla is one of the most understated features I've ever seen. IMHO, it is just as good as tabbed browsing in terms of usefulness. For example, take the word banana. Look at what I can do by using keywords, Mozilla, and just typing in the URL bar:

g banana -- Search Google for the word banana
gg banana -- Search Google Groups for the word banana
d banana -- Look up a definition for the word banana
t banana -- Look up banana in Roget's Thesaurus
ef banana -- Translate the word banana into French
fe banane -- Translate the French word "banane" into English, "banana"

The keywords feature is totally customizable and expandable for just about any site that uses forms. (Although I'm sure that there are some sites out there that use dynamic hidden fields to prevent this type of action.) Check it out.

Setting this pref (instructions here) should turn off pop-up and pop-under ads that use the onload handler of tags to work around our previous window.open() filter. (Bug 92955)
user_pref("dom.disable_open_click_delay", 1000);

Setting this pref (instructions here) should turn off pop-up and pop-under ads that use the onload handler of tags to work around our previous window.open() filter. (Bug 92955)
user_pref("dom.disable_open_click_delay", 1000);

Setting this pref (instructions here) should turn off pop-up and pop-under ads that use the onload handler of tags to work around our previous window.open() filter. (Bug 92955)
user_pref("dom.disable_open_click_delay", 1000);