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.

Sign up for GitHub

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

Jump to bottom

Terminal Rendering Issue; Insiders 1.25 on Windows 10 #51798

Closed
christopherwolf1 opened this issue Jun 13, 2018 · 4 comments
Closed

Terminal Rendering Issue; Insiders 1.25 on Windows 10 #51798

christopherwolf1 opened this issue Jun 13, 2018 · 4 comments
Assignees
@Tyriar
Labels
*duplicate Issue identified as a duplicate of another issue(s) terminal Integrated terminal issues

Comments

@christopherwolf1
Copy link

  • VSCode Version:
    Version: 1.25.0-insider
    Commit: 583f1e4
    Date: 2018-06-13T05:18:10.709Z
    Electron: 2.0.2
    Chrome: 61.0.3163.100
    Node.js: 8.9.3
    V8: 6.1.534.41
    Architecture: x64

  • OS Version:
    Windows 10 Enterprise Version 1803
    Build 17134.112

  • Steps to Reproduce:

  1. Launch Visual Studio Code Insiders
  2. Wait for Integrated Terminal to load; unless a carriage return and line feed is executed, the portion beneath the active command line in the terminal is pure black. After a CRLF event, the new line restores the background to the normal color, but the black portion beneath still remains. See attached GIF.

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

vscode-insiders_integratedterminalbug
@vscodebot vscodebot bot added the terminal Integrated terminal issues label Jun 13, 2018
@jordanmaslyn
Copy link

Duplicate of #51774

@yume-chan
Copy link
Contributor

yume-chan commented Jun 14, 2018 •
edited
Loading

Duplicate of #51749

It has already been fixed in today's insiders version.

@Tyriar Tyriar added the *duplicate Issue identified as a duplicate of another issue(s) label Jun 14, 2018
@vscodebot
Copy link

vscodebot bot commented Jun 14, 2018

Thanks for creating this issue! We figured it's covering the same as another one we already have. Thus, we closed this one as a duplicate. You can search for existing issues here. See also our issue reporting guidelines.

Happy Coding!

@vscodebot vscodebot bot closed this as completed Jun 14, 2018
@christopherwolf1
Copy link
Author

Confirmed for me with the latest insider's version, as stated above; pretty fast fix. 😃 👍

@vscodebot vscodebot bot locked and limited conversation to collaborators Jul 29, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@Tyriar Tyriar

Labels
*duplicate Issue identified as a duplicate of another issue(s) terminal Integrated terminal issues
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@yume-chan @jordanmaslyn @Tyriar @christopherwolf1