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

Color Schemes............. #15429

New Issue
Closed
opened 2026-01-31 04:38:24 +00:00 by claunia · 4 comments
claunia commented 2026-01-31 04:38:24 +00:00
Owner
Copy Link

Originally created by @pb5050 on GitHub (Oct 3, 2021).

i imported a massive amount of color schemes from colortool and or other palces and the settings file becomes massively long.

is there a way we could make "color schemes" a separate file?

im not to familiar with coding is there a way i could create a json file with array for color schemes and somehow reference it in the settings file so its not so cluttered"?

Originally created by @pb5050 on GitHub (Oct 3, 2021). i imported a massive amount of color schemes from colortool and or other palces and the settings file becomes massively long. is there a way we could make "color schemes" a separate file? im not to familiar with coding is there a way i could create a json file with array for color schemes and somehow reference it in the settings file so its not so cluttered"?
claunia commented 2026-01-31 04:38:25 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Oct 4, 2021):

A clever way to work around this would be to pretend that they're a "fragment extension". The docs are much more elaborate here. But you could do something like:

  1. Make a folder in %localappdata%\Microsoft\Windows Terminal\Fragments. For this example, we'll use TestFragment as our directory name.
  2. in that TestFragment, make a new .json file. It can be named anything (as long as it's extension is .json). We'll call it schemes.json.
  3. In schemes.json, add all your schemes. For example:
{
"schemes": [
  {
    "name": "Banana Blueberry",
    "black": "#17141f",
    "red": "#ff6b7f",
    "green": "#00bd9c",
    "yellow": "#e6c62f",
    "blue": "#22e8df",
    "purple": "#dc396a",
    "cyan": "#56b6c2",
    "white": "#f1f1f1",
    "brightBlack": "#495162",
    "brightRed": "#fe9ea1",
    "brightGreen": "#98c379",
    "brightYellow": "#f9e46b",
    "brightBlue": "#91fff4",
    "brightPurple": "#da70d6",
    "brightCyan": "#bcf3ff",
    "brightWhite": "#ffffff",
    "background": "#191323",
    "foreground": "#cccccc",
    "cursorColor": "#e07d13",
    "selectionBackground": "#220525"
  }

]
}

Restart the Terminal, and you'll see that all the schemes from that file are available in the Terminal, without needing to be in the settings.json file itself.

@zadjii-msft commented on GitHub (Oct 4, 2021): A clever way to work around this would be to pretend that they're a "fragment extension". The docs are much more elaborate [here](https://docs.microsoft.com/en-us/windows/terminal/json-fragment-extensions). But you could do something like: 1. Make a folder in `%localappdata%\Microsoft\Windows Terminal\Fragments`. For this example, we'll use `TestFragment` as our directory name. 2. in that `TestFragment`, make a new `.json` file. It can be named anything (as long as it's extension is `.json`). We'll call it `schemes.json`. 3. In `schemes.json`, add all your schemes. For example: ```json { "schemes": [ { "name": "Banana Blueberry", "black": "#17141f", "red": "#ff6b7f", "green": "#00bd9c", "yellow": "#e6c62f", "blue": "#22e8df", "purple": "#dc396a", "cyan": "#56b6c2", "white": "#f1f1f1", "brightBlack": "#495162", "brightRed": "#fe9ea1", "brightGreen": "#98c379", "brightYellow": "#f9e46b", "brightBlue": "#91fff4", "brightPurple": "#da70d6", "brightCyan": "#bcf3ff", "brightWhite": "#ffffff", "background": "#191323", "foreground": "#cccccc", "cursorColor": "#e07d13", "selectionBackground": "#220525" } ] } ``` Restart the Terminal, and you'll see that all the schemes from that file are available in the Terminal, without needing to be in the `settings.json` file itself.
claunia commented 2026-01-31 04:38:26 +00:00
Author
Owner
Copy Link

@pb5050 commented on GitHub (Nov 9, 2021):

i was trying to do this again but i have No "Fragments" directory

the only thing i could find was
C:\Users\Janss\AppData\Local\Packages\Microsoft.WindowsTerminalPreview_8wekyb3d8bbwe\LocalState
that had all my settings backup json files and the main settings . json file......

hmm i have it installed from the app store. but i did a search for folders names "Fragments" and found nothing.

@pb5050 commented on GitHub (Nov 9, 2021): i was trying to do this again but i have No "Fragments" directory the only thing i could find was C:\Users\Janss\AppData\Local\Packages\Microsoft.WindowsTerminalPreview_8wekyb3d8bbwe\LocalState that had all my settings backup json files and the main settings . json file...... hmm i have it installed from the app store. but i did a search for folders names "Fragments" and found nothing.
claunia commented 2026-01-31 04:38:26 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Nov 9, 2021):

i was trying to do this again but i have No "Fragments" directory

That makes sense, we don't make one by default. Hence why I asked in the first step to create the Fragments/ directory 😄

@zadjii-msft commented on GitHub (Nov 9, 2021): > i was trying to do this again but i have No "Fragments" directory That makes sense, we don't make one by default. Hence why I asked [in the first step](https://github.com/microsoft/terminal/issues/11406#issuecomment-933479870) to _create the `Fragments/` directory_ 😄
claunia commented 2026-01-31 04:38:26 +00:00
Author
Owner
Copy Link

@pb5050 commented on GitHub (Dec 19, 2021):

love you. what elese will this work with>!?!?!

@pb5050 commented on GitHub (Dec 19, 2021): love you. what elese will this work with>!?!?!
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 Issue-Question Needs-Tag-Fix Needs-Triage Resolution-Answered
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#15429
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?