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

Black background in Windows Terminal when using Cmd'er #13288

New Issue
Closed
opened 2026-01-31 03:38:51 +00:00 by claunia · 6 comments
claunia commented 2026-01-31 03:38:51 +00:00
Owner
Copy Link

Originally created by @Hejle on GitHub (Apr 2, 2021).

Originally assigned to: @DHowett on GitHub.

When using Cmd'er inside windows terminal I get black bars under ther default text, which looks annoying.
I have been using Windows Terminal with Cmd'er since November 2020, and this is the first time I have had the issue.
The two lines at the bottom is how the black bar looks when I open the terminal - while resizing the terminal makes the whole line black. The issue is not present in any other terminal.

billede

I have followed this Medium-Blogpost to setup Cmd'er and Windows Terminal so it should be fairly simply to follow.

Lastly I run this on a Surface Pro running windows 10 pro version 19041.867

Originally created by @Hejle on GitHub (Apr 2, 2021). Originally assigned to: @DHowett on GitHub. When using Cmd'er inside windows terminal I get black bars under ther default text, which looks annoying. I have been using Windows Terminal with Cmd'er since November 2020, and this is the first time I have had the issue. The two lines at the bottom is how the black bar looks when I open the terminal - while resizing the terminal makes the whole line black. The issue is not present in any other terminal. ![billede](https://user-images.githubusercontent.com/18572997/113423727-4203f100-93cf-11eb-8491-436860bbbaee.png) I have followed this [Medium-Blogpost](https://medium.com/talpor/windows-terminal-cmder-%EF%B8%8F-573e6890d143) to setup Cmd'er and Windows Terminal so it should be fairly simply to follow. Lastly I run this on a Surface Pro running windows 10 pro version 19041.867
claunia added the Resolution-ExternalNeeds-Tag-Fix labels 2026-01-31 03:38:51 +00:00
claunia commented 2026-01-31 03:38:52 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Apr 2, 2021):

Right, so, this happens when an application explicitly requests the black background color. On Consoles that existed before Windows Terminal, this would automatically resolve to "the DEFAULT background color". Unfortunately, since we have acrylic or an image or some other background color, we had to make it possible for applications to differentiate "background" from "black". Applications are generally well-behaved, and this works perfectly fine with well-behaved applications.

Do you happen to know the prompt settings for the default cmder/clink setup?

@DHowett commented on GitHub (Apr 2, 2021): Right, so, this happens when an application _explicitly requests_ the black background color. On Consoles that existed before Windows Terminal, this would automatically resolve to "the DEFAULT background color". Unfortunately, since we have acrylic or an image or some other background color, we had to make it possible for applications to differentiate "background" from "black". Applications are generally well-behaved, and this works perfectly fine with well-behaved applications. Do you happen to know the prompt settings for the default cmder/clink setup?
claunia commented 2026-01-31 03:38:53 +00:00
Author
Owner
Copy Link

@Hejle commented on GitHub (Apr 2, 2021):

Sorry, I don't know the promt-settings for the default cmder setup since I'm not completely sure where to find the prompt setting.. :)

It is possible that it is a cmder issue more than a windows terminal issue - just wanted to let it be known since I have Cmd'er/WT combo on my workpc without the black box. (Though not near the workpc due to easter).

@Hejle commented on GitHub (Apr 2, 2021): Sorry, I don't know the promt-settings for the default cmder setup since I'm not completely sure where to find the prompt setting.. :) It is possible that it is a cmder issue more than a windows terminal issue - just wanted to let it be known since I have Cmd'er/WT combo on my workpc without the black box. (Though not near the workpc due to easter).
claunia commented 2026-01-31 03:38:53 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Apr 2, 2021):

ALRIGHT, Found it!

c34eb73555/vendor/clink.lua (L50)

This is in the source for cmder. It comes with a "prompt hook" that prints some raw control sequences. Many of them are used to set the color (\x1b[...m).

The one that is using 40 (\x1b[1;32;40m) is requesting the black boxes, explicitly. 40 is the graphical representation code for "background in ANSI color 0 (which is typically black)".

Might have to mark this one external 😄

I will file the bug on cmder, as I have the most context here. We had to file a similar bug on PowerShell, after all!

@DHowett commented on GitHub (Apr 2, 2021): ALRIGHT, Found it! https://github.com/cmderdev/cmder/blob/c34eb735556d5f2ccf59b042d17d5f2880414356/vendor/clink.lua#L50 This is in the source for cmder. It comes with a "prompt hook" that prints some raw control sequences. Many of them are used to set the color (`\x1b[...m`). The one that is using `40` (`\x1b[1;32;40m`) is requesting the black boxes, explicitly. `40` is the graphical representation code for "background in ANSI color 0 (which is typically black)". Might have to mark this one external :smile: *I* will file the bug on cmder, as I have the most context here. We had to file a similar bug on PowerShell, after all!
claunia commented 2026-01-31 03:38:53 +00:00
Author
Owner
Copy Link

@Hejle commented on GitHub (Apr 2, 2021):

Thank you for the amazing explanation (Way more than I expected when I posted)! Have a good day!

@Hejle commented on GitHub (Apr 2, 2021): Thank you for the amazing explanation (Way more than I expected when I posted)! Have a good day!
claunia commented 2026-01-31 03:38:54 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Apr 2, 2021):

I've moved this upstream to /dup https://github.com/cmderdev/cmder/issues/2516

Thanks for the report!

@DHowett commented on GitHub (Apr 2, 2021): I've moved this upstream to /dup https://github.com/cmderdev/cmder/issues/2516 Thanks for the report!
claunia commented 2026-01-31 03:38:54 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Apr 2, 2021):

Hi! We've identified this issue as a duplicate of one that exists on somebody else's Issue Tracker. Please make sure you subscribe to the referenced external issue for future updates. Thanks for your report!

@ghost commented on GitHub (Apr 2, 2021): Hi! We've identified this issue as a duplicate of one that exists on somebody else's Issue Tracker. Please make sure you subscribe to the referenced external issue for future updates. Thanks for your report!
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 Needs-Tag-Fix Resolution-External
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#13288
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?