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

Define vim color scheme related to the windows terminal theme #10496

New Issue
Closed
opened 2026-01-31 02:23:09 +00:00 by claunia · 4 comments
claunia commented 2026-01-31 02:23:09 +00:00
Owner
Copy Link

Originally created by @pumpingiron on GitHub (Sep 4, 2020).

Hello,

I'd like to be able to apply the good vim's color scheme in accordance with the windows terminal theme defined.
In putty or Iterm, I use a variable defined when loading the profile whether it is a dark or bright theme that I can reuse later according to what I wanna do.

So, Is there an already integrated solution or has anyone ever tried to do that ?

Thanks in advance.

Originally created by @pumpingiron on GitHub (Sep 4, 2020). Hello, I'd like to be able to apply the good vim's color scheme in accordance with the windows terminal theme defined. In putty or Iterm, I use a variable defined when loading the profile whether it is a dark or bright theme that I can reuse later according to what I wanna do. So, Is there an already integrated solution or has anyone ever tried to do that ? Thanks in advance.
claunia added the Needs-TriageNeeds-Tag-FixNeeds-Attention labels 2026-01-31 02:23:09 +00:00
claunia commented 2026-01-31 02:23:10 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Sep 9, 2020):

What variable is that? If there is prior art for exposing the terminal's color scheme to connected applications, we could consider following it.

@DHowett commented on GitHub (Sep 9, 2020): What variable is that? If there is prior art for exposing the terminal's color scheme to connected applications, we could consider following it.
claunia commented 2026-01-31 02:23:10 +00:00
Author
Owner
Copy Link

@pumpingiron commented on GitHub (Sep 10, 2020):

I don't understand.

I just wanna apply the correct color scheme in my vim editor related to my terminal color scheme.

For example, If I launch my terminal in a bright mode, i wanna get my vim editor in a bright mode too, so how can i get the terminal color scheme information in order to be able to detect it in my vimrc file and apply it when it's needed, and the same in reverse for a dark display ?

@pumpingiron commented on GitHub (Sep 10, 2020): I don't understand. I just wanna apply the correct color scheme in my vim editor related to my terminal color scheme. For example, If I launch my terminal in a bright mode, i wanna get my vim editor in a bright mode too, so how can i get the terminal color scheme information in order to be able to detect it in my vimrc file and apply it when it's needed, and the same in reverse for a dark display ?
claunia commented 2026-01-31 02:23:10 +00:00
Author
Owner
Copy Link

@skyline75489 commented on GitHub (Sep 16, 2020):

#3718 could be a solution. Unfortunately WT has not yet support it.

@skyline75489 commented on GitHub (Sep 16, 2020): #3718 could be a solution. Unfortunately WT has not yet support it.
claunia commented 2026-01-31 02:23:10 +00:00
Author
Owner
Copy Link

@pumpingiron commented on GitHub (Sep 16, 2020):

Sorry, I had forgotten this issue.

I've found the solution in the meantime, you juste have to get WT_PROFILE_ID variable's content which corresponds to your loaded profile's id with colorization etc ...
Then from there, if your .bashrc configuration is well designed, you can autodetect all other colorization's parameters like in vim for example.

I'm gonna close the issue.

@pumpingiron commented on GitHub (Sep 16, 2020): Sorry, I had forgotten this issue. I've found the solution in the meantime, you juste have to get WT_PROFILE_ID variable's content which corresponds to your loaded profile's id with colorization etc ... Then from there, if your .bashrc configuration is well designed, you can autodetect all other colorization's parameters like in vim for example. I'm gonna close the issue.
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-Attention Needs-Tag-Fix Needs-Triage
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#10496
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?