Pádraig,
I'm actually interested in whitespace blocks, rather than just runs of
spaces, but I see that this was also discussed at the link. I suppose
from a typability and readability standpoint I still prefer 'awk' to
the alternative
$ tr '[:blank:]' ' ' | cut -d ' ' -f 3-5
although I'd st
Mike Coleman wrote:
> It would be really nice if cut(1) could split fields using whitespace
> as a separator (as many other text tools do). Currently I use
>
> $ awk '{ print $3, $4, $5 }'
>
> for this sort of thing, but it seems relatively klutzy, as opposed to (say)
>
> $ cut -w -f 3-
Christoph Hellwig wrote:
> On Tue, Sep 08, 2009 at 12:29:49PM +0100, P??draig Brady wrote:
>> fsetxattr() is failing for me when the permissions are readonly
>> but the descriptor is writable as demonstrated by the program below.
>> I've tried this on ext3 and ext4 with libattr-2.4.43-3.fc11.i586
>
Pádraig Brady wrote:
> Eric Blake wrote:
>> According to OndYej Vaaík on 9/9/2009 2:19 AM:
>>> Hello,
>>> as requested via https://bugzilla.redhat.com/show_bug.cgi?id=511188 , it
>>> would be nice to clarify default blocksize used by du in manpage/--help
>>> output. Although I closed that bugzilla
Eric Blake wrote:
> According to OndYej Vaaík on 9/9/2009 2:19 AM:
>> Hello,
>> as requested via https://bugzilla.redhat.com/show_bug.cgi?id=511188 , it
>> would be nice to clarify default blocksize used by du in manpage/--help
>> output. Although I closed that bugzilla as notabug, further
>> commu
Jim Meyering wrote:
> Eric Blake wrote:
> > This repetition begs for a helper method in system.h. It would look better
> > like:
> >
> > emit_blocksize (program_name);
>
> I agree.
> Though please call it something like "emit_blocksize_note"
> so it's name doesn't imply it's printing a bare numbe
Eric Blake wrote:
> Ondřej Vašík redhat.com> writes:
>> Good, point. Added blurb about the environment variables to all of those
>> utilities.
>
>>fputs (_("\n\
>> +If none of the environment variables BLOCKSIZE, BLOCK_SIZE or \n\
>> +_BLOCKSIZE is specified, blocksize defaults to 1024 byt
FYI,
>From f1e1e89e8166153852de1cc1777edb40dc4c08e9 Mon Sep 17 00:00:00 2001
From: Jim Meyering
Date: Wed, 9 Sep 2009 16:44:37 +0200
Subject: [PATCH] maint: make cfg.mk slightly more generic
* cfg.mk (url_dir_list): Don't hard-code "coreutils". Use $(PACKAGE).
---
cfg.mk |2 +-
1 files cha
Ondřej Vašík redhat.com> writes:
>
> Good, point. Added blurb about the environment variables to all of those
> utilities.
>fputs (_("\n\
> +If none of the environment variables BLOCKSIZE, BLOCK_SIZE or \n\
> +_BLOCKSIZE is specified, blocksize defaults to 1024 bytes.\n\
When I do du -
Eric Blake wrote:
> According to Ondřej Vašík on 9/9/2009 2:19 AM:
> > Hello,
> > as requested via https://bugzilla.redhat.com/show_bug.cgi?id=511188 , it
> > would be nice to clarify default blocksize used by du in manpage/--help
> > output. Although I closed that bugzilla as notabug, further
> >
On Mon, Sep 07, 2009 at 05:15:58PM +0200, Jim Meyering wrote:
Giuseppe Scrivano wrote:
This patch changes `tail' to handle stdin separately from inotify
events, similar to what we are already doing when a --pid is specified.
This sounds good in principle, but it's too invasive for 7.6.
I'll lo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Ondřej Vašík on 9/9/2009 2:19 AM:
> Hello,
> as requested via https://bugzilla.redhat.com/show_bug.cgi?id=511188 , it
> would be nice to clarify default blocksize used by du in manpage/--help
> output. Although I closed that bugzilla as no
Hello,
as requested via https://bugzilla.redhat.com/show_bug.cgi?id=511188 , it
would be nice to clarify default blocksize used by du in manpage/--help
output. Although I closed that bugzilla as notabug, further
communication via private emails convinced me to propose that change to
upstream.
As it
13 matches
Mail list logo
