tee|tee|tee

2010-01-19 Thread jidanni
The tee(1) documents fail to say what happens when tee is given no arguments. Do say what is going on in $ echo o|tee|tee|tee o Also there is a Info reference to (bashref), but here on Debian there is no such match in apt-file(1).

Re: expr exit status

2010-01-19 Thread Alfred M. Szmidt
What are all the exit statuses I need to check just after expr command? Is it only need to check 1 or 2 or 3 for fail condition and zero for success ?else pease specify You only need to check for non-zero exit codes for failure.

Re: tee|tee|tee

2010-01-19 Thread Giuseppe Scrivano
jida...@jidanni.org writes: > The tee(1) documents fail to say what happens when tee is given no > arguments. Do say what is going on in > $ echo o|tee|tee|tee "The `tee' command copies standard input to standard output and also to any files given as arguments." it looks quite clear to me, if yo

Re: Bug in expr***urgent

2010-01-19 Thread Eric Blake
According to salih k on 1/16/2010 7:32 AM: > Piece of Script > -- > > /isnum=`awk -F$delim '$1=="BH"{print $5}' $fil`/ > / That's still not exactly what you ran (you marked it up afterwards), but it is close enough, I suppose. > int_num=`echo -e $isnu

Re: expr exit status

2010-01-19 Thread Eric Blake
According to Alfred M. Szmidt on 1/19/2010 12:37 AM: >What are all the exit statuses I need to check just after expr >command? Is it only need to check 1 or 2 or 3 for fail condition >and zero for success ?else pease specify > > You only need to check for non-zero exit codes for failu

Re: Incorrect use of USE_XATTR in coreutils-8.4

2010-01-19 Thread Eric Blake
According to Jim Meyering on 1/17/2010 1:03 AM: > Thanks! > That would fix it, but please retain the 0/1 semantics, in case > we ever want to use USE_XATTR in a C (as opposed to cpp) expression. > > # Map yes,no to 1,0. > AC_DEFINE_UNQUOTED([USE_XATTR], >[`test $use

Re: Incorrect use of USE_XATTR in coreutils-8.4

2010-01-19 Thread Jim Meyering
Eric Blake wrote: > According to Jim Meyering on 1/17/2010 1:03 AM: >> Thanks! >> That would fix it, but please retain the 0/1 semantics, in case >> we ever want to use USE_XATTR in a C (as opposed to cpp) expression. >> >> # Map yes,no to 1,0. >> AC_DEFINE_UNQUOTED([USE_XATTR], >>

RE: different behavior of sort

2010-01-19 Thread Sheila Yao
Eric: Very interesting. However, it doesn't seem to work, after I followed the instructions of http://www.gnu.org/software/coreutils/faq/coreutils-faq.html#Sort-does-not-sort-in-normal-order_0021. At the host that sort doesn't work, where LC_ALL is null, I ran: export LC_ALL=POSIX env |grep L

Re: different behavior of sort

2010-01-19 Thread Andreas Schwab
Sheila Yao writes: > sort -n -k2.1,2.4 /tmp/sort.out > /dev/emcpowera 47G 39G 7.8G 84% /DB1/DW/data9 The sort key is probably not what you think it is. I have marked it for you. Since the sort key is identical in all lines, sort has used as a last resort the wh

RE: different behavior of sort

2010-01-19 Thread Sheila Yao
Eric: So it is not a bug? When I use sort -n -k2.1,2.19, it sorts accordingly. Thanks.   Have a nice day,   Sheila Yao -Original Message- From: Andreas Schwab [mailto:sch...@linux-m68k.org] Sent: Tuesday, January 19, 2010 11:23 AM To: Sheila Yao Cc: Eric Blake; bug-coreutils@gnu.org Sub

Re: tee|tee|tee

2010-01-19 Thread jidanni
> "GS" == Giuseppe Scrivano writes: GS> jida...@jidanni.org writes: >> The tee(1) documents fail to say what happens when tee is given no >> arguments. Do say what is going on in >> $ echo o|tee|tee|tee GS> "The `tee' command copies standard input to standard output and also to GS> any files

Re: Bug in expr***urgent

2010-01-19 Thread salih k
On Tue, Jan 19, 2010 at 9:10 PM, Eric Blake wrote: > According to salih k on 1/16/2010 7:32 AM: > > Piece of Script > > -- > > > > /isnum=`awk -F$delim '$1=="BH"{print $5}' $fil`/ > > / > > That's still not exactly what you ran (you marked it up afterwards), but >

Re: expr exit status

2010-01-19 Thread salih k
On Tue, Jan 19, 2010 at 3:37 PM, Alfred M. Szmidt wrote: > What are all the exit statuses I need to check just after expr > command? Is it only need to check 1 or 2 or 3 for fail condition > and zero for success ?else pease specify > > You only need to check for non-zero exit codes for fai