On 06/16/2010 01:09 PM, Carlos E. R. wrote:
I'm not an expert, I did not understand all your logic on my light read. However, I know this: pipes are interpreted by the shell. If lynx is seeing behind the 1st pipe symbol, it means that bash is not seeing it first. Maybe bash does not intervene in the line execution?
Carlos, You are right on-the-money with your thinking. It looks like if the pipes are contained in a variable expression, then they are not seen at all and lynx just happily reads past them until it hits an '-e' and pukes. I guess the problem is that I can't put an explicit pipe in unless I break the expression up something like this: dumpSTR="lynx -dump $url ${rpmSTR} | ${debugSTR_1} | ${debugSTR} | grep http | sed -e 's/^.*\shttp/http/'${dirSTR}" but then you have the problem of $rpmSTR being undefined or "" if the option isn't set and that results in either: | | - bash: syntax error near unexpected token `|'; or | "" | - bash: : command not found I guess I would need some type of 'stub' function that read stdin and then wrote to stdout. I'll keep my 'if' jungle at that point :p -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org