On Sunday 16 December 2007 20:05, David C. Rankin wrote: > Otto Rodusek (AP-SGP) wrote: > > ... > > > > Hi, > > > > Your script is wrong. change all your echo to (use double quotes) > > > > echo -e "*** /usr/lib/libGL.so Config \n" > > > > and all your probs will disappear!! > > Thank you Otto, > > For solving my CRI! I missed that in man bash, but I knew I had to > quote the escape sequence. It was a forest for the trees issue. Also, > single quotes work just fine as well.
In this case they do, but they're not equivalent. Double quotes do not prevent shell variable references from being expanded. Single quotes do. > The error is really weird. It was the result of the 'echo *' > statement. Why it would interpret the *** is also just as strange. This has nothing to do with the "echo" built-in, per se. Globbing (the process of expanding shell wild-card arguments) logically precedes the invocation of the command whose arguments are generated by the globbing process and is entirely independent of the command for which the expansion is being carried out. Since the glob interpretation of '*' is "zero or more occurrence of any character," putting more than one together is just redundant (they're idempotent). > -- > > man bash (line 2988) > > echo [-neE] [arg ...] Output the args, ... As I said, echo isn't at issue. Shell wild-card globbing is. > -- > David C. Rankin Randall Schulz -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
