Support long options

[Kaligule]

I love batsignal, it so fun to work with. Thank you.

In practice I assume that batsignal is likely to be used in a script of some sorts (and not being run manually on the commandline).
Therefore I would prefer to use long options, because they are more readable and selfexplaining, especially If one doesn't have the manpage open right now. Saving space and time typing by using short options is not a concern in these cases.

Could batman start supporting long options?

Examples would include:

• -h = --help
• -v = --version
• -f = --full
• -W = --warning
• -C = --critical
• -D = --danger
• -f = --full
• -e = --expire

[electrickite]

I agree that long options are more readable and would be a nice affordance, but one of the goals of batsignal is to be dead simple and reasonably portable. currently (AFAIK) the project uses POSIX compliant C features and (other than a well supported shell command convention in the the Makefile) a cross-platform build process.

Command line option parsing is done using the getopt function from unistd.h. There is a GNU extension, getopt_long, which would be the most straightforward way to add long option parsing, but I am hesitant to add a dependency on Glibc.

I would definitely be open to suggestions or PRs that don't introduce that type of dependency, though.

[Kaligule]

I agree that simplicity is definitely a feature of batsignal and a new depency just for this might not be worth it. Of course one could code this by hand, but that's not reasonable. I don't know enough about getopt (or C) to give advice here. Thanks.