Gracefully exit application

[jerrytingley]

I've noticed a general issue with ncurses applications where they do not always exist gracefully. Once you Ctrl-C from the applciation, typing into the shell shows nothing and pressing enter shifts the prompt to the right. Usually requires one to just close that terminal and open another one. Is there a way for globe to exit curses in a way as to return the terminal to its original state?

[adamsky]

Hey! Not sure what you mean there. This project doesn't use ncurses, it uses crossterm instead. In terms of graceful exit, it's hard to tell what's the issue there. For most people it works just fine from what I've heard.

Could you share some information about your system? Perhaps the terminal you're running doesn't play nicely with crossterm or something.

[jamesblau]

Same problem here: Ubuntu 20.04.1 LTS, with kitty terminal (TERM=xterm-kitty), gnome-terminal (TERM=xterm-256color), and sucklesss simple terminal (TERM=st-256color).

[adamsky]

Does Ctrl-C end up producing the same result as exiting by pressing any character key?

[jamesblau]

Yep, same result.

Cargo 1.44.1, rustup 1.22.0 if that matters.

Same result in kitty terminal (TERM=xterm-kitty), gnome-terminal (TERM=xterm-256color), and suckless simple terminal (TERM=st-256color), assuming I'm using pan-up-panic branch (only one that works for me).

[adamsky]

I'm unable to replicate on any of my machines, tried different terminals and older rust versions.

[jerrytingley]

Whoops should have checked if it was using curses before posting, I've had this issue when I worked on a curses application. I remember having to write some code to exit the application such that the the prior state of the terminal was set on quit and thought something conceptually similar was needed here, but not sure how that all works in crossterm.

For reference I'm on Ubuntu LTS 20.04.01 and tested with gnome-terminal/bash with TERM=xterm-256color. Interesting that @jamesblau and I have the nearly identical configurations and are having the same issue, just not sure what common denominator would be the most likely culprit.

[evan-chaney]

I checked with kitty and gnome-terminal on Fedora 33. Tried xterm-256color, xterm and screen-256color and could not replicate.