> Adding an option that aborts and trashes the state directory is much > worse than not having a choice other than drop and keep, which is in > turn a bit worse than having a way to countermand an option that was > given earlier on the command line. Another option to countermand an option is only meaningful when it can be applied as a resume value but not in such a case, I think. "--empty=<option>" is only kept in each am session, and it seems we can't countermand the option after the session.