start-child drops command line arguments

[Antoine Martin]

Example:

xpra start ssh:localhost:10 --start-child="xterm -bg blue"

Should start a blue xterm... but instead we find:

ssh -T localhost sh -c \
    'xpra initenv >> /dev/null 2>&1 || echo "Warning: xpra server does not support initenv" 1>&2; \
     ~/.xpra/run-xpra _proxy_start :10 '--start-child=xterm -bg blue' --dpi=96'
sh -c xpra initenv >> /dev/null 2>&1 || echo "Warning: xpra server does not support initenv" 1>&2; \
    ~/.xpra/run-xpra _proxy_start :10 --start-child=xterm -bg blue --dpi=96
/bin/python /usr/bin/xpra _proxy_start :10 --start-child=xterm
/bin/python /usr/bin/xpra start :10 --start-child=xterm

The quotes are correct when we call ssh, but by the time sh is run, the quotes have been stripped?

Related to #632.

[Antoine Martin]

Works for me with r7520.

I've tested:

• the command in this ticket
• xpra start ssh:localhost:44 --start-child="xterm" --start-child="xeyes"
• as above but with a start-child entry in xpra.conf (checking for #632 regressions)

@onlyjob: can you break it? Do you think this is suitable for v0.14.x?

[Antoine Martin]

Backport for v0.14.x was in r7529. Closing.

[Antoine Martin]

Apparently, this may cause problems with tcsh: ​Ambiguous output redirect

[Antoine Martin]

This should be fixed in r7912. Needs backporting.
Keeping this open until then to make sure we don't somehow break / miss something.

[Antoine Martin]

Backported in r7926.