-
Notifications
You must be signed in to change notification settings - Fork 264
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
Dropping AlternateScreen breaks alternate screen mode with Crossterm instance #88
Comments
It turns out it is possible to stay in raw mode by calling ...
{
let mut alternate_screen = screen.enable_alternate_modes(raw_mode).unwrap();
alternate_screen.screen.disable_drop();
crossterm = Crossterm::from_screen(&alternate_screen.screen);
}
// <-- Dropping alternate_screen here
... However this feels like a bit of a hack. Alternate screen mode still breaks after the drop. |
In the future, this might be more flexible and I will build in the functionality to have multiple screen buffers who have their own settings. You can be using I get your argument that the user might be misled and I take a look to see if I can improve the docs here. Are there any problems you are encountering with otherwise I'll close this issue. |
Thanks for the quick reply. I think Given that Edit: Consuming the |
closing this, because it is answered if you have any more question feel free to reopen. |
When creating a
Crossterm
instance from anAlternateScreen
, dropping theAlternateScreen
breaks both raw and alternate screen mode, see example above. This gets tricky when users assume it is possible to only store theCrossterm
instance to draw to the alternate screen.The text was updated successfully, but these errors were encountered: