a//../*///*'
> .a//../a///b
> .a//../d///e
> .a//../g///h
>
I suppose it all comes down to an implementation question.
Best,
Mickaël
On Wed, Jan 8, 2020 at 4:09 PM Chet Ramey wrote:
> On 1/8/20 2:34 AM, Mickael KENIKSSI wrote:
> > Hello,
>
Hello,
I found a bug regarding how pathnames are processed during filename
expansion. The result for non-normalized path-patterns may get mangled in a
such a way that it becomes inconsistent and unpredictable, making it
useless for string comparison or any kind of string manipulation where
having
