積丹尼 Dan Jacobson writes:
Hi Dan,
> As you can see, the Subject got damaged somehow when sending this
> message to me.
>
> (Subject: Re: bug#18479 acknowledged by developer ())
I don't see the problem. The debbugs system has told you that there was
an action ("acknowledged by developer"), that's
積丹尼 Dan Jacobson writes:
> Say, can we get the final information just from this email next time,
> just like in Debian. Where one doesn't need to click on the link to see
> how the bug was solved.
Well, we plan to merge with Debian's debbugs sources. This should
improve also messages like this.
Pádraig Brady writes:
>> Thanks for the hint with QUOTING_STYLE. However, it doesn't work for me:
>>
>> # env QUOTING_STYLE=escape /usr/bin/stat -c %N /tmp/foo*
>> '/tmp/foo'$'\t''bar'
>
> Right, stat currently hard codes the "shell" style.
> It probably makes sense to have this configurable.
> I
Pádraig Brady writes:
Hi,
>> I have a file called "foobar". Yes, it includes the char in
>> its name. When I call "stat -c %N", I get 'foo'$'\t''bar' .
>
>> This looks pretty strange. It is with "stat (GNU coreutils) 8.25". Earlier
>> stat versions, say "stat (GNU coreutils) 6.12" on a very old
Eric Blake writes:
Hi Eric,
>> I have a file called "foobar". Yes, it includes the char in
>> its name. When I call "stat -c %N", I get 'foo'$'\t''bar' .
>
> That is intentional; in the same vein as the way 'ls' changed its
> default output for files with awkward characters. The defaults are t
Hi,
I have a file called "foobar". Yes, it includes the char in
its name. When I call "stat -c %N", I get 'foo'$'\t''bar' .
This looks pretty strange. It is with "stat (GNU coreutils) 8.25". Earlier
stat versions, say "stat (GNU coreutils) 6.12" on a very old machine I
have access too, used to r
