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

Transparency not passing through when using git #10924

New Issue
Closed
opened 2026-01-31 02:33:51 +00:00 by claunia · 2 comments
claunia commented 2026-01-31 02:33:51 +00:00
Owner
Copy Link

Originally created by @musm on GitHub (Oct 7, 2020).

I'm having a hard time localizing if this is a git or windows terminal or neovim issue. But alas, here's the problem. Perhaps git for windows is setting something that it shouldn't.

  • nvim --version:
> nvim --version
NVIM v0.5.0-709-g4f8d98e58
Build type: RelWithDebInfo
LuaJIT 2.1.0-beta3
Compilation: C:/Program Files (x86)/Microsoft Visual Studio/2017/Community/VC/Tools/MSVC/14.16.27023/bin/Hostx86/x64/cl.exe /DWIN32 /D_WINDOWS /W3 /MD /Zi /O2 /Ob1 /DNDEBUG /W3 -D_CRT_SECURE_NO_WARNINGS -D_CRT_NONSTDC_NO_DEPRECATE -DWIN32 -D_WIN32_WINNT=0x0600 -DINCLUDE_GENERATED_DECLARATIONS -DNVIM_MSGPACK_HAS_FLOAT32 -DNVIM_UNIBI_HAS_VAR_FROM -DMIN_LOG_LEVEL=3 -IC:/projects/neovim/build/config -IC:/projects/neovim/src -IC:/projects/nvim-deps/usr/include -IC:/projects/neovim/build/src/nvim/auto -IC:/projects/neovim/build/include
Compiled by appveyor@APPVYR-WIN

Features: -acl +iconv +tui
See ":help feature-compile"

   system vimrc file: "$VIM\sysinit.vim"
  fall-back for $VIM: "C:/Program Files/nvim/share/nvim"

Run :checkhealth for more info
  • Operating system/version: Windows 10, Version 20H2 (Build 19042.546)
  • Terminal name/version: Windows Terminal v1.3.2651.0

Actual behavior

** Note the black background which should be transparent ** when using normal git operations

image

Note the black background surrounded by the transparent border (which should be the actual background)

Expected behavior

Normally using nvim (no issues w.r.t background transparency)

image

Originally created by @musm on GitHub (Oct 7, 2020). <!-- Before reporting: search existing issues and check the FAQ. --> I'm having a hard time localizing if this is a git or windows terminal or neovim issue. But alas, here's the problem. Perhaps `git` for windows is setting something that it shouldn't. - `nvim --version`: ``` > nvim --version NVIM v0.5.0-709-g4f8d98e58 Build type: RelWithDebInfo LuaJIT 2.1.0-beta3 Compilation: C:/Program Files (x86)/Microsoft Visual Studio/2017/Community/VC/Tools/MSVC/14.16.27023/bin/Hostx86/x64/cl.exe /DWIN32 /D_WINDOWS /W3 /MD /Zi /O2 /Ob1 /DNDEBUG /W3 -D_CRT_SECURE_NO_WARNINGS -D_CRT_NONSTDC_NO_DEPRECATE -DWIN32 -D_WIN32_WINNT=0x0600 -DINCLUDE_GENERATED_DECLARATIONS -DNVIM_MSGPACK_HAS_FLOAT32 -DNVIM_UNIBI_HAS_VAR_FROM -DMIN_LOG_LEVEL=3 -IC:/projects/neovim/build/config -IC:/projects/neovim/src -IC:/projects/nvim-deps/usr/include -IC:/projects/neovim/build/src/nvim/auto -IC:/projects/neovim/build/include Compiled by appveyor@APPVYR-WIN Features: -acl +iconv +tui See ":help feature-compile" system vimrc file: "$VIM\sysinit.vim" fall-back for $VIM: "C:/Program Files/nvim/share/nvim" Run :checkhealth for more info ``` - Operating system/version: Windows 10, Version 20H2 (Build 19042.546) - Terminal name/version: Windows Terminal v1.3.2651.0 ### Actual behavior ** Note the black background which should be transparent ** when using normal git operations ![image](https://user-images.githubusercontent.com/4319522/95352984-c2b6ba00-0890-11eb-8f0b-2706ebf6baf2.png) Note the black background surrounded by the transparent border (which should be the actual background) ### Expected behavior Normally using `nvim` (no issues w.r.t background transparency) ![image](https://user-images.githubusercontent.com/4319522/95353161-f560b280-0890-11eb-8fbb-3bd547fda019.png)
claunia added the Resolution-By-DesignNeeds-TriageNeeds-Tag-Fix labels 2026-01-31 02:33:52 +00:00
claunia commented 2026-01-31 02:33:52 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Oct 7, 2020):

This is another instance of the color banding issue described in our troubleshooting docs. Specifically, it looks like Vim for Windows is explicitly requesting a black background.

@DHowett commented on GitHub (Oct 7, 2020): This is another instance of the [color banding issue](https://docs.microsoft.com/en-us/windows/terminal/troubleshooting#my-colors-look-strange-there-are-black-bars-on-my-screen) described in our troubleshooting docs. Specifically, it looks like Vim for Windows is explicitly requesting a black background.
claunia commented 2026-01-31 02:33:52 +00:00
Author
Owner
Copy Link

@desmap commented on GitHub (Jan 4, 2021):

@DHowett just checked the troubleshooting docs and that color banding and I'm not sure if it's really related. Whatever, I couldn't get it to work with my use case:

I am using neovim/nvim and face a similar issue. Windows Terminal seems to respect a set bgcolor and treat it as opaque instead of setting all defined backgrounds as transparant.

So is this intended by design? If yes, what would be the motivation behind that? Should we open a new issue or what are the next steps?

For others driving by, I could fix this by just turning off the set bg color and redefine on Windows Terminal level but this is just a very hacky work around no one should aim for.

Here the issue with that hack: https://github.com/neovim/neovim/issues/13065#issuecomment-753789430

@desmap commented on GitHub (Jan 4, 2021): @DHowett just checked the troubleshooting docs and that color banding and I'm not sure if it's really related. Whatever, I couldn't get it to work with my use case: I am using neovim/nvim and face a similar issue. Windows Terminal seems to respect a set bgcolor and treat it as opaque instead of setting all defined backgrounds as transparant. So is this intended by design? If yes, what would be the motivation behind that? Should we open a new issue or what are the next steps? For others driving by, I could fix this by just turning off the set bg color and redefine on Windows Terminal level but this is just a very hacky work around no one should aim for. Here the issue with that hack: https://github.com/neovim/neovim/issues/13065#issuecomment-753789430
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 Needs-Triage Resolution-By-Design
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#10924
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?