Thus said Stephan Beal on Thu, 08 Aug 2019 12:06:30 +0200: > fossil clone 'ssh://user@domain://path/to/"directory with > spaces"/my.fossil' my.fossil
Yes, that works, but it's a hack really because the user has to know that Fossil is using /bin/sh instead of simply calling exec() with appropriate arguments. In my opinion, Fossil really should not be using execl with /bin/sh here: https://www.fossil-scm.org/home/artifact?udc=1&ln=203&name=036510c48cbc9212 Instead, I think it would be preferable to do something like: https://www.fossil-scm.org/home/info/ce7baa9798de21aa Otherwise, Fossil will have to be enhanced to start quoting things shell-style so the user doesn't have to worry about anything more than quoting it in his shell. In other words, what Poor Yorick did by quoting the entire string should have been sufficient, but what he didn't know was that another level of quotes was needed because Fossil is going to pass it to another /bin/sh interpreter will will require additional quoting---surprise. Thanks, Andy -- TAI64 timestamp: 400000005d4c30ff _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
