On Fri, 27 Nov 2015 11:15:44 +0000, Daniel Silverstone wrote: > This seems odd Chris. > > Instead of stopping consumption of arguments on the first non-configuration > argument, it instead ends up swallowing the entire commandline rendering the > rest of commandline processing worthless. > > Could you either fix this so that you get your desired behaviour while not > breaking processing for the rest of us; or else revert the change?
I've reverted and fixed my problem a different way. The issue I was having was the commandline processing was stopping on encountering -v, so it was impossible to specify commandline options with logging enabled, which seemed ridiculous. I hadn't appreciated that there was such strict ordering for arguments, and code further down meant they were now being obliterated. My apologies. Chris
