I guess my final question on this is, for the second cut:
|cut -d\) -f1`
Where in that code is it telling it to grab the previous. If the delimeter is indicated as being ), why wouldnt it think to grab what ever follows as it did with the first cut. Sorry if the answer is obvious to you guys but not me
from the result of the first part of the command:
the cut splits this into two fields
If there had been more text after the ), it would be in field 2.
As we only want the stuff in field 1, we ask for it.
If you fed this line into that cut, you would have more than 2 fields:
Oh ok, the delimiter seperates it into fields. First you ask for field 2, then field 1. Took me a while lol. Now that sed example, I think I better get more coffee before I attempt to decipher that.
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)
Hi
Can anyone what I am doing wrong while using cut command.
for f in *.log
do
logfilename=$f
Log "Log file Name: $logfilename"
logfile1=`basename $logfilename .log`
flength=${#logfile1}
Log "file length $flength"
from_length=$(($flength - 15))
Log "from... (2 Replies)