113 reputation
4
bio website sahyog.blogspot.com
location Seattle
age
visits member for 2 years, 7 months
seen Feb 10 '13 at 3:39

Im a code monkey :)


Jun
12
awarded  Tumbleweed
Apr
11
revised Use different shell for scp
Updated to reflect that its the bashrc thats getting executed not bash_profile
Apr
10
asked Use different shell for scp
Feb
7
awarded  Scholar
Feb
7
comment Awk responds differently based on how an empty argument is specified
Thanks @Gordon . That does clear it up
Feb
7
accepted Awk responds differently based on how an empty argument is specified
Feb
7
awarded  Editor
Feb
7
revised Awk responds differently based on how an empty argument is specified
added 460 characters in body
Feb
7
comment Awk responds differently based on how an empty argument is specified
Thanks, that clears up the confusion between awk and awk ''. But I still dont understand what is meant by an empty awk expression. I tried running $ echo "" > /tmp/empty.awk $ python -c 'print "hello"' | awk -f /tmp/empty.awk $ echo $? $ 0 and that works
Feb
7
comment Awk responds differently based on how an empty argument is specified
So if I understand you correctly, you are implying if I run awk with an empty script, awk doesnt read STDIN which is why python writing to STDOUT encounters the error? If this were valid, then I should encounter the same error if I ran awk with a file that was empty, correct? Like python -c 'print "hello"' | awk -f /tmp/empty.awk . The empty awk script passed with -f doesnt reproduce the error.
Feb
4
awarded  Student
Feb
4
asked Awk responds differently based on how an empty argument is specified