A suggestion: it might be nice if the documentation used long options by default. I think all of these look clearer: they're more self-documenting, so it's much more obvious what each one does. (If I see -t and it's extracting the text, I end up thinking "ah, I bet the -t stands for --text, and if the docs used the long options then I'd know that already without having to reverse-engineer it in my head.)
It's also subtle encouragement to others to use long options when describing htmlq, which makes everyone else's articles about it slightly more friendly and slightly less impenetrably techie, perhaps.
A suggestion: it might be nice if the documentation used long options by default. I think all of these look clearer: they're more self-documenting, so it's much more obvious what each one does. (If I see
-tand it's extracting the text, I end up thinking "ah, I bet the-tstands for--text, and if the docs used the long options then I'd know that already without having to reverse-engineer it in my head.)It's also subtle encouragement to others to use long options when describing htmlq, which makes everyone else's articles about it slightly more friendly and slightly less impenetrably techie, perhaps.