Carlos E. R. wrote:
On 2017-06-22 01:13, L A Walsh wrote:
I've never seen this behavior.
Well, somehow that is not surprising. You customize a lot your systems, they depart too much from the standard.
--- Having a desktop running Windows, logging into a *nix machine isn't exactly what most people would classify as "customizing", though that I'm not running an X11 based browser on Windows _may_ be the reason I'm not seeing this behavior (I don't know of any X11 browsers that do run on Windows, offhand). Some of these crazy statements about what I run are baseless and often contrary to what is actually true. Just like someone from some suse list who thought I ran some "huge monolithic kernel" (no doubt trying to reference my, accurate, statements about sysd). It was also claimed I blamed sysd for every little problem: not only not true, but impossible as I don't run it. The _reality_ on the "huge monolithic kernel", with 8% of the loadable module total, built-in, my kernel was still 30% smaller than any of the kernels they were comparing it to. Too many people have misperceptions about my practices/setup that differ from reality which is unavoidable, but what is avoidable is them broadcasting those distortions to others causing no end of problems. You, Carlos, should know better.
That's different -- as it finds the firefox on the running machine.
Carlos is claiming this works across machines -- something I've never seen.
And we have proven that it is correct. I posted links to explanations and how it is done.
**remote control of unix mozilla**
[Borrowed from the 4.x x-remote doc]
--- The document(s) I can find about remote control (searching on your keywords) date back almost 10 years and don't mention firefox (ex.: https://www-archive.mozilla.org/unix/remote.html). It *seems* they may only be applicable to browsers run via X (which would exclude my Windows-based browsers).
«When Netscape Navigator is invoked with the -remote argument, it does not open a window, but instead connects to and controls an already-existing process. The argument to the -remote switch is an Xt action to invoke, with optional arguments.»
«Remote control is implemented using X properties, so the two processes need not be running on the same machine, and need not share a file system.»
What website did you get that from? I'd like to look at it -- who knows, I might be able to use a working X11 setup to do that to proxy commands into a non-X environment. (though it also might be too much work). -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org