Fwd: [DISCUSS] 10 Good Unix command line habits

[Luke-Jr]

Notes:
In "Quote variables with caution", it says to use square brackets, and then 
goes on to give a correct example with curly braces.
"Stop piping cats" only refers to piping to grep, but in reality there's 
almost never a good reason to pipe a single-file cat. The < operator provides 
a file on standard input. So "cat foo | wc -l" can become "wc -l < foo"


On Sunday 17 December 2006 05:47, Don Ellis wrote:
> KC Guys - I thought you might like to see this item.
>
> --Don Ellis
>
>
> ---------- Forwarded message ----------
> From: Ed Howland <ed.howland at gmail.com>
> Date: Dec 16, 2006 2:09 PM
> Subject: [DISCUSS] 10 Good Unix command line habits
> To: discuss at sluug.org, Central West End Linux Users Group <
> cwe-lug at lists.firepipe.net>
>
>
> A good article from IBM developerWorks.
>
> http://tinyurl.com/vof3r
>
> Or the full thing:
> http://www-128.ibm.com/developerworks/aix/library/au-badunixhabits.html?ca=
>lnxw01GoodUnixHabits
>
> Now some of the examples don't work (mkdir with parenthesized dirs) on
> Debian-like systems. But you might find a few gems there. I did.
>
>
> Ed
> --
> Ed Howland
> http://greenprogrammer.blogspot.com
> -------
> St. Louis Unix Users Group - http://www.sluug.org/
> To unsubscribe from the SLUUG discussion mailing list, send a message to
> discuss-request at sluug.org with the word 'unsubscribe' as the body

-- 
I digitally sign my emails.  If you see an attachment with .asc, then that 
means your email client doesn't support PGP digital signatures.
http://www.gnupg.org/documentation/faqs.html#q1.1