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
From what I have read from raw mode in the terminal, there is way to "restore" the terminal state when the application exits, so that the terminal goes back to where it was.
It means storing the original state in memory though.
Is there a good reason why it is not implemented in neatvi? The outcome is that I continue to see some part of the editing session when I quit neatvi, instead of just being back to where I was before launching it.
The text was updated successfully, but these errors were encountered:
From what I have read from raw mode in the terminal, there is way to "restore" the terminal state when the application exits, so that the terminal goes back to where it was.
It means storing the original state in memory though.
See [this link](https://viewsourcecode.org/snaptoken/kilo/02.enteringRawMode.html#disable-raw-mode-at-exit) or the below snippet for more info.
```
struct termios orig_termios;
void disableRawMode() {
tcsetattr(STDIN_FILENO, TCSAFLUSH, &orig_termios);
}
```
Is there a good reason why it is not implemented in neatvi? The outcome is that I continue to see some part of the editing session when I quit neatvi, instead of just being back to where I was before launching it.
Neatvi restores terminal state but not terminal contents.
Ali
From what I have read from raw mode in the terminal, there is way to "restore" the terminal state when the application exits, so that the terminal goes back to where it was.
It means storing the original state in memory though.
See this link or the below snippet for more info.
Is there a good reason why it is not implemented in neatvi? The outcome is that I continue to see some part of the editing session when I quit neatvi, instead of just being back to where I was before launching it.
The text was updated successfully, but these errors were encountered: