Jim Meyering wrote:
...
>> The awkward/somewhat redundant -n, --no-newline option
>> is handled in the same way as on BSD and the help text adjusted like:
>>
>> - -n, --no-newline do not output the trailing newline\n\
>> + -n, --no-newline do not output the separator cha
Hello,
Attached is an updated version of 'numfmt' .
(The patch should be compatible with "git am").
Most of the previously raised issues have been addressed, except handling
locale'd grouping in the input numbers (locale'd decimal-point is handled
correctly).
Added support for header, auto-wh
Pádraig Brady wrote:
> On 12/12/2012 08:19 PM, Jim Meyering wrote:
>> Pádraig Brady wrote:
>>> On 12/12/2012 07:05 PM, Aaron Davies wrote:
Is there a reason the interface for readlink(1) is “FILE” instead of
“FILE...”? I’ve often wanted to do e.g. “find -type l|xargs
readlink” or (in
On 12/12/2012 08:00 PM, Eric Blake wrote:
On 12/12/2012 12:54 PM, Pádraig Brady wrote:
On 12/12/2012 07:05 PM, Aaron Davies wrote:
Is there a reason the interface for readlink(1) is “FILE” instead of
“FILE...”? I’ve often wanted to do e.g. “find -type l|xargs readlink”
or (in zsh) “readlink **/
On 12/12/2012 08:19 PM, Jim Meyering wrote:
Pádraig Brady wrote:
On 12/12/2012 07:05 PM, Aaron Davies wrote:
Is there a reason the interface for readlink(1) is “FILE” instead of
“FILE...”? I’ve often wanted to do e.g. “find -type l|xargs
readlink” or (in zsh) “readlink **/*(@)”, and having to d
Pádraig Brady wrote:
> On 12/12/2012 07:05 PM, Aaron Davies wrote:
>> Is there a reason the interface for readlink(1) is “FILE” instead of
>> “FILE...”? I’ve often wanted to do e.g. “find -type l|xargs
>> readlink” or (in zsh) “readlink **/*(@)”, and having to do a shell
>> loop or use “xargs -n1”
On 12/12/2012 12:54 PM, Pádraig Brady wrote:
> On 12/12/2012 07:05 PM, Aaron Davies wrote:
>> Is there a reason the interface for readlink(1) is “FILE” instead of
>> “FILE...”? I’ve often wanted to do e.g. “find -type l|xargs readlink”
>> or (in zsh) “readlink **/*(@)”, and having to do a shell loo
On 12/12/2012 07:05 PM, Aaron Davies wrote:
Is there a reason the interface for readlink(1) is “FILE” instead of “FILE...”?
I’ve often wanted to do e.g. “find -type l|xargs readlink” or (in zsh)
“readlink **/*(@)”, and having to do a shell loop or use “xargs -n1” seems
inelegant.
Note the ne
Is there a reason the interface for readlink(1) is “FILE” instead of “FILE...”?
I’ve often wanted to do e.g. “find -type l|xargs readlink” or (in zsh)
“readlink **/*(@)”, and having to do a shell loop or use “xargs -n1” seems
inelegant.
--
Aaron Davies
aaron.dav...@gmail.com
