Shell Programming and Scripting

Nobody understood it until you explained.

What is obvious to you isn't obvious to us -- we can't see your computer. When you say "something doesn't work" and don't tell us what you did or changed, we are left wild-guessing. We're not going to assume you interpreted our instructions correctly either; if it's that obvious, why couldn't you get it to work? Did you misinterpret something we said? We don't know. We can't tell. We can't even tell how, we can't even tell in what way it didn't work.

I remember a while ago trying to talk to someone who was having a problem with a website of mine. I asked him to tell me exactly what he did and what URL's but he refused to be specific and berated me instead. I had to remote into his computer to discover he was going to the wrong URL, something he could have simply told me when I asked instead of expecting me to read his mind. He thought something was obvious, but it wasn't.

Never make us guess if you can help it.

Lets end this misinterpretation.
Sorry Aia and thanks a lot to all the people who tried to help me. especially RudiC, Aia and Corona.




Thanks & Regards,
linuxUser_

---------- Post updated at 11:03 AM ---------- Previous update was at 10:41 AM ----------

I have one more problem.
Corona code reads fields as single string

Code:

echo ${fields[0]}

results

Code:

p U T

How can I separate them?
I mean how can I access each field independently?

Thanks & Regards,
linuxUser_

That's because Corona688's script creates and executes

Code:

fields=( "p U T" "p U" )

How can I separate them out?

As much as I like to help, this is becoming a bit tedious. Make it e.g.

Code:

fields=( p U T p U )

as the man page for your shell suggests.

Did you try to run my proposal outputting to a unique file (like /tmp/$$ in Corona688's script) and then sourcing this file? Wouldn't that be a satisfying solution?

See comment number 27. I ended up with that error.

#27 is Aia's post?

OK, in case you were talking of post#26: run the command without the . <(...) construct and post the output.