-
Notifications
You must be signed in to change notification settings - Fork 42
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
Unexpected behavior on certain inputs #196
Comments
This might be related to issue #98 ? |
Hey @EpicDavi, thanks for trying out pick. I'm happy you like it! When running To exit pick you can press Ctrl-C. When you do, you should see the usage message that
Could you elaborate on this? Maybe upload a screen recording? This does sound like a bug but I can't reproduce it on macOS 10.12.5 running pick from bash in Terminal. Are you running a different shell or terminal emulator? |
Just tried it on another machine (macOs 10.12) and am having the same issue. However, I tried it on the built-in Terminal (instead of iTerm2) and the issue no longer occurs. This makes me think it is an issue with iTerm2 (3.0.15)? Anyways, here is what the issue looks like, if you are curious: https://asciinema.org/a/xqJPG5vAVHkkIvNdblbiOuKDJ |
Thanks for the report, I'm able to reproduce this using $ pick </dev/null Please try out #198 and see if it solves the problem. |
Fix has been merged, closing for now. |
I recently started playing around with pick (1.6.1) and it's fantastic! I discovered some weird behavior while messing around with it.
Here is an example:
pick -h | pick
. Running this initially results in a blank screen but as characters are inputted, the current string is duplicated until it reaches the top of the screen.Piping in
pick -h
is probably not a typical use case, but the behavior that results is strange.EDIT: I am running macOS 10.12.5, if this helps at all.
The text was updated successfully, but these errors were encountered: