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

Support importing themes from other terminal apps #3118

New Issue
Open
opened 2026-01-30 23:13:27 +00:00 by claunia · 3 comments
claunia commented 2026-01-30 23:13:27 +00:00
Owner
Copy Link

Originally created by @atrauzzi on GitHub (Aug 4, 2019).

Description of the new feature/enhancement

Fluent Terminal has the really neat ability to import iterm themes which allows me to use themes from rainglow.

I would love it if the new Windows terminal was able to do the same. That way the community isn't waiting for all the various theme authors to recognize it (if ever!).

Proposed technical implementation details (optional)

I'll leave it up to you guys, but the basic idea would be to just have a look at all the applications rainglow has themes for and maybe implement hyper and iterm theme import functionality.

Originally created by @atrauzzi on GitHub (Aug 4, 2019). # Description of the new feature/enhancement Fluent Terminal has the really neat ability to import iterm themes which allows me to use themes from [rainglow](https://rainglow.io/). I would love it if the new Windows terminal was able to do the same. That way the community isn't waiting for all the various theme authors to recognize it (if ever!). # Proposed technical implementation details (optional) I'll leave it up to you guys, but the basic idea would be to just have a look at all the applications rainglow has themes for and maybe implement hyper and iterm theme import functionality.
claunia added the Issue-FeatureArea-SettingsProduct-Terminal labels 2026-01-30 23:13:27 +00:00
claunia commented 2026-01-30 23:13:28 +00:00
Author
Owner
Copy Link

@egmontkob commented on GitHub (Aug 4, 2019):

IMHO the ideal solution would be for terminal developers to agree on a format so that vendors can ship their color schemes in a single format only which would work in pretty much all emulators.

This was discussed e.g. in https://bugzilla.gnome.org/show_bug.cgi?id=655030 with no conclusion.

Indeed unfortunately it's much harder to come to an agreement among the involved parties than to implement importing foreign formats.

@egmontkob commented on GitHub (Aug 4, 2019): IMHO the ideal solution would be for terminal developers to agree on a format so that vendors can ship their color schemes in a single format only which would work in pretty much all emulators. This was discussed e.g. in https://bugzilla.gnome.org/show_bug.cgi?id=655030 with no conclusion. Indeed unfortunately it's much harder to come to an agreement among the involved parties than to implement importing foreign formats.
claunia commented 2026-01-30 23:13:28 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Aug 5, 2019):

This is a pretty good idea for once #1564 lands.

As of #1052, colortool can write out a color scheme as a json blob for the Windows Terminal to be able to consume. While it's obviously not as great as a one-click "import theme" option, it should work well enough currently for converting .itermcolors schemes into Windows Terminal compatible ones.

@zadjii-msft commented on GitHub (Aug 5, 2019): This is a pretty good idea for once #1564 lands. As of #1052, colortool can write out a color scheme as a json blob for the Windows Terminal to be able to consume. While it's obviously not as great as a one-click "import theme" option, it should work well enough currently for converting `.itermcolors` schemes into Windows Terminal compatible ones.
claunia commented 2026-01-30 23:13:29 +00:00
Author
Owner
Copy Link

@tylerszabo commented on GitHub (Nov 14, 2020):

ColorTool releases a new build with the update I wrote a short PowerShell script to perform the conversion from ColorTool .INI files. It's public domain so feel free to adapt it for other formats.

https://gist.github.com/tylerszabo/eeaea83d05889191efcf7da0853ab365

@tylerszabo commented on GitHub (Nov 14, 2020): ColorTool releases a new build with the update I wrote a short PowerShell script to perform the conversion from ColorTool `.INI` files. It's public domain so feel free to adapt it for other formats. https://gist.github.com/tylerszabo/eeaea83d05889191efcf7da0853ab365
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-Settings Issue-Feature Product-Terminal
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#3118
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?