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

Windows Terminal turns completely opaque when I load Vim #10997

New Issue
Closed
opened 2026-01-31 02:35:48 +00:00 by claunia · 14 comments
claunia commented 2026-01-31 02:35:48 +00:00
Owner
Copy Link

Originally created by @Chaoticsys101 on GitHub (Oct 13, 2020).

Environment

Windows build number: Microsoft Windows [Version 10.0.18363.720]
Windows Terminal version (if applicable): Windows Terminal 1.3.2651.0

Any other software?  Vim 8.2

Steps to reproduce

First open Window Terminal, turn acrylic on.
It works fine. Execute vim.exe. Windows Terminal turns opaque.
Exit vim.exe. Windows Terminal goes back to normal.

Expected behavior

Acrylic transparency should stay the same.
This behaviour does not occur with cmd.exe (transparency stays the same).

Capturar
Capturar2

Originally created by @Chaoticsys101 on GitHub (Oct 13, 2020). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING: 1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement. 2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement. 3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number). 4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement. 5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement. All good? Then proceed! --> <!-- This bug tracker is monitored by Windows Terminal development team and other technical folks. **Important: When reporting BSODs or security issues, DO NOT attach memory dumps, logs, or traces to Github issues**. Instead, send dumps/traces to secure@microsoft.com, referencing this GitHub issue. If this is an application crash, please also provide a Feedback Hub submission link so we can find your diagnostic data on the backend. Use the category "Apps > Windows Terminal (Preview)" and choose "Share My Feedback" after submission to get the link. Please use this form and describe your issue, concisely but precisely, with as much detail as possible. --> # Environment ```none Windows build number: Microsoft Windows [Version 10.0.18363.720] Windows Terminal version (if applicable): Windows Terminal 1.3.2651.0 Any other software? Vim 8.2 ``` # Steps to reproduce First open Window Terminal, turn acrylic on. It works fine. Execute vim.exe. Windows Terminal turns opaque. Exit vim.exe. Windows Terminal goes back to normal. <!-- A description of how to trigger this bug. --> # Expected behavior Acrylic transparency should stay the same. This behaviour does not occur with cmd.exe (transparency stays the same). <!-- A description of what you're expecting, possibly containing screenshots or reference material. --> ![Capturar](https://user-images.githubusercontent.com/67800528/95847895-35b6a980-0d45-11eb-8b22-0501d1e0ab38.PNG) ![Capturar2](https://user-images.githubusercontent.com/67800528/95847900-37806d00-0d45-11eb-9056-6a6976148b03.PNG)
claunia commented 2026-01-31 02:35:49 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Oct 15, 2020):

@Chaoticsys101

I am not having any issues with vim but can you share your vimrc to let me try to repro this issue

@ghost commented on GitHub (Oct 15, 2020): @Chaoticsys101 I am not having any issues with vim but can you share your vimrc to let me try to repro this issue
claunia commented 2026-01-31 02:35:49 +00:00
Author
Owner
Copy Link

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

This is intentional behavior. Vim is requesting that the background color be set, so Windows Terminal must set the background color. More info here.

@DHowett commented on GitHub (Oct 15, 2020): This is intentional behavior. Vim is requesting that the background color be set, so Windows Terminal _must_ set the background color. More info [here](https://docs.microsoft.com/en-us/windows/terminal/troubleshooting#my-colors-look-strange-there-are-black-bars-on-my-screen).
claunia commented 2026-01-31 02:35:50 +00:00
Author
Owner
Copy Link

@Chaoticsys101 commented on GitHub (Oct 15, 2020):

Could you please be a bit more specific? I put "background" : "#000000" in
defaults in the config file but it stayed the same.

Dustin L. Howett notifications@github.com escreveu no dia quinta,
15/10/2020 à(s) 18:57:

@Chaoticsys101 commented on GitHub (Oct 15, 2020): Could you please be a bit more specific? I put "background" : "#000000" in defaults in the config file but it stayed the same. Dustin L. Howett <notifications@github.com> escreveu no dia quinta, 15/10/2020 à(s) 18:57:
claunia commented 2026-01-31 02:35:50 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Oct 16, 2020):

@Chaoticsys101

Vim is setting the console color to be that color, that's what @DHowett meant. Even though I am not having any troubles with vim.

Must have something to do with your vimrc or you can just create an issue in vim

@ghost commented on GitHub (Oct 16, 2020): @Chaoticsys101 Vim is setting the console color to be that color, that's what @DHowett meant. Even though I am not having any troubles with vim. Must have something to do with your vimrc or you can just create an issue in [vim](https://github.com/vim/vim)
claunia commented 2026-01-31 02:35:50 +00:00
Author
Owner
Copy Link

@Chaoticsys101 commented on GitHub (Oct 16, 2020):

