[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: Bash help requested: Capturing command errors within pipes



On Friday, Mar 20th 2009 at 00:39 -0000, quoth Cameron Simpson:

=>Your quotes are unneeded here. Plenty of people find the "" marks and in
=>similar cases, to use ${foo} instead of $foo elsewhere, but I find the
=>syntactic noise annoying if there's no other necessity.
=>
=>Also, you should never use UPPER CASE names for script local variables (i.e.
=>that are not to be exported). I give some background why here:

Yes, yes yes a thousand times yes. I encourage people to always quote in 
an informed manner. This also can be expressed in a style that uses 
minimal quotes.
1. Don't quote if not necessary.
2. Use single quotes if quotes are needed but no variable interpolation is 
used.
3. Only use double quotes if you need variable interpolation.

-- 
Time flies like the wind. Fruit flies like a banana. Stranger things have  .0.
happened but none stranger than this. Does your driver's license say Organ ..0
Donor?Black holes are where God divided by zero. Listen to me! We are all- 000
individuals! What if this weren't a hypothetical question?
steveo at syslang.net


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]