Use long flags when scripting

Re:Use long flags when scripting by fusiongyro on Monday February 04, 2013 @01:19PM (#5165920)

There's something to be said for the automatic recognition that something like "tar zxvf foo.tar.gz" has, versus the verbose "tar --gzip --extract --verbose --file foo.tar.gz." It feels terribly ponderous to do the latter. That said, when I see a command I don't recognize immediately ('sed -n' comes to mind for some reason) I would benefit from seeing the long option. The other side of the coin is that once I go look up 'sed -n' I'll probably remember it for next time.

[ Parent | on HN ]

Re:Use long flags when scripting by sabraham on Monday February 04, 2013 @02:06PM (#5166259)

http://xkcd.com/1168/

[ Parent | on HN ]

Re:Use long flags when scripting by jlangenauer on Tuesday February 05, 2013 @03:21AM (#5169717)

I always remember this as "eXtract Ze Vucking File".

(You have to say it in a bad german accent.)

[ Parent | on HN ]

Re:Use long flags when scripting by ralph on Monday February 04, 2013 @02:58PM (#5166666)

Aside,

    sed -n /re/p

is grep. sed's default is to print every line at the end of the script, -n says not to. Larry Wall rightly had perl(1) inherit -n along with perl's -p.

[ Parent | on HN ]