Context Navigation

Changes between Initial Version and Version 1 of Ticket #223

Timestamp:

12/13/12 18:25:28 (8 years ago)

Author:

Antoine Martin

Comment:

I was thinking of doing exactly what you are suggesting.

I don't think this will fit in 0.8, but maybe.

Ticket #223
- Property Status changed from new to accepted
- Property Milestone changed from future to 0.9

initial	v1
1		I usually start my xpra sessions from the client, using ssh and --start-child=«cmd». Currently this requires using "ssh «host» xpra start :«display» --start-child=«cmd»", and if «cmd» includes spaces and/or " or ', the extra escaping needed is butt-ugly, and easy to get wrong. I'm currently solving this by using an doubly escaping shell script, but it should really be internal to xpra, using the same display syntax as a remote attach (eg xpra start ssh:«host»:«display» --start-child=«cmd»).
	1	I usually start my xpra sessions from the client, using ssh and {{{--start-child=«cmd»}}}. Currently this requires using "{{{ssh «host» xpra start :«display» --start-child=«cmd»}}}", and if {{{«cmd»}}} includes spaces and/or " or ', the extra escaping needed is butt-ugly, and easy to get wrong. I'm currently solving this by using an doubly escaping shell script, but it should really be internal to xpra, using the same display syntax as a remote attach (eg {{{xpra start ssh:«host»:«display» --start-child=«cmd»}}}).
2	2
3	3	Bonus points if would be possible to start a session and attach to it using a single ssh session, so that a user only has to supply his password once for this common use case. That would probably need a new "start-and-attach" sub command that accepts any options accepted by either "start" or "attach".