Version: (using KDE KDE 3.5.2) Installed from: SuSE RPMs The long story is here -- https://bugs.kde.org/show_bug.cgi?id=126961 but to summarize all of this: I work this way that I would like to open all URL links I see (in Kmail, or KNode -- in future) and see the content later. And in all cases the most suitable application (for me) is the web browser (currently -- Konqueror). Thanks to web browser I can be sure that: * all documents are opened in one place (one window exactly, since I use tabbed view always) -- the web browser * all errors will be reported in normal fashion and no URL link will be missed * all URL addresses will be visible and easy to manipulate (copying, changing typos, etc). However, today when I click on URL link in KMail (for example) KMail opens small window with some process which connects to the server and it decides what to do (in almost every case it is really --> web browser). So -- first, it looks like overkill to have additional flying windows to do what was obvious for the user in the first place, the second -- it is not really productive (all those windows, and lack of all of the features mentioned above). Such option would be a great help and time-saver. In other words, for me it means more efficient workplace. Of course someone could argue to improve current "URL launching" to shape it like KGet -- one global list, status info, copying, editing features, etc. And I agree -- it would also be a big help, two issues however: a) it means a lot more changes b) it is still one app more in the chain "URL link -> web browser" instead "URL link -> KRun(?) -> dedicated application".
There is yet another issue which makes the current design counterproductive. If you click on such several links, and you go to browser first tab and you try to work you will be auto switched each time new address kicks in. So the current design force user to wait for all links to be opened. Working is possible but inefficient.
Not everything can be viewed in a web browser. This option would introduce breakages, when clicking on a link to a type of document which doesn't have a KPart. Or when the preferred webbrowser isn't konqueror. With konqueror you would get an empty tab offering you to launch an application - not really an efficient way to do this. The "flying window" effect is solved by the default job notification stuff being in plasma nowadays. Although I personally still prefer the flying windows ;)
Sorry, I was wrong, there is actually a way to do this. When you configure a Browser Application in the component chooser, all HTTP urls are sent to it. You could just configure Konqueror (or kfmclient openURL) as the browser application.