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

[Terminal][macOS] Lost terminal output after clearing screen using ctrl+l #178743

Closed
sridhargopinath opened this issue Mar 30, 2023 · 4 comments
Closed
Assignees
Labels
confirmation-pending *duplicate Issue identified as a duplicate of another issue(s)

Comments

@sridhargopinath
Copy link

Does this issue occur when all extensions are disabled?: Yes

  • VS Code Version: Version: 1.77.0 (Universal)
  • OS Version: macOS Ventura 13.3

Steps to Reproduce:

  1. Print something to fill the entire screen
  2. ctrl+l
  3. Scroll up to see the previous output missing.

Does not reproduce on iTerm2

I have seen multiple issues around this topic but mostly on Windows and not on MacOS. I tried to reproduce on an iTerm2 terminal but doesn't reproduce. So something directly related to VSCode's integrated terminal.

Screen.Recording.2023-03-30.at.4.54.09.PM.mov
@meganrogge
Copy link
Contributor

meganrogge commented Mar 31, 2023

works for me on macOS in insider's - can you repro there?
https://user-images.githubusercontent.com/29464607/229181906-5911735c-f6f5-4bc8-b819-9f105469bf85.mov

@meganrogge meganrogge added the info-needed Issue requires more information from poster label Mar 31, 2023
@sridhargopinath
Copy link
Author

Yes, continues to be an issue even on Insider's build. Here's the screen capture:

Screen.Recording.2023-03-31.at.3.29.47.PM.mov

@meganrogge meganrogge added confirmation-pending and removed info-needed Issue requires more information from poster labels Apr 3, 2023
@sridhargopinath
Copy link
Author

@Tyriar Could you please take a look?

@Tyriar
Copy link
Member

Tyriar commented May 7, 2023

/duplicate xtermjs/xterm.js#1727

@Tyriar Tyriar closed this as completed May 7, 2023
@vscodenpa vscodenpa added the *duplicate Issue identified as a duplicate of another issue(s) label May 7, 2023
@github-actions github-actions bot locked and limited conversation to collaborators Jun 21, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
confirmation-pending *duplicate Issue identified as a duplicate of another issue(s)
Projects
None yet
Development

No branches or pull requests

4 participants