A number of utilities, including bison, m4 and findutils, install a
charset.alias file under Mac OS X, and this breaks the locale system
(any locale is regarded as UTF-8) [*]. The problem has been around
for a couple of years.
Moreover, even if it didn't break anything, the file is overwritten
whe
On 2005-06-08 20:41:21 +0200, Alexandre Duret-Lutz wrote:
> unset is not portable.
> Can we override TIME_STYLE with some safe value? Which one?
> What happens when this is set to the empty string?
An empty string is incorrect:
ay:~> TIME_STYLE= ls -l
ls: ambiguous argument `' for `time style'
On 2005-06-07 13:49:40 +0100, James Youngman wrote:
> I can't explain that. The mdate-sh command contains no loops (at
> least at the Bource shell source level).
Yes, there is the "until" loop (really strange!).
> Can you reproduce the problem? Can you preproduce it wile using thr
> "-x" option
On 2005-06-07 09:08:50 +0100, James Youngman wrote:
> How did you find the patch?
The behaviour seems OK to me.
> More importantly, is the updated documentation intelligible?
[EMAIL PROTECTED] -ls
[EMAIL PROTECTED] -fls
+Unusual characters are always escaped. White space, backslash, and
+double
I tried to compile the findutils from the CVS tree (checked out a few
minutes ago). But make stalls here:
[...]
Making all in doc
make[2]: Entering directory `/home/vlefevre/software/findutils/doc'
ps says in particular:
vlefevre 21409 21408 99 13:30 pts/10 00:00:46 /bin/sh ./mdate-sh ./find.t
On 2005-06-05 15:36:01 +0100, James Youngman wrote:
> I think that -print0 and friends should probably just pass the data
> through unchanged, even if stdout is a tty.
Anyway I think that this does not make sense to use -print0 when
stdout is a tty. So any behavior would be OK in this case.
--
V