On Wed, Apr 11, 2007 at 05:01:40PM -0500, Matthew R. Dempsky wrote: > On Wed, Apr 11, 2007 at 04:33:32PM -0400, Nick ! wrote: > > Karel, single quotes cause backslashes to be backslashes, instead of > > escape chars (*except* if it's a backslash in front of a single quote, > > so that you can escape single quotes to include them). > > No, backslashes have no special meaning inside single quotes. > > $ echo '\' > \
indeed. i'll add the verbose <G> : maybe nick ! just forgot to mention that that is only relevant in the situation where you're chuggin' along using single quotes and then want to escape one of them, so therefore have to close your currently-open single quote and then use the \' jobby out in the open, and then probably start another singlequoted string :) $ echo '$RANDOM'\'x"'$RANDOM" would yield: $RANDOM'x'????? where ????? is some number; as one doesn't need to escape the single quote inside double quotes because everyone knows double quotes have TWICE THE POWER! back on topic; i had the impression that the filenames had to be relevant to whatever host they were supposed to be relevant to, and that there was a natural layer of escaping that would have to take place. file "a b" doesn't need to have its space escaped locally, it's just when it has to be referenced by name on the remote side; so maybe looking at it like that it is more sensible? -- jared
