Tested as part of #1894. Running:
Fires up xpra as expected, but it actually does not connect anywhere.
The URL handling code was originally added in r12380.
This does work (as expected - only trimming the connection string):
/Applications/Xpra.app/Contents/MacOS/Xpra attach xpra+tcp://HOST:PORT/
This does fire up the launcher:
open -a Xpra.app
And these fire up the launcher with the URL string (though there are parsing problems?):
open -a Xpra.app xpra+tcp://HOST+PORT/ open -a Xpra.app xpra://HOST+PORT/
So does this:
Maybe macos needs a reboot or something, because previously the same open command wouldn't get to the point of showing the launcher..
Going through the launcher for handling URLs has one advantage: we have a GUI for showing connection errors and URL problems, but there is also a problem with it: the global menu shown is the one for the launcher, not the full one - as per #1385.
this ticket has been moved to: https://github.com/Xpra-org/xpra/issues/1905