Skip to content
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

Using atuin TUI often leaves terminal in an unusable state #522

Closed
peterjanes opened this issue Sep 9, 2022 · 3 comments
Closed

Using atuin TUI often leaves terminal in an unusable state #522

peterjanes opened this issue Sep 9, 2022 · 3 comments
Labels
bug Something isn't working shell-bash Impacts bash specifically

Comments

@peterjanes
Copy link

When I use the Atuin TUI (via Ctrl+R keybinding) and exit, either by selecting a command or hitting Ctrl+C, my terminal is often left in a state where it doesn't echo keypresses. I'd estimate this happens 10-20% of the time; there's no other pattern I've been able to discern.

Workaround: If I blind-type "stty sane" things go back to normal.

$ atuin --version
atuin 0.10.0
$ bash --version
GNU bash, version 5.1.16(1)-release (x86_64-redhat-linux-gnu)
[copyright/license blocks elided]
$ cat /etc/system-release
Fedora release 36 (Thirty Six)
@conradludgate
Copy link
Collaborator

Might be related to #492

@conradludgate conradludgate added bug Something isn't working shell-bash Impacts bash specifically labels Sep 10, 2022
@conradludgate
Copy link
Collaborator

Can you describe what "unusable state" looks like? I'll setup bash and try to replicate

@peterjanes
Copy link
Author

I think it's a duplicate of #492 as you suggested.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working shell-bash Impacts bash specifically
Projects
None yet
Development

No branches or pull requests

2 participants