Re: Possible file completion bug when the path contains a backslash

[Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx>]

On Jan 11, 11:22am, Drew Frank wrote:
}
} $ autoload -U compinit
} $ compinit
} $ ls bad\\dir/[TAB]
} 
} Any idea what's going on here? Is this, in fact, a bug?

It appears to be a bug in the (largely undocumented) compfiles builtin,
which generates a glob pattern of 'baddir*(-/)' for the directory in
question, which then does not match.  Special characters other than a
backslash appear to be handled correctly, at least in a few minimal
tests I tried.

Don't have time right now to try to trace this down (and frankly don't
care to venture into that part of the code if I don't have to ...).