Using exec to make it easier to debug a client or server in real-time.
Not everything is available via
xpra info or debug logging. (see also #2749)
This will allow runtime inspection and modification of the code.
Very useful, in particular for things like #2756.
xpra shell subcommand added in r26340, with server support only.
XPRA_SHELL=1 python3 /usr/bin/xpra start --start=xterm --bind-tcp=0.0.0.0:10000 -d exec
xpra shell tcp://127.0.0.1:10000 > print(server.get_root_window_size()) (8192, 4096) > exit
execthread (server could have debug enabled and printing lots of other unrelated stuff)
BlockingIOError: [Errno 11] write could not complete without blocking
shell-replypacket, use brotli?
r27425 allows individual server sockets to have the shell option enabled, ie:
xpra start :20 --bind-tcp=0.0.0.0:10000,shell=true --no-daemon --start=xterm
This will do for now, will follow up in #2872
this ticket has been moved to: https://github.com/Xpra-org/xpra/issues/2750