Re: RH 7.2 bash 2.05.8(1) whacked?

2002-02-04 Thread Benjamin Scott
On Mon, 4 Feb 2002, Paul Lussier wrote: > I expect Unicode to supercede ASCII about the same time IPv6 supercedes > IPv4. Actually, to make the transition go smoothly, they will probably > implement both simultaneously. > > I expect to pushing up daisies long before either happen. Like I said

Re: RH 7.2 bash 2.05.8(1) whacked?

2002-02-04 Thread Paul Lussier
In a message dated: Mon, 04 Feb 2002 13:01:32 PST "Karl J. Runge" said: >Sorry, I wasn't clear. Just a nit: I only meant 'export FOO=bar' is >bash specific. Some people work only on Linux where sh -> bash, but in >a heterogeneous environment it could make a difference... (no sh wars pls). Ohh

Re: RH 7.2 bash 2.05.8(1) whacked?

2002-02-04 Thread Karl J. Runge
On Mon, 04 Feb 2002, Paul Lussier <[EMAIL PROTECTED]> wrote: > > >That's not as portable as what Derek wrote. > > That may be so, but unless you're outside the US, or non-English > speaking, how much would that matter? I've always had LANG=C, and > I've never needed to change anything. Sorry

Re: RH 7.2 bash 2.05.8(1) whacked?

2002-02-04 Thread Benjamin Scott
On Mon, 4 Feb 2002, Derek D. Martin wrote: > This really *shouldn't* be much of a problem, as there are already > well-established routines for decoding Unicode, through which applications > should feed their input at such time as that becomes appropriate. Note > the emphasis on "shouldn't" above

Re: RH 7.2 bash 2.05.8(1) whacked?

2002-02-04 Thread Derek D. Martin
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Benjamin Scott said: > On Mon, 4 Feb 2002, Derek D. Martin wrote: > > The problem is that Red Hat, and probably other vendors, have changed the > > default locale. > > Expect this problem to get worse as more and more of the three billion or > so

Re: RH 7.2 bash 2.05.8(1) whacked?

2002-02-04 Thread Paul Lussier
In a message dated: Mon, 04 Feb 2002 15:43:46 EST Benjamin Scott said: >On Mon, 4 Feb 2002, Derek D. Martin wrote: >> The problem is that Red Hat, and probably other vendors, have changed the >> default locale. > > Expect this problem to get worse as more and more of the three billion or >so no

Re: RH 7.2 bash 2.05.8(1) whacked?

2002-02-04 Thread Paul Lussier
In a message dated: Mon, 04 Feb 2002 12:43:32 PST "Karl J. Runge" said: >That's not as portable as what Derek wrote. That may be so, but unless you're outside the US, or non-English speaking, how much would that matter? I've always had LANG=C, and I've never needed to change anything. Can y

Fwd: Re: RH 7.2 bash 2.05.8(1) whacked?

2002-02-04 Thread Derek D. Martin
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Paul Lussier said: > Couldn't you just: > > export LANG=C Yes, but there may be reasons not to do that. If you're English-speaking and live in the US (which, granted, is most of us) then this works fine for you, since that's basically the be

Re: RH 7.2 bash 2.05.8(1) whacked?

2002-02-04 Thread Karl J. Runge
On Mon, 04 Feb 2002, Paul Lussier <[EMAIL PROTECTED]> wrote: > "Derek D. Martin" said: > > >LANG=en_US > >LC_COLLATE=C > >export LANG LC_COLLATE > > Couldn't you just: > > export LANG=C That's not as portable as what Derek wrote.

Re: RH 7.2 bash 2.05.8(1) whacked?

2002-02-04 Thread Benjamin Scott
On Mon, 4 Feb 2002, Derek D. Martin wrote: > The problem is that Red Hat, and probably other vendors, have changed the > default locale. Expect this problem to get worse as more and more of the three billion or so non-English-speaking people in the world begin using computers. Personally, I

Re: RH 7.2 bash 2.05.8(1) whacked?

2002-02-04 Thread Paul Lussier
In a message dated: Mon, 04 Feb 2002 15:19:21 EST "Derek D. Martin" said: >LANG=en_US >LC_COLLATE=C >export LANG LC_COLLATE Couldn't you just: export LANG=C ? -- Seeya, Paul God Bless America! If you're not having fun, you're not doing it rig

Re: [TriLUG] RH 7.2 bash 2.05.8(1) whacked?

2002-02-04 Thread Rodent of Unusual Size
James Manning wrote: > > [Rodent of Unusual Size] > > Anyone else seen this? Or have a suggestion on how to proceed? > > sounds like the LANG/LC/etc settings issues. iirc, LC_SORT=C > LANG=C, or something like that. I forget :) *@&#*(&@!!! LANG="en_US", LC_COLLATE=(not set). Changing to LC

Re: RH 7.2 bash 2.05.8(1) whacked?

2002-02-04 Thread Derek D. Martin
Rodent of Unusual Size said: > Something seems *really* whacked out with bash wildcards. > Firstly they aren't being listed in case-sensitive lexical > order (A B C a b c) they way they should be, and secondly > ranges are *really* screwed up: Welcome to the new default behavior of posixly-corre

Re: RH 7.2 bash 2.05.8(1) whacked?

2002-02-04 Thread Paul Lussier
In a message dated: Mon, 04 Feb 2002 15:12:44 EST Rodent of Unusual Size said: >Something seems *really* whacked out with bash wildcards. Did you check your LANG setting? Make sure it's 'C'. -- Seeya, Paul God Bless America! If you're not having fu

RH 7.2 bash 2.05.8(1) whacked?

2002-02-04 Thread Rodent of Unusual Size
Something seems *really* whacked out with bash wildcards. Firstly they aren't being listed in case-sensitive lexical order (A B C a b c) they way they should be, and secondly ranges are *really* screwed up: % cd /tmp % mkdir test % cd test % touch A B C a b c % /bin/ls -1 a A b B c C % /bin/ls -1