Question #215356 on Duplicity changed: https://answers.launchpad.net/duplicity/+question/215356
edso posted a new comment: On 27.11.2012 19:11, edso wrote: > Question #215356 on Duplicity changed: > https://answers.launchpad.net/duplicity/+question/215356 > > edso posted a new comment: > On 27.11.2012 18:56, Will Torres wrote: >> Question #215356 on Duplicity changed: >> https://answers.launchpad.net/duplicity/+question/215356 >> >> Will Torres posted a new comment: >> i forgot to mention, this is through cygwin :P >> >> i wonder if cygwin path expansion is doing something funky. >> > > nope. just doublechecked.. > > A. the splitting occurs already before parameters are given to python > B. eval seems to be the workaround (that's also what i do in duply) > > see also > http://stackoverflow.com/questions/9982573/pass-shell-escaped-string-of-arguments-to-a-subcommand-in-bourne-shell > > ..have fun.. ede/duply.net > also here is some more nifty background http://www.greenend.org.uk/rjk/tech/shellmistakes.html the following seems to be a way around using the potentially unsafe 'eval' set -- '--foo' 'bar baz' 'qux' command "$@" of course you should have interpreted all parameters befor overwriting them in your script. --ede -- You received this question notification because you are a member of duplicity-team, which is an answer contact for Duplicity. _______________________________________________ Mailing list: https://launchpad.net/~duplicity-team Post to : [email protected] Unsubscribe : https://launchpad.net/~duplicity-team More help : https://help.launchpad.net/ListHelp
