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

Watch mode to re-render the current screen instead of clearing the scrollback #10674

Closed
borekb opened this issue Oct 21, 2020 · 4 comments
Closed

Comments

@borekb
Copy link

borekb commented Oct 21, 2020

🚀 Feature Proposal

Watch mode currently prints test outputs over and over again, filling up scrollback, which is probably why a drastic measure was taken back in 2016 and the scrollback has been cleared ever since, see #1861. Clearing a scrollback means that I cannot scroll to previous output in my terminal, so it's a small "data loss".

iTerm2 beta (I'm on 3.4.0beta10) started disallowing this and shows this warning:

Screen Shot 2020-10-21 at 16 07 37

The current iTerms stable, and I guess many other terminals, just accept the control character and clear the scrollback.

The proposal is to implement the watch mode in a similar way that vim / less / man and others that temporarily redraw their UI but don't leave traces in terminal history (sorry if I'm using imprecise terms). That means that the watch mode would have no big reason to clear the scrollback, the iTerm warning would go away and previous terminal data would be preserved.

@pfernandez
Copy link

I'd call this a bug report rather than a feature request. Clearing the entire scroll history is a problem.

@github-actions
Copy link

This issue is stale because it has been open for 1 year with no activity. Remove stale label or comment or this will be closed in 14 days.

@github-actions github-actions bot added the Stale label Feb 25, 2022
@github-actions
Copy link

This issue was closed because it has been stalled for 7 days with no activity. Please open a new issue if the issue is still relevant, linking to this one.

@github-actions
Copy link

github-actions bot commented May 5, 2022

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Please note this issue tracker is not a help forum. We recommend using StackOverflow or our discord channel for questions.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 5, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants