Christoph Anton Mitterer <calestyo@xxxxxxxxxxxx> wrote: > > This works, btw. in bash, but neither in busybox sh, nor klibc sh. This happens only with fnmatch. So I would presume that it's a bug in glibc and you can take it up with them. Thanks, -- Email: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx> Home Page: http://gondor.apana.org.au/~herbert/ PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
Re: possible wrong behaviour with patterns double [ with no closing ]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- Subject: Re: possible wrong behaviour with patterns double [ with no closing ]
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- Date: Tue, 18 Jan 2022 17:18:31 +1100
- Cc: dash@xxxxxxxxxxxxxxx
- In-reply-to: <3709ca54c9001bffd3e690695c3b44d47d50c7c8.camel@scientia.org>
- Follow-Ups:
- Re: possible wrong behaviour with patterns double [ with no closing ]
- From: Christoph Anton Mitterer
- Re: possible wrong behaviour with patterns double [ with no closing ]
- From: Christoph Anton Mitterer
- Re: possible wrong behaviour with patterns double [ with no closing ]
- References:
- possible wrong behaviour with patterns double [ with no closing ]
- From: Christoph Anton Mitterer
- possible wrong behaviour with patterns double [ with no closing ]
- Prev by Date: [PATCH] expand: Always quote caret when using fnmatch
- Next by Date: Re: [PATCH] expand: Always quote caret when using fnmatch
- Previous by thread: possible wrong behaviour with patterns double [ with no closing ]
- Next by thread: Re: possible wrong behaviour with patterns double [ with no closing ]
- Index(es):
 |