Bug#317773: LC_ALL=C foo, where foo is a shell function

2008-02-21 Thread Peter Stephenson
On Sun, Jul 10, 2005 at 12:57:47AM +, Bart Schaefer wrote: > I just noticed that, even in the latest build, if LC_ALL starts out set > (even to nothing), but not exported, then when "LC_ALL=C foo" is run > LC_ALL becomes and remains exported, even though its value gets reset > to the previous s

Bug#317773: LC_ALL=C foo, where foo is a shell function

2008-01-29 Thread Clint Adams
[moved to -workers] On Sat, Apr 14, 2007 at 01:18:31PM -0700, Bart Schaefer wrote: > I'm not able to reproduce it with the latest CVS on my RHEL4 machine, or > at least I can't do so with the most straightforward interpretation of > "LC_ALL starts out set". > > If it is happening, it has to be re

Bug#317773: LC_ALL=C foo, where foo is a shell function

2007-04-14 Thread Bart Schaefer
On Apr 14, 3:38pm, Clint Adams wrote: } } On Sun, Jul 10, 2005 at 12:57:47AM +, Bart Schaefer wrote: } > I just noticed Nearly two years ago. Phrases like "just now" certainly take on a different flavor in the face of permanent archival ... } > that, even in the latest build, if LC_ALL star

Bug#317773: LC_ALL=C foo, where foo is a shell function

2007-04-14 Thread Clint Adams
On Sun, Jul 10, 2005 at 12:57:47AM +, Bart Schaefer wrote: > Ah. I tried it with the latest -dev version, compiled out of my CVS > sandbox. > > If I try with 4.2.5, I get the same results as you. > > I just noticed that, even in the latest build, if LC_ALL starts out set > (even to nothing),