(info "(coreutils) Sorting the output") says
‘-r’
‘--reverse’
Reverse whatever the sorting method is—e.g., list files in reverse
alphabetical order, youngest first, smallest first, or whatever.
OK but mention 'whatever' doesn't mean -U, -f, because they are sorted
in "unsorted" order. I
On 04/03/2018 12:29 PM, kalle wrote:
But what do you think of my teaching concept, to try to explain why a
`7' in `755' means =4+2+1=111=rwx="rwx for owner", which is assumed as
self-evident or intuitive in both the original text and your patch?
I think it's out of place in the coreutils manua
On 04/03/2018 06:16 PM, Matthew Fowkes wrote:
>> root@4901abe58547:/app# tail -f /var/log/check*
>> tail: unrecognized file system type 0x794c7630 for
>> '/var/log/checkForClaimFiles.log'. please report this to
>> bug-coreutils@gnu.org. reverting to polling
Support for this file system type has
hello,
Am 03.04.2018 um 17:45 schrieb Paul Eggert:
> Thanks for mentioning the problem.
so you see a problem there too?
However, I found the proposed rewrite
> to be more confusing than the original.
It may me that my way of building sentences is quite amendable. I'm not
a native english write
Just launched a new server on ec2 and received this message when trying to
watch a log file:
> root@4901abe58547:/app# tail -f /var/log/check*
> tail: unrecognized file system type 0x794c7630 for
> '/var/log/checkForClaimFiles.log'. please report this to
> bug-coreutils@gnu.org. reverting to p
Thanks for mentioning the problem. However, I found the proposed rewrite
to be more confusing than the original. I think part of the problem is
that this is not really the place to explain octal notation; any reader
who doesn't know octal before reading the manual is not likely to
understand it
OK. Please on (info "(coreutils) cp invocation") at
‘-v’
‘--verbose’
Print the name of each file before copying it.
add:
"(Note this reveals internal order of operations, often in ls -U order,
thus occasionally appearing to be in ls, ls -t, ls -r, ls -rt etc. order.)"
(I mean on the same pag
On 04/03/2018 09:37 AM, 積丹尼 Dan Jacobson wrote:
> OK maybe I was just looking at the latter half of
>
> $ sh O
> /tmp
> created directory '/var/tmp/y'
> copied 'x/1' -> '/var/tmp/y/1'
> copied 'x/2' -> '/var/tmp/y/2'
> copied 'x/3' -> '/var/tmp/y/3'
> copied 'x/4' -> '/var/tmp/y/4'
> copied 'x/5'
OK maybe I was just looking at the latter half of
$ sh O
/tmp
created directory '/var/tmp/y'
copied 'x/1' -> '/var/tmp/y/1'
copied 'x/2' -> '/var/tmp/y/2'
copied 'x/3' -> '/var/tmp/y/3'
copied 'x/4' -> '/var/tmp/y/4'
copied 'x/5' -> '/var/tmp/y/5'
copied 'x/6' -> '/var/tmp/y/6'
copied 'x/7' -> '/v
tag 31045 notabug
thanks
On 04/03/2018 05:59 AM, Abhijeet Patwari wrote:
> Hi,
>
> I was using split 8.25 version. In my code, I have used split -e option.
> After server upgrade, split also got upgraded and my code is giving error
> at split -e.
>
> Kindly let me know what is the equivalent of
tag 31038 notabug
thanks
On 04/03/2018 02:52 AM, 積丹尼 Dan Jacobson wrote:
> $ mv -v dir1/* dir2
> reveals that mv works backwards,
> copying in ls -r order.
Not quite true. It copies the arguments in the order given on the
command line (the * glob expands to a sorted list according to the
current
Hi,
I was using split 8.25 version. In my code, I have used split -e option.
After server upgrade, split also got upgraded and my code is giving error
at split -e.
Kindly let me know what is the equivalent of split -e in 8.4. OR any
alternate solution for this.
--
Regards,
Abhijeet Patwari
Mob.
hello,
below a patch proposal of mine.
kalle
>From b250dcdaba02083a0174d9157c655f0dbb586ef6 Mon Sep 17 00:00:00 2001
From: kalle
Date: Wed, 3 Jan 2018 20:56:07 +0100
Subject: [PATCH] changed presentation in 'File permissions' in 'numeric
modes'
I described the numeric modes explaining it's octa
$ mv -v dir1/* dir2
reveals that mv works backwards,
copying in ls -r order.
Well OK, but why is that order better than the order of the arguments it
was given?
14 matches
Mail list logo
