> We both disagree with you. What would that definition be? A “bash one-liner” as in common use is a chain of commands using any combination of pipes, subshell

> We both disagree with you. What would that definition be? A “bash one-liner” as in common use is a chain of commands using any combination of pipes, subshells, variables, tests, loops, etc. The distinction between a “bash one-liner” and a “bash script” is that extraneous white space is removed and generally speaking should still be readable. Admittedly mine is pushing the limits of readability do to the advanced bash syntax, but I still feel it qualifies. Also, just because my reply was threaded two levels below yours doesn’t mean I was replying to you. I had upvoted you in fact as I actually agree with you re: oathtool example. The party I was replying to actually doesn’t agree with you and thinks that the oathtool example is a “bash one-liner” and that because I call other basic Unix commands mines not, which is just silliness.