it seems that a nonexistent config that is specified with --config/-c is reported to the user first as missing defaults for mandatory arguments. this is never desirable: a config file that is specified but that does not exist should always result in error with informative message.
it seems that a nonexistent config that is specified with
--config/-c
is reported to the user first as missing defaults for mandatory arguments. this is never desirable: a config file that is specified but that does not exist should always result in error with informative message.