Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Terminal doesn't reset after exiting hopa
See original GitHub issueWhen you run hopa, and then exit hopa, either through the menu or via ctrl+c, the terminal does not reset properly.
I have tested this on both windows and macos and have experienced different effects, most notably duplicated keystrokes on windows and being unable to scroll through the terminal on macos.
Running reset on macos fixes the issue
Issue Analytics
- State:
- Created 4 years ago
- Comments:8 (3 by maintainers)
Top Results From Across the Web
The Unresponsive Terminal - Learning the UNIX Operating ...
If this works, your terminal needs to be reset to fix the RETURN key. Some systems have a reset command that you can...
Read more >Terminal isn't reset to previous state when quitting a man ...
When I view a man page and then quit it - by pressing Q - the contents of the man page stay in...
Read more >crossterm: Terminal's state not always reset on exit #80
When running examples with the crossterm feature enabled, I found that the cursor remains hidden and mouse capture remains enabled sometimes ...
Read more >How to reinitialize a terminal window instead of closing it ...
This just reloads your PATH and some environment variables. It doesn't "reset" anything. @NES's answer is the correct one. – Cerin. Jun 12,...
Read more >Release Note
Remove the Firmware Upgrade Card and then press the Exit button." Premature removal of the card will cause the upgrade to fail. When...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
My portion of the issue has been resolved, thanks for the hard work and dedication to the project! ❤️
Sorry for the delay, I can confirm that 1.3.2 fixed the issue, thanks again!