3 ms·

Since xpra takes a sub-command as the first arg it's more like: : xpra_cmd="$1" shift exec /usr/bin/xpra "$xpra_cmd" --ssh=ssh "$@" And I don't see ho

Since xpra takes a sub-command as the first arg it's more like: : xpra_cmd="$1" shift exec /usr/bin/xpra "$xpra_cmd" --ssh=ssh "$@" And I don't see how that helps with using the GUI (like the comment I replied to). Also, defaults matter.

totaam 2y ago
No, the subcommand does not need to be the first arg.
kragen 2y ago
can't you put the flag before the subcommand? and can't you pass the flag when you launch the gui? i haven't been using it lately so i don't remember defaults do matter, but defaults can be changed. if it only takes a four-line shell script to change them, they don't matter much
- aidenn0 2y ago
  > can't you put the flag before the subcommand? The manpage implies you can't, but I tested and you can. > and can't you pass the flag when you launch the gui? I just tested and passing the flag when you launch the gui has no effect.
  - totaam 2y ago
    If you don't want to change the global defaults (in `/etc/xpra`), or your personal config (`~/.config/xpra`), you should be able to stick `ssh=ssh` in a `$HOST.xpra` session file and the launcher should honour it when you open the file / double-click on it. (add `autoconnect=true` and the launcher won't be seen unless the connection fails)
    - kragen 2y ago
      thank you for sharing your expertise!
    - aidenn0 2y ago
      Thanks for sharing multiple solutions; I'll try the configuration setting tomorrow.
  - kragen 2y ago
    hmm, that last item seems like a pretty serious flaw; it makes the default matter a lot