On Nov 8, 2016, at 11:54 AM, Stefan Ehmann wrote:
> On 07.11.2016 22:13, Charles Swiger wrote:
>> On Nov 6, 2016, at 1:49 PM, Stefan Bethke wrote:
>>> Am 06.11.2016 um 22:27 schrieb Baptiste Daroussin
>>> :
That works for POSIX locale aka
On 07.11.2016 22:13, Charles Swiger wrote:
> On Nov 6, 2016, at 1:49 PM, Stefan Bethke wrote:
>> Am 06.11.2016 um 22:27 schrieb Baptiste Daroussin
>> :
>>> That works for POSIX locale aka C aka ASCII only world
>>
>> So what do I set my LANG and LC variables
2016-11-06 22:49, Stefan Bethke wrote:
So what do I set my LANG and LC variables to? I do want UTF-8, but I
do also want my scripts to continue to work. Clearly, en_US.UTF-8 is
not what I want. Is it C.UTF-8?
Or do I set LANG=en_US.UTF-8 and LC_COLLATE=C?
Yes, that is the safest bet.
On Nov 6, 2016, at 1:49 PM, Stefan Bethke wrote:
> Am 06.11.2016 um 22:27 schrieb Baptiste Daroussin :
>> That works for POSIX locale aka C aka ASCII only world
>
> So what do I set my LANG and LC variables to? I do want UTF-8, but I do also
> want my scripts
Am 06.11.2016 um 22:27 schrieb Baptiste Daroussin :
>
>> But under what circumstances would [A-Z] mean anything other than a
>> character whose Unicode codepoint is between U+0041 and U+005A, inclusive?
>> Especially given the locale in the example is en_US.UTF-8. Or, put
On 06/11/2016 23:30, Stefan Bethke wrote:
> Although with en_US.UTF-8 on other systems, I have not had that experience.
> A quick check on stuff I have immediate access to:
>
> macOS 10.12:
> $ echo 'abcdABCD' | sed 's/[A-Z]/X/g’
> abcd
>
> Ubuntu 14.04.5
> $ echo 'abcdABCD' | sed
> Am 06.11.2016 um 22:14 schrieb Stefan Ehmann :
>
>> That is rather surprising. Is there a normative reference for the
>> treatment of bracket expressions and character classes when using
>> locales other than C and/or encodings like UTF-8?
>
> I found an interesting article
On Sun, Nov 06, 2016 at 10:20:54PM +0100, Stefan Bethke wrote:
>
> > Am 06.11.2016 um 22:06 schrieb Baptiste Daroussin :
> >
> > On Sun, Nov 06, 2016 at 09:57:00PM +0100, Stefan Bethke wrote:
> >>
> >>> Am 06.11.2016 um 12:07 schrieb Baptiste Daroussin :
>
> Am 06.11.2016 um 22:06 schrieb Baptiste Daroussin :
>
> On Sun, Nov 06, 2016 at 09:57:00PM +0100, Stefan Bethke wrote:
>>
>>> Am 06.11.2016 um 12:07 schrieb Baptiste Daroussin :
>>>
>>> On Sat, Nov 05, 2016 at 08:23:25PM -0500, Greg Rivers wrote:
I
On 06.11.2016 21:57, Stefan Bethke wrote:
>
>> Am 06.11.2016 um 12:07 schrieb Baptiste Daroussin
>> :
>>
>> On Sat, Nov 05, 2016 at 08:23:25PM -0500, Greg Rivers wrote:
>>> I happened to run an old script today that uses sed(1) to extract
>>> the system boot time from the
On Sun, Nov 06, 2016 at 09:57:00PM +0100, Stefan Bethke wrote:
>
> > Am 06.11.2016 um 12:07 schrieb Baptiste Daroussin :
> >
> > On Sat, Nov 05, 2016 at 08:23:25PM -0500, Greg Rivers wrote:
> >> I happened to run an old script today that uses sed(1) to extract the
> >> system
> Am 06.11.2016 um 12:07 schrieb Baptiste Daroussin :
>
> On Sat, Nov 05, 2016 at 08:23:25PM -0500, Greg Rivers wrote:
>> I happened to run an old script today that uses sed(1) to extract the system
>> boot time from the kern.boottime sysctl MIB. On 11.0 this no longer works as
On Sun, Nov 06, 2016 at 01:26:51PM +0100, Mark Martinec wrote:
> 2016-11-06 12:07, Baptiste Daroussin wrote:
> > Yes A-Z only means uppercase in an ASCII only world in a unicode world
> > it means
> > AaBb... Z because there are way more characters that simple A-Z. In
> > FreeBSD 11
> > we have a
2016-11-06 12:07, Baptiste Daroussin wrote:
Yes A-Z only means uppercase in an ASCII only world in a unicode world
it means
AaBb... Z because there are way more characters that simple A-Z. In
FreeBSD 11
we have a unicode collation instead of falling back in on LC_COLLATE=C
which
means ascii
On Sat, Nov 05, 2016 at 08:23:25PM -0500, Greg Rivers wrote:
> I happened to run an old script today that uses sed(1) to extract the system
> boot time from the kern.boottime sysctl MIB. On 11.0 this no longer works as
> expected:
>
> $ sysctl kern.boottime
> kern.boottime: { sec = 1478380714,
I happened to run an old script today that uses sed(1) to extract the
system boot time from the kern.boottime sysctl MIB. On 11.0 this no longer
works as expected:
$ sysctl kern.boottime
kern.boottime: { sec = 1478380714, usec = 145351 } Sat Nov 5 16:18:34 2016
$ sysctl kern.boottime | sed -e
16 matches
Mail list logo