omego configuration file and command line parsing about omego HOT 4 CLOSED

Assuming gh-38 goes through, we'll have at least one dependency (yaclifw). For 1 that means maybe the config parsing should go there? For 2 that likely means it's not a big problem to add the requirement. I think docopt is really slick, but I haven't tried much in anger. I do worry that we could run into barriers that we'll have to workaround, which we've already handled with argparse. My vote then would likely be for 1, especially if we could also use it for supporting a ~/.omerorc!

from omego.

@joshmoore @sbesson are you planning any significant changes to yaclifw? If not I'll start porting my changes from https://github.com/manics/omego/tree/argparse_config_file to yaclifw so we can test and discuss.

from omego.

I have nothing planned.

from omego.

See #76

from omego.