An example directory of common usage patterns

The decorator would allow the use of async functions by running them using loop.run_until_complete. This should be implemented in a way that doesn't prevent execution if asyncio isn't present. (import within the decorator will do)

I guess there is no real consistent scheme, but quite a few tools capitalize the help section headers.
So maybe a flag could be added to do the same when using kotlin-argparser.

So showiing

Usage: [-h] [-a] IMAGE-DIRECTORY MARKDOWN-FILES...

Optional arguments:
  -h, --help        show this help message and exit

  -a, --auto        Automatically remove orphan images


Position

Apparently GoDoc cannot show documentation for exported methods of un-exported structs, and it makes no sense to export parser and/or command, thus this project should provide its own documentation page.

Hi,
Will it be possible to add support for optional configuration files, the same general idea as ConfigArgParse: https://github.com/bw2/ConfigArgParse

The idea is to be able to pass a file path as an argument and some additional arguments.
the logic should be to first parse the config file and then parse the rest of the arguments.
Thank you!