-
Notifications
You must be signed in to change notification settings - Fork 744
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
bug: loss of input on ReleaseTerminal / Bubbletea shutdown #616
Comments
Is there any update on this? This seems to happen pretty consistently when mouse input gets involved. |
@chabad360 can you say more? What are the symptoms? |
After clicking around for a bit (an easy way to speed this up is to click outside the terminal), the entire system stops receiving input but does still respond to other things like resizing the window. If I force kill the program with pkill, the terminal no longer accepts input. Now that I'm rereading the issue, it seems different, but still related. |
Thanks. I think you are experiencing the symptoms of a different problem, but i believe it could also improve with this change #569 |
And also this change #570 |
hmm, |
Is there any plan to address this issue in a near future ? |
It is not currently possible to integrate Bubbletea-based programs in scripts or unit tests that buffer terminal input
across multiple runs of the Bubbletea event loop.
The specifics are explained here: https://dr-knz.net/bubbletea-control-inversion.html
In summary, the input reader function is "greedy" but drops/forgets input event messages during
ReleaseTerminal()
. This is where the input is lost.The text linked above outlines a solution:
Update
calls.The text was updated successfully, but these errors were encountered: