If you too, find the following usefull, i can sit down and write a patch for it: for instace: If you set plain "firefox" as your default browser in kcontrol and open a link via konversation your old location on the web will be gone, because no new tab/window was opened. Since firefox as the -remote option, it is possible to make it open a new tab/window instead of "overwriting" the old one. The problem is the following: "No running windows found Error: No running window found firefox-bin exited with non-zero status (2)" It should not be too hard to write a handler for this in mozilla-launcher via using the firefox -remote "ping()" command, so if no running window is found we can fallback to opening a new one. you see? Reproducible: Always Steps to Reproduce:
I may be misunderstanding you - my apologies if so. What mozilla-launcher does is use xremote if a currently running window is found, and starts a new one if not, just as you requested. As for controlling overwriting of the current window/tab or causing a new one to open, it just honors whatever preferences you've got set for firefox/mozilla (refer to bug #82653). In Firefox, see "Edit/Preferences/Advanced/Tabbed Browsing/Open links from other applications in..." Personally, I use the Tab Mix extension (http://tab-mix.info.tm/) to give me finer control. When I open links from other apps (I haven't tried konversation, but I do use other KDE apps), mozilla-launcher opens new tabs for me, because that's how I have my firefox/Tab-Mix prefs set. I *think* the same would be true if I weren't using Tab Mix.
You're right, bug's invalid. Thanks. Seems like i missed this setting in preferences...
