Strange to me that is.
Why am I asking here? Perhaps I should make a fool of myself to the
kernel or glibc people?
Well I know geniuses hang out here. Plus coreutils must have dealt with
issues like this if it is indeed normal.
$ ls -la fread-fseek.c
-rw-r--r-- 1 joe joe 1155 Jan 26 13:37
Jeff Silverman wrote:
I am trying to parse whitespace delimited files, and it seems
intuitively obvious to me that I ought to be able to do it with the
cut command. Cut works fine with /etc/mtab, where the fields really
and truly are delimited by a single space character. But for files
suc
I want to say thank you to Jim and Bob who have responded kindly to me
with informative information.
___
Bug-coreutils mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-coreutils
Jim Meyering wrote:
Joe Maimon <[EMAIL PROTECTED]> wrote:
When using the -d option I find it frustrating that arbitrary whitespace
ruins the field count.
witness this script:
dig -x $addr +noall +answer | grep -v '^;' | grep -v '$^' | expand | cut
-d' '
When using the -d option I find it frustrating that arbitrary whitespace
ruins the field count.
witness this script (new option -z)(one line):
dig -x $addr +noall +answer | grep -v '^;' | grep -v '$^' | expand | cut
-d' ' -f5 -z
With the new option in this patch, you can rely on the behavior to
pr
When using the -d option I find it frustrating that arbitrary whitespace
ruins the field count.
witness this script:
dig -x $addr +noall +answer | grep -v '^;' | grep -v '$^' | expand | cut
-d' ' -f5 -z
With the new option in this patch, you can rely on the behavior to
produce a hostname if there
