On 20.09.2017 19:14, Phil Susi wrote: > I see now. I believe it used to be that it would consume the "1" > command line argument as the answer to the yes/no question. I think > there was a patch to fix that a while ago. I had thought it just made > the exception handler not take input from the command line, but now it > appears to discard the remainder of the command line. It shouldn't be > doing that. > > By moving the check, if you answer No, then you first get prompted for > the end, even though it is a moot point. Interactively it would be nice > to avoid this, but when using the command line, it is probably better > your way since otherwise, answering No and skipping the End question > would leave the end value in the command line buffer and then try to > interpret that as another command.
Thanks, I'll send a v2 which addresses this.
