Should the defaults be given both here and in the individual flag descriptions?

I'm not sure whether here and elsewhere in DESCRIPTION where options (other than the one being described, ie -o --output-file here) are mentioned, it's better to use the long form or the short form as diff(1) and others do. Opinions welcome.

s/syslog tag/syslog-tag/

IMHO long form improves readability everywhere, I don't have to look up what -H means every time. Short options are difficult to remember unless you work with this tool every day.

But that being said I am happy to revert this if other reviewers feel the same.

Prevailing style is to insert a comma between the short option and long option in these listings, e.g.,

.It Fl c , Fl -change-dir

Might as well const this

I think we can drop this line, it's generally assumed that one will seek out the manpage for details.

why not add a --help while you're at it?

this way, drop the exit(1) from usage(), and exit as appropriate from main().

I was tempted to do this, but I was not sure if reviewers will like it. Not everybody likes the scope creep. I was planning to do this in a separate revision, but I will gladly add it to this diff!

how we could pass on an option here if we're printing onto stderr or stdout, because often you'd want to foo --help | grep topic

but i'd leave this to more experienced people

I like the idea and this is easy to do, but I will keep this feature for the next diff, I want to keep this change scoped

usage(0) would be better, and adjust usage to take a parameter and exit that value. Avoids errors like no {} from creeping in.

and could double for the other requested change, 'if usage() is not an error, write to stdout instead of stderr'

It is not me, it was like that before, I promise :)

Will fix.

ack, will do

ah, my bad , that was late change after adding --help...

I'm not aware of another program does that in the tree, so I'd suggest that we don't do that here.