-
Notifications
You must be signed in to change notification settings - Fork 332
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
interactive CLI has no quit or exit command. #1414
Comments
Thanks for the suggestion. I'd be happy with |
just thinking out loud here, but perhaps this could be "fixed" by simply updating the input descriptions for interactive mode? pressing "escape" cancels the interactive mode prompt, returning the user to their terminal, as (I imagine) the OP would expect |
@ZaLiTHkA Good to know. But not very obvious or intuitive: In my experience, |
@vassudanagunta I agree with you on that point, it's definitely not very "intuitive" as it is right now. on the other hand, the fact that there is already a mechanism in place to "cancel" interactive mode also means that adding support for a either way, a short message in the initial usage notes would clear this up for everyone. |
Signed-off-by: David Edler <[email protected]>
Currently the only way, AFAIK, is to issue a terminal kill command. You can also press
ENTER
and then notENTER
butn
at the next prompt (which is unintuitive when looking at the initial list).Ideally
q
orx
to exit with nothing upgraded or changed.If agreed, I can take a stab at a PR when I get some free time.
The text was updated successfully, but these errors were encountered: