> \052 is '*', and that substitution happens before the wildcard check--which is
> what's causing your issue since it matches the next entry `foobar'.
So, as I read the code, the logic was
1. expand escape sequences
2. if there's an asterisk, a questian mark or a left square bracket,
set the magic flag.
and your patch swaps 1. and 2.
But that would mean that in "foo\052bar?", the \052 would still be treated
as a glob wildcard, no?
EF> Err, what? Are you saying what it currently does is treating the
EF> on-filesystem filename foo*bar as a wildcard pattern?
RVP> Yes.
What I meant is when comparing a spec to an on-disc structure with a file name
that happens to contain octet 2A, whether that on-disc file name is considered
magic (whatever that means). I sincerely hope that's not the case.
