I am begging developers of command line tools to simply write an example of the working command after the options.

reading a 1000 lines of documentation with a million -flags and -switches and then guessing how im supposed to use them is not fun. many many non coders want to use your program. Let us copy paste the working command and then edit to our needs

@nix "reading a 1000 lines of documentation with a million -flags and -switches and then guessing how im supposed to use them" Wait a second, you're saying the problem is that people *do read* the documentation but it doesn't answer the their questions clearly and they are forced to guess? I thought the problem was that people, very reasonably, want to read as little as possible, so they *don't read* a 1000 lines of documentation, instead they look for the examples which are often lacking. I agree with you that adding examples would be good, but I think there is a chance you've misdiagnosed the problem.

@oantolin @nix

Possibly the reason people don't read thousands of lines of documentation is that they've learned that it still won't answer their question even if they put the effort in.