Jeff Lindsay
Jeff Lindsay
Yeah I don't think issues are the best place for these. Maybe a wiki page or perhaps you could start a blog with these posts? On Sunday, January 18, 2015,...
I generally don't like `set -u`, but I do like `"${foo:?}"` when needed.
Interesting. Where can I get the specifics of how this works?
Cool. This sounds like a good tip that some people might want to wrap in a more explanatory function if they use it a fair amount in their script.
Actually, can you give some examples where it's useful to be serializing... including the xargs example, but specifically other cases.
I think I understand what you mean, but some real examples to point me at would be helpful.
Yeah, I get the second two, but I was pretty sure it's unnecessary for the first case as long as it's quoted `"$@"`
So that is a special case for SSH wonkiness.
Alright, I'll have to try this more to internalize it. I believe you're right that it is the right way to universally serialize command line arguments though.
So I tried replacing this line: https://github.com/gliderlabs/herokuish/blob/master/include/procfile.bash#L21 With: ``` unprivileged /bin/bash -c "$(printf '%q' "$@")" ``` And it was unable to run the commands. Why didn't it work?