-
-
Notifications
You must be signed in to change notification settings - Fork 6.5k
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
Clear scrollback on terminal clear in watch mode #1861
Comments
We clear it every time we re-run tests. It just seems that terminals like iterm allow to scroll back up indefinitely. I know @gaearon has done a ton of work with this. |
Hmmm... Interesting, when I hit CMD+K, it clears the terminal entirely and I can't scroll up (in contrast to the |
@cpojer I'm using standart terminal app What you think guys? |
I'm happy to support this in Jest but I want to get some input from @gaearon first. Also, how does this behave on windows? Do we need to do a platform sniff and print different things or will this work on both? |
Tested on windows 7 cmd - UPD |
In this case, would you mind sending a PR with the new behavior for osx (and linux?) and the old one for windows? Can you double check it works well on linux, too? |
yes, but may be wait for @gaearon message? Interesting, what he can say on it |
Send a PR and I'll be happy to test it with a few edge cases I know have been broken in the past last time I tried to fix this. |
let's continue the conversation in the PR. |
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. |
Output grows really fast in watch mode, and after sometime it gets really hard to navigate through terminal output with scrollbar.
Clearing scrollback before each run will fix that.
OS X : hotkey is CMD+K. but in watch mode you fast get tired of pressing it each time
How to do it programmatically:
printf '\e[3J'
[1][1] VIA: http://apple.stackexchange.com/a/113168
P.S. It's only about watch mode
The text was updated successfully, but these errors were encountered: