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
Ever since I ported my applications from Termion to Crossterm, the terminal settings do not get restored when the application quits. But that only happens if my login shell is bash. If my login shell is fish, then everything works fine. Is there some standard teardown command needs to be used with Crossterm?
To Reproduce
If using ZFS on FreeBSD (and presumably Linux too)
Steps to reproduce the behavior:
Expected behavior
When the application exits, the terminal's original behavior should be restored. Keypresses should be echoed to the screen, and newlines should include a carriage return.
OS
FreeBSD 13.2, 14.0, and 15.0-CURRENT
Terminal/Console
xterm-256color, tmux-256color, and reportedly some kind of OSX terminal, too.
The text was updated successfully, but these errors were encountered:
Oh, I think I've figured out. I was missing crossterm::terminal::disable_raw_mode. I should've read the docs better. I guess I was just confused because I didn't need that with Termion, nor with certain shells.
Describe the bug
Ever since I ported my applications from Termion to Crossterm, the terminal settings do not get restored when the application quits. But that only happens if my login shell is bash. If my login shell is fish, then everything works fine. Is there some standard teardown command needs to be used with Crossterm?
To Reproduce
If using ZFS on FreeBSD (and presumably Linux too)
Steps to reproduce the behavior:
If not using ZFS, but still using FreeBSD
Expected behavior
When the application exits, the terminal's original behavior should be restored. Keypresses should be echoed to the screen, and newlines should include a carriage return.
OS
Terminal/Console
xterm-256color, tmux-256color, and reportedly some kind of OSX terminal, too.
The text was updated successfully, but these errors were encountered: