News for hackers. Stuff that matters.

A comment on Use long flags when scripting (2013). Parent comment

Re:Use long flags when scripting (2013) by zbuf on Friday September 18, 2020 @02:53PM (#24520560)
Personally a fan of '--verbose' to be honest. It's clear. "grep -v" anyone?
[ Parent | on HN ]
Re:Use long flags when scripting (2013) by frenchy on Friday September 18, 2020 @03:08PM (#24520730)
Particularly in this case, because `-v` sometimes means "print out the version number".
[ Parent | on HN ]
Re:Use long flags when scripting (2013) by jfrunyon on Friday September 18, 2020 @03:11PM (#24520758)
That's why they mentioned `grep -v`. Go look it up. It doesn't mean verbose OR version.

Doubt you'd be printing out a version number in a shell script though.

[ Parent | on HN ]
Re:Use long flags when scripting (2013) by cogburnd02 on Friday September 18, 2020 @03:52PM (#24521199)
You may want to compare a version number of a command to make sure it's bigger than (or equal to) the minimum version required by your script, though.
[ Parent | on HN ]
Re:Use long flags when scripting (2013) by codazoda on Friday September 18, 2020 @04:42PM (#24521694)
>-v, --invert-match

> Selected lines are those not matching any of the specified patterns.

For the lazy.

Edit: I don't know hackernews formatting and I'm among the lazy, so... Marked as "won't fix".

[ Parent | on HN ]
Re:Use long flags when scripting (2013) by mattkrause on Saturday September 19, 2020 @11:22AM (#24528012)
Of all the options, it is so fitting and proper to use the long form for —-verbose.
[ Parent | on HN ]