Linked by pkrumins on Thu 19th Feb 2009 12:17 UTC
Thread beginning with comment 349850
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 06/19/13 23:02 UTC, submitted by M.Onty
Linked by Thom Holwerda on 06/19/13 22:28 UTC
Linked by Thom Holwerda on 06/18/13 22:33 UTC
Linked by Anonymous on 06/18/13 22:26 UTC
Linked by Thom Holwerda on 06/18/13 22:25 UTC
Linked by Thom Holwerda on 06/18/13 17:45 UTC
Linked by Thom Holwerda on 06/18/13 17:32 UTC, submitted by poundsmack
Linked by Thom Holwerda on 06/17/13 17:58 UTC
Linked by Thom Holwerda on 06/17/13 17:52 UTC
Linked by Thom Holwerda on 06/14/13 21:03 UTC
More News »
Sponsored Links



Member since:
2005-07-06
I wouldn't really say that AWK and SED encourage these one liners, rather I would say they enable one liners.
When you work with these tools to the comfort level that you can just spit out these one liners, that's where this facility becomes a powerful command line tool rather than a just a scripting language.
I don't think twice about just pounding out long pipelines in the shell, or short scripts. Similarly, if it can fit on one line, I'll consider doing the same with AWK or SED.
These are one off events that never last beyond perhaps the shell history.