On Thu, Oct 20, 2016 at 6:35 PM, Samuel Williams < space.ship.traveller at gmail.com> wrote:> it would be very nice if at least backslash escapes would be supported >They are supported just fine. In your first message you passed several option\\\=args to ssh, and it was *ssh* that gave you an error (it didn't like that it received a backslash as part of the option name). ..wayne.. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.samba.org/pipermail/rsync/attachments/20161021/4a74753b/attachment.html>
Wayne, I guess if you apply standard shell escaping logic you end up with a string which isn't processed correctly, yes, ssh complains, but only because Rsync passed the backslashes through without dealing with them. My opinion is that if Rsync is splitting a string based on whitespace it also needs to take into account backslashes.
On Fri, Oct 28, 2016 at 5:39 AM, Samuel Williams < space.ship.traveller at gmail.com> wrote:> Rsync passed the backslashes through without dealing with them. >Yeah, it only does space-splitting and that's all it will ever do. It still looks to me like there is a bug in the original escaping, since any command receiving that string is receiving a backslash that is not supposed to be there. It should only be escaping the string enough to get it to rsync, not trying to guess what rsync is going to do with it after it gets it. To work around that bug, you could consider using an ssh-calling shell script instead of manually specifying the ssh command and args to rsync. ..wayne.. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.samba.org/pipermail/rsync/attachments/20161028/2a3905e3/attachment.html>