Kamil Dudka wrote:
> Hello Jim,
>
> new version of patch is attached. Options --backup and --no-clobber are now
> mutually exclusive.
Hi Kamil,
Thanks again for enduring all those iterations.
I've just pushed your patch.
___
Bug-coreutils mailing list
Bob Proulx wrote:
> Olaf Reitmaier Veracierta wrote:
>> I'm trying to use the output of the command df -T as input for some
>> shell script the problem arises when for some reason some line split
>> into two lines, ...
>
> The lines are split when a field is too long to avoid misalignment.
> To av
Pádraig Brady writes:
> This should not be controlled by -P I think.
> At least this feature should only be enabled if isatty(1).
> Otherwise scripts that don't use this non obvious option
> will break as new devices are added to the system.
The option is specified by POSIX for exactly this purp
Pádraig Brady writes:
> Ok, but it would be nice not to have wildly differing output
> on the same system, depending on what devices are attached.
> This "feature" is only to aid human parsing so should be
> restricted to ttys IMHO.
Keying that on isatty is not a good way, since that would chang
Andreas Schwab wrote:
> Pádraig Brady writes:
>> Ok, but it would be nice not to have wildly differing output
>> on the same system, depending on what devices are attached.
>> This "feature" is only to aid human parsing so should be
>> restricted to ttys IMHO.
>
> Keying that on isatty is not a g
basename does not check if the file exists.
ex:
$ ls Desktop/
daniel.txt TODO.txt
$ basename Desktop/daniel.txt
daniel.txt
/(ok)/
$ basename Desktop/okidoki
okidoki
/( bad =[ )/
Tested on versions 5.2.1 (RHEL) and 6.10 (Ubuntu 8.10).
basename is suppose to work on that way or this is a bug?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Jim Meyering on 1/10/2009 2:32 PM:
>>> "[" feels like it should be the exception.
>>> I see treating --v like --version as a feature. a typing saver.
>>> But with "[", it's good to minimize the number of strings that
>>> make it act diffe
Leonardo wrote:
> basename does not check if the file exists.
That's expected behaviour.
Use the test command to check file existence:
input=Desktop/okidoki
file=$(test -e "$input" && basename "$input")
[ "$file" ] && echo "$file" || echo "missing"
Pádraig.
Eric Blake wrote:
> According to Jim Meyering on 1/10/2009 2:32 PM:
"[" feels like it should be the exception.
I see treating --v like --version as a feature. a typing saver.
But with "[", it's good to minimize the number of strings that
make it act differently.
>>>
>>> O
Aaron Peterson wrote:
Note, interactive, and no-clobber don't have to be exclusive... Here
is an example of them combined: Interactively see if the person wants
to overwrite, then say, oh, you can't do it because you told me not
to.
Then -n -i would say it can't overwrite a certain file, and no
I'd like to submit the attached small patch for du. it adds a
'--min-size' option, which can be used to filter the output to only
include items of that size or greater.
I find it useful in locating large folders on disk in one pass, to zero
in on the worst offenders when disk space is getting
Hi,
Not sure if this patch will be accepted or not, just wondering why awk
won't work for this purpose? A quick example is below. I would think
awk combined with sort could provide some very nicely formatted
output.
# du -sb * | awk '$1 > 1024*1024 {print $1/(1024*1024) "MB", $2}'
7.5757MB 200707
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Paul Chambers on 1/14/2009 3:54 PM:
> I'd like to submit the attached small patch for du. it adds a
> '--min-size' option, which can be used to filter the output to only
> include items of that size or greater.
It seems like find(1) might
On Wed, Jan 14, 2009 at 8:56 AM, Matthew Woehlke <> wrote:
>> -i -n would ask, and then say, can't overwrite or similar.
>
> I don't think that makes sense... why are you asking if you won't do it
> anyway?
because if I put a -i in my alias, then I want it to ask every time!
Sometimes I wan
Perhaps I'm missing something, but won't that only find large individual
files? What if a directory (or subtree) has a very large number of small
to medium-sized files? (e.g. someone's music or photo collection). The
docs I've found for find's -size option refer to file size, no
discussion of b
15 matches
Mail list logo
