starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-03 21:25:34 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Weird grey text background rendering in VS Code integrated terminal using bash #169

New Issue
Closed
opened 2026-01-30 21:44:30 +00:00 by claunia · 5 comments
claunia commented 2026-01-30 21:44:30 +00:00
Owner
Copy Link

Originally created by @HymanZHAN on GitHub (Feb 25, 2018).

  • Windows build number: 10.0.16299.248

  • Problem: I just enabled WSL on my desktop and installed Ubuntu from the Microsoft Store. I didn't like the default color scheme (which is terrible to read btw) so I made use of the colortool and switched to solarized_dark. Everything looked great on bash and cmd. I also made use of ansi-dark theme to further polish text rendering.

ubuntubash

However, when I tried to use it within VS Code as the integrated terminal, there was something strange.

vscode_terminal

P.S. I am using the One Dark Pro theme extension on VS Code.

  • What should be happening instead: Actually I have used bash as my integrated terminal in VS Code for the past month on my laptop. Same use of colortool and the ansi-dark theme. I was expecting the same rendered result as on my laptop, which looks like this:
vscode_terminal_laptop
Originally created by @HymanZHAN on GitHub (Feb 25, 2018). * Windows build number: 10.0.16299.248 * Problem: I just enabled WSL on my desktop and installed Ubuntu from the Microsoft Store. I didn't like the default color scheme (which is terrible to read btw) so I made use of the [colortool](https://blogs.msdn.microsoft.com/commandline/2017/08/11/introducing-the-windows-console-colortool/) and switched to solarized_dark. Everything looked great on bash and cmd. I also made use of [ansi-dark theme](https://github.com/seebi/dircolors-solarized) to further polish text rendering. <img width="559" alt="ubuntubash" src="https://user-images.githubusercontent.com/26806995/36637010-61170386-19a0-11e8-8f20-15e02ae292ff.PNG"> However, when I tried to use it within VS Code as the integrated terminal, there was something strange. <img width="523" alt="vscode_terminal" src="https://user-images.githubusercontent.com/26806995/36636971-8da8a41e-199f-11e8-9cd3-67f864babf3b.PNG"> P.S. I am using the One Dark Pro theme extension on VS Code. * What should be happening instead: Actually I have used bash as my integrated terminal in VS Code for the past month on my laptop. Same use of colortool and the ansi-dark theme. I was expecting the same rendered result as on my laptop, which looks like this: <img width="362" alt="vscode_terminal_laptop" src="https://user-images.githubusercontent.com/26806995/36637027-b0e3cffc-19a0-11e8-8122-09a06f9330db.PNG">
claunia added the Product-ConhostArea-OutputIssue-BugResolution-Duplicate labels 2026-01-30 21:44:30 +00:00
claunia commented 2026-01-30 21:44:31 +00:00
Author
Owner
Copy Link

@sethrr commented on GitHub (Jan 24, 2019):

Did you ever resolve this? I am having the same issue with my bash integrated terminal

@sethrr commented on GitHub (Jan 24, 2019): Did you ever resolve this? I am having the same issue with my bash integrated terminal
claunia commented 2026-01-30 21:44:31 +00:00
Author
Owner
Copy Link

@HymanZHAN commented on GitHub (Jan 27, 2019):

@sethrr Sorry, I cannot reproduce this problem anymore. I reinstalled the whole Win10 on my machine a few months ago. I just tried and did not observe anything abnormal.

@HymanZHAN commented on GitHub (Jan 27, 2019): @sethrr Sorry, I cannot reproduce this problem anymore. I reinstalled the whole Win10 on my machine a few months ago. I just tried and did not observe anything abnormal.
claunia commented 2026-01-30 21:44:31 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Feb 6, 2019):

This looks like it was either fixed by us or a problem in winpty, the library VSCode uses on all versions of windows below 19H1.
@sethrr What versions of Windows and VSCode are you using? Have you set any unusual color schemes on the windows console (outside of VSCode?)

@DHowett-MSFT commented on GitHub (Feb 6, 2019): This looks like it was either fixed by us or a problem in _winpty_, the library VSCode uses on all versions of windows below 19H1. @sethrr What versions of Windows and VSCode are you using? Have you set any unusual color schemes on _the windows console_ (outside of VSCode?)
claunia commented 2026-01-30 21:44:31 +00:00
Author
Owner
Copy Link

@sethrr commented on GitHub (Feb 6, 2019):

Windows 10, VS Code 1.30.2

I haven't changed anything except for some Powershell profile colors which
don't seem to conflict. CMD and Powershell display fine in the Integrated
Terminal.

On Tue, Feb 5, 2019 at 10:36 PM Dustin L. Howett (MSFT) <
notifications@github.com> wrote:

This looks like it was either fixed by us or a problem in winpty, the
library VSCode uses on all versions of windows below 19H1.
@sethrr https://github.com/sethrr What versions of Windows and VSCode
are you using? Have you set any unusual color schemes on the windows
console (outside of VSCode?)

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Microsoft/console/issues/121#issuecomment-460898633,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ANdYeUFggYspq9n9_Y2U_PuFQy5pwe_cks5vKlvRgaJpZM4SSHvA
.

@sethrr commented on GitHub (Feb 6, 2019): Windows 10, VS Code 1.30.2 I haven't changed anything except for some Powershell profile colors which don't seem to conflict. CMD and Powershell display fine in the Integrated Terminal. On Tue, Feb 5, 2019 at 10:36 PM Dustin L. Howett (MSFT) < notifications@github.com> wrote: > This looks like it was either fixed by us or a problem in *winpty*, the > library VSCode uses on all versions of windows below 19H1. > @sethrr <https://github.com/sethrr> What versions of Windows and VSCode > are you using? Have you set any unusual color schemes on *the windows > console* (outside of VSCode?) > > — > You are receiving this because you were mentioned. > Reply to this email directly, view it on GitHub > <https://github.com/Microsoft/console/issues/121#issuecomment-460898633>, > or mute the thread > <https://github.com/notifications/unsubscribe-auth/ANdYeUFggYspq9n9_Y2U_PuFQy5pwe_cks5vKlvRgaJpZM4SSHvA> > . >
claunia commented 2026-01-30 21:44:31 +00:00
Author
Owner
Copy Link

@miniksa commented on GitHub (May 29, 2019):

This appears to be a dupe of #85. Closing.

@miniksa commented on GitHub (May 29, 2019): This appears to be a dupe of #85. Closing.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label Area-Output Issue-Bug Product-Conhost Resolution-Duplicate
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#169
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?