now, this doesn't make sense to me because it is unwieldy and it prints white space between fields, instead of retaining its comma delimited structure. Even if we manipulated this to suit our needs, is there a clear advantage of using awk over cut piped to sed?
the only differance you are looking at is speed, and w/ your awk statement you are specifing exactly which fields you want to keep and not keep. you can do w/ the same thing w/ cut saying which fields you dont want.
Personaly i would take my method vs the current awk statement due to not to be mean but its an eye soar. When i first started doing scripting i did it the long way (that awk statement) now i find i am able ot do the exact same thing but shorter and quicker, and much faster to read thru for errors. IMHO
I am using : << cut / cut to comment out block of code.
Works fine on few lines of script, then it gives me this cryptic error when I try to comment out about 80 lines.
The "warning " is at last line of script.
done < results
169 echo "END read all positioning parameters"
170... (8 Replies)
I'm a complete beginner in UNIX (and not a computer science student either), just undergoing a tutoring course. Trying to replicate the instructions on my own I directed output of the ls listing command (lists all files of my home directory ) to My_dir.tsv file (see the screenshot) to make use of... (9 Replies)
Can anyone what I am doing wrong while using cut command.
for f in *.log
Log "Log file Name: $logfilename"
logfile1=`basename $logfilename .log`
Log "file length $flength"
from_length=$(($flength - 15))
Log "from... (2 Replies)