On Wed, 11 Nov 2015 07:16:42 +0100
Patrick Lauer wrote:
> On 11/11/2015 03:51 AM, Mike Frysinger wrote:
> > On 10 Nov 2015 18:53, Mike Frysinger wrote:
> >> i randomly stumbled across an ebuild that was using ^^ to make a variable
> >> uppercase. this is new to bash-4.0
On Wed, 11 Nov 2015 07:16:42 +0100
Patrick Lauer wrote:
> Wouldn't it be 'easier' (fsov easy) to have portage use sane-default
> locale settings, so that estonian or turkish users don't get hit by
> weirdness in the [a-z] character class etc.?
Paludis forces all the LC
> On Wed, 11 Nov 2015, Mike Frysinger wrote:
>> This is wrong on so many levels. :( It starts with the fact that the
>> dot over the lowercase latin i historically never was a diacritical
>> mark [1].
>>
>> Maybe we should advise users in our documentaion that they should
>> avoid such
On 10 Nov 2015 18:53, Mike Frysinger wrote:
> i randomly stumbled across an ebuild that was using ^^ to make a variable
> uppercase. this is new to bash-4.0 and thus invalid for EAPI=[0-5]. only
> the fresh EAPI=6 permits it since we bumped the min ver to bash-4.2.
Arfrever highlights these are
Am 11.11.2015 um 05:16 schrieb Ulrich Mueller:
>> On Tue, 10 Nov 2015, Mike Frysinger wrote:
>
>> Arfrever highlights these are not even safe to use. bash is locale aware,
>> so it'll apply LC_COLLATE rules when processing the ^/, casemods. while
>> you can fix this with external programs
> On Wed, 11 Nov 2015, René Neumann wrote:
>> Shouldn't these be safe to use if the string consists purely of
>> ASCII characters? I mean, A-Z and a-z should be uppercase and
>> lowercase, respectively, in any locale?
> Unfortunately, no (have been bitten by this issue already some years
>
On 11 Nov 2015 05:16, Ulrich Mueller wrote:
> > On Tue, 10 Nov 2015, Mike Frysinger wrote:
>
> > Arfrever highlights these are not even safe to use. bash is locale aware,
> > so it'll apply LC_COLLATE rules when processing the ^/, casemods. while
> > you can fix this with external programs
On 11 Nov 2015 08:37, Ulrich Mueller wrote:
> > On Wed, 11 Nov 2015, René Neumann wrote:
>
> >> Shouldn't these be safe to use if the string consists purely of
> >> ASCII characters? I mean, A-Z and a-z should be uppercase and
> >> lowercase, respectively, in any locale?
>
> > Unfortunately,
On 11/11/2015 03:51 AM, Mike Frysinger wrote:
> On 10 Nov 2015 18:53, Mike Frysinger wrote:
>> i randomly stumbled across an ebuild that was using ^^ to make a variable
>> uppercase. this is new to bash-4.0 and thus invalid for EAPI=[0-5]. only
>> the fresh EAPI=6 permits it since we bumped
sorry, i meant char classification here (LC_CTYPE), not collation.
i've been dealing with sorting bugs lately ;).
-mike
signature.asc
Description: Digital signature
> On Tue, 10 Nov 2015, Mike Frysinger wrote:
> Arfrever highlights these are not even safe to use. bash is locale aware,
> so it'll apply LC_COLLATE rules when processing the ^/, casemods. while
> you can fix this with external programs ala:
> LC_COLLATE=C tr ...
> you can't do it
11 matches
Mail list logo