I mentioned this in #61 as well, but it happens across several commands. Basically, the command fails out, but then doesn't return me to my prompt. Instead, it keeps asking me questions about a thing that it's already decided I can't do. Since this isn't normal command line behavior, I don't notice, and try to do something else, and end up in these error loops:
I can control C out of it eventually, but it's super annoying behavior. Users shouldn't have to keep interacting with a command and answering its questions when it has already failed.
I mentioned this in #61 as well, but it happens across several commands. Basically, the command fails out, but then doesn't return me to my prompt. Instead, it keeps asking me questions about a thing that it's already decided I can't do. Since this isn't normal command line behavior, I don't notice, and try to do something else, and end up in these error loops:
I can control C out of it eventually, but it's super annoying behavior. Users shouldn't have to keep interacting with a command and answering its questions when it has already failed.