-
Notifications
You must be signed in to change notification settings - Fork 137
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
Ctrl-C improperly handled when q.echo = false #236
Comments
I'll be having a look at it as soon as possible. Thanks for reporting the issue! 👍 |
Hi, No worries, this isn't in any way a blocking/problematic bug, so don't feel pressed to fix this :) I might look into it on the train sometime, but no promises here :) |
I've just run into this as well - we can work around it for now, and if I have time for a PR I'll raise one, but also subscribing for notifications if you happen to fix it before I do. Cheers! |
io/console #getpass handles ctrl-C correctly |
Just a thought, you could always throw the exit in with the character checks in HighLine#get_line_raw_no_echo_mode, this would "catch" (I say that because
|
Hi,
Just noticed something a little odd with the handling of a ctrl-c while in an
ask
with echo set to false.Two things happened here:
q.echo
is not set to false)I'm using highline-2.0.0.gem, and
zsh
in the standard terminal app in OSX.The text was updated successfully, but these errors were encountered: