You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
After editing my config from "inside" lazydocker, I was faced with a prompt that would not actually accept any input.
To Reproduce
Steps to reproduce the behavior:
Go to 'Status'
Click on 'About'
Press 'e' to edit the config
Exit vim with :q
Press 'Enter' to dismiss the prompt
Expected behaviour
I should be taken back to lazydocker's UI.
Screenshots
Desktop (please complete the following information):
OS: macOS 10.14.5
Lazydocker Version 0.2.4 (from Homebrew)
Additional context
This issue does not consistently reproduce for me. It triggered for me in a session where I'd been exploring for a while, but I haven't seen it again in a new session.
The text was updated successfully, but these errors were encountered:
I've seen this myself a couple times too. I believe it's an issue with how we're using termbox-go. termbox-go wasn't really made to be initialized and closed multiple times in a single session, so it has some package-level variables being used for state. I think that's the core of the issue: it might take a bit of work on the termbox-go fork to make it deal better with e.g. exiting PollEvent() when we want it to, and then being able to listen for more events when we call PollEvent() again. I think it's something along those lines
Describe the bug
After editing my config from "inside" lazydocker, I was faced with a prompt that would not actually accept any input.
To Reproduce
Steps to reproduce the behavior:
:q
Expected behaviour
I should be taken back to lazydocker's UI.
Screenshots
Desktop (please complete the following information):
Additional context
This issue does not consistently reproduce for me. It triggered for me in a session where I'd been exploring for a while, but I haven't seen it again in a new session.
The text was updated successfully, but these errors were encountered: