Re: Bash removes unrequested characters in bracket expressions (not a range).

From	Bize Ma <binaryzebra@gmail.com>
Newsgroups	gnu.bash.bug
Subject	Re: Bash removes unrequested characters in bracket expressions (not a range).
Date	2018-11-28 06:45 -0400
Message-ID	<mailman.5073.1543846788.1284.bug-bash@gnu.org> (permalink)
References	<CAFra36hcAjBHGgd_8sHjOV4wSzjmdCyLV2aQo8Ww1bwJqkxYQA@mail.gmail.com> <1c24a279-f439-a13c-be60-901096ccd4e1@case.edu> <CAFra36hdkG+5qq94cf-sbKrnw6roJWez03aKJPU=Z=Vad2LaXg@mail.gmail.com> <63b8941d-16bc-0761-7272-83eb7347354e@case.edu> <f3ddce9d-8494-e93d-62b7-26c61ee4ef96@case.edu>

Show all headers | View raw

Chet Ramey (<chet.ramey@case.edu>) wrote:

> On 11/24/18 2:32 PM, Chet Ramey wrote:
>
> >> But IMO locale collation should not be used for an explicit list.
> >
> > Collation order is used for each individual character in a bracket
> > expression when compared against the string, as posix specifies.
>

Yes, values resulting from a glob expansion should be compared with strcoll.

How many characters should there be in a range like [0-0] ?
Or to be more precise: in a [0] bracket expression? one?

If I were you, I would file a bug report with Debian against wcscoll.
>

And I would be told that wcscoll is doing what the collation file 14651 is
telling it to do.

And, that in any case, that file has been updated in glib2.8 anyway.

> It returns 0 (equal) for L"٠" and L"0" without setting errno. That's
> clearly a problem with wcscoll (if the character isn't valid in the current
> locale) or the locale definition.
>

Both characters collate to the same position as I have already explained.

I don't follow you about what you mean with:
*(if the character isn't valid in the current locale).*

Back to gnu.bash.bug | Previous | Next | Find similar | Unroll thread

Thread

Re: Bash removes unrequested characters in bracket expressions (not a range). Bize Ma <binaryzebra@gmail.com> - 2018-11-28 06:45 -0400

csiph-web