Thanks. If I do 'vim -u NONE -U NONE' it works fine. So the problem is in my vimrc. Do you have a public email or some place where we could talk? I would like to share my vimrc to see if we could figure out what is wrong

@Chaoticsys101 commented on GitHub (Oct 16, 2020): Thanks. If I do 'vim -u NONE -U NONE' it works fine. So the problem is in my vimrc. Do you have a public email or some place where we could talk? I would like to share my vimrc to see if we could figure out what is wrong
claunia commented 2026-01-31 02:35:51 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Oct 16, 2020):

@Chaoticsys101 This may help -> https://vi.stackexchange.com/questions/18212/prevent-colorscheme-from-changing-background-color

@ghost commented on GitHub (Oct 16, 2020): @Chaoticsys101 This may help -> https://vi.stackexchange.com/questions/18212/prevent-colorscheme-from-changing-background-color
claunia commented 2026-01-31 02:35:51 +00:00
Author
Owner
Copy Link

@Chaoticsys101 commented on GitHub (Oct 16, 2020):

Unfortunately it did not... BTW how did you set your vimrc to 256 color?

@Chaoticsys101 commented on GitHub (Oct 16, 2020): Unfortunately it did not... BTW how did you set your vimrc to 256 color?
claunia commented 2026-01-31 02:35:51 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Oct 16, 2020):

@Chaoticsys101 Ok. I got a random vimrc that I got from the internet (I installed vim in WSL Ubuntu)

@ghost commented on GitHub (Oct 16, 2020): @Chaoticsys101 Ok. I got a random vimrc that I got from the internet (I installed vim in WSL Ubuntu)
claunia commented 2026-01-31 02:35:51 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Oct 16, 2020):

@Chaoticsys101 try using a different vimrc and add settings back individually and see which is causing the trouble.

@ghost commented on GitHub (Oct 16, 2020): @Chaoticsys101 try using a different vimrc and add settings back individually and see which is causing the trouble.
claunia commented 2026-01-31 02:35:51 +00:00
Author
Owner
Copy Link

@Chaoticsys101 commented on GitHub (Oct 16, 2020):

I will send my vimrc in a few hours, I'll share a link or something

@Chaoticsys101 commented on GitHub (Oct 16, 2020): I will send my vimrc in a few hours, I'll share a link or something
claunia commented 2026-01-31 02:35:52 +00:00
Author
Owner
Copy Link

@Chaoticsys101 commented on GitHub (Oct 16, 2020):

I tried but it either worked with the default colorscheme or didn't

@Chaoticsys101 commented on GitHub (Oct 16, 2020): I tried but it either worked with the default colorscheme or didn't
claunia commented 2026-01-31 02:35:52 +00:00
Author
Owner
Copy Link

@Hammster commented on GitHub (Mar 29, 2021):

👋 For anyone who wants to change this behaviour I created a shader to solve this issue.

You have to adjust the color inside the shader as explained in the settings section. but after that you can run xterm colors + transparency. For now, it can only turn 1 color into transparency though that should be enough for 99% of the use cases, cheers.

https://github.com/Hammster/windows-terminal-shaders#Transparent

@Hammster commented on GitHub (Mar 29, 2021): 👋 For anyone who wants to change this behaviour I created a shader to solve this issue. You have to adjust the color inside the shader as explained in the settings section. but after that you can run xterm colors + transparency. For now, it can only turn 1 color into transparency though that should be enough for 99% of the use cases, cheers. https://github.com/Hammster/windows-terminal-shaders#Transparent
claunia commented 2026-01-31 02:35:52 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Mar 29, 2021):

While it’s cool that we can do that with shaders, it seems like the wrong speed to delete an entire color when someone could just reconfigure vim :)

@DHowett commented on GitHub (Mar 29, 2021): While it’s cool that we can do that with shaders, it seems like the wrong speed to delete an entire color when someone could just reconfigure vim :)
claunia commented 2026-01-31 02:35:52 +00:00
Author
Owner
Copy Link

@Hammster commented on GitHub (Mar 29, 2021):

If the configurations solve the issue sure, and deleting the color is more or less a workaround, but it get's the job done. Especially when using xterm based color themes especially when hi Normal ctermbg=NONE guibg=NONE isn't working at all and your only other option is to disable xterm colors :)

No critic on your statement, the shader is definitely the hammer method 👍

@Hammster commented on GitHub (Mar 29, 2021): If the configurations solve the issue sure, and deleting the color is more or less a workaround, but it get's the job done. Especially when using xterm based color themes especially when `hi Normal ctermbg=NONE guibg=NONE ` isn't working at all and your only other option is to disable xterm colors :) No critic on your statement, the shader is definitely the hammer method 👍
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 Issue-Question Needs-Tag-Fix Resolution-Answered 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#10997
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?