[winswitch] XPRA Launcher CLI options and config files

xpra at zellners.com xpra at zellners.com
Sun Mar 19 20:26:00 GMT 2023


When using xpra_launcher with a config file ie: xpra_launcher 
/home/me/connect.xpra

Does this file OVERRIDE any other CLI options being used?

ie:
xpra_launcher --speaker=off /home/me/connect.xpra

Tried that.. still connected with audio active

IF I move the option to the connect.xpra file it disables audio being 
active...

Not a big deal, just figured I could add what I wanted to the CLI 
option.. versus the file...

I read this:
https://github.com/Xpra-org/xpra/blob/master/docs/Usage/Client.md

And noting this:
Any command line option can be specified in this file by removing the -- 
that precedes options when they're used via the command line. ie: 
--min-quality=50 becomes just quality=50.

And: man xpra_launcher
  When called without FILENAME, xpra_launcher will spawn a GTK window 
allowing you to set the connection parameters easily.  If FILENAME is 
specified, the parame‐
        ters  in  the  GUI  will  be  set  to  the values specified in 
the session file. Additionally, if the session file contains the special 
parameter "autoconnect",
        xpra_launcher will skip displaying the parameters window and will 
establish the connection directly.


Doesn't spell out that the XPRA file overrides any CLI options, but it 
appears so...

Again, not a big deal.. just wanting to confirm .. thats all... Since my 
clients all now are current to support audio, I have cases which I don't 
need/want audio.... again.. not a big just trying to confirm XPRA file 
overrides any CLI options, or if not then a bug?

Thanks.


More information about the shifter-users mailing list