Wolfgang Rosenauer wrote:
Hi,
Am 10.12.2010 18:02, schrieb James Knott:
Yes, I usually have Firefox and/or Seamonkey running. However, why should an app on a remote computer open the same browser on the local computer? I'm running that app remotely, because I want to do something on that remote computer. In this instance, it is to install software on that remote computer. If this is some genius's idea of a "feature", I'd like to know how to turn it off, as it's worse than useless. BTW, this is a fairly recent thing, as it didn't work that way a few years ago.
This feature is soooo old. It actually got ported from Netscape 4 to Mozilla many years ago. I think the reasoning was completely different. http://www.mozilla.org/unix/remote.html
Yes, the ability to send an URL to a running Mozilla via X's ICC is old. That it's the default action of the respective commands (seamonkey or firefox) has been introduced by Mozilla, though.
That it misbehaves for non local sessions is a side effect and caused by X's network transparency (again I guess).
No, definitively not. That behaviour is not a side effect, but explicitely coded this way by the Mozilla developers: Mozilla checks for a running browser on the running X server. If it detects one, it sends the request to open a new window, with the argument URL. -no-remote, which you mentioned, skips that initial check. Joachim -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Joachim Schrod Email: jschrod@acm.org Roedermark, Germany -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org