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

Possible default for dark mode #8509

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

Originally created by @MarcoBarna on GitHub (May 22, 2020).

Thanks Scott Hanselman on YT i have set this theme for all of my shells.
I think it goes really really well with default dark mode.
The setting to get this are:
On every shell settings you have add :

"useAcrylic" : true,
"acrylicOpacity" : 0.85,
"colorScheme" : "Tomorrow Night Eighties"

and here is the color scheme

{
  	"name": "Tomorrow Night Eighties",
  	"black": "#000000",
  	"red": "#f2777a",
  	"green": "#99cc99",
  	"yellow": "#ffcc66",
  	"blue": "#6699cc",
  	"purple": "#cc99cc",
  	"cyan": "#66cccc",
  	"white": "#ffffff",
  	"brightBlack": "#000000",
  	"brightRed": "#f2777a",
  	"brightGreen": "#99cc99",
  	"brightYellow": "#ffcc66",
  	"brightBlue": "#6699cc",
  	"brightPurple": "#cc99cc",
  	"brightCyan": "#66cccc",
  	"brightWhite": "#ffffff",
  	"background": "#2d2d2d",
  	"foreground": "#cccccc"
}

Here is the result
82693215-69dbe180-9c61-11ea-83aa-ca227a404540

Originally created by @MarcoBarna on GitHub (May 22, 2020). Thanks Scott Hanselman on YT i have set this theme for all of my shells. I think it goes really really well with default dark mode. The setting to get this are: On every shell settings you have add : ``` "useAcrylic" : true, "acrylicOpacity" : 0.85, "colorScheme" : "Tomorrow Night Eighties" ``` and here is the color scheme ``` { "name": "Tomorrow Night Eighties", "black": "#000000", "red": "#f2777a", "green": "#99cc99", "yellow": "#ffcc66", "blue": "#6699cc", "purple": "#cc99cc", "cyan": "#66cccc", "white": "#ffffff", "brightBlack": "#000000", "brightRed": "#f2777a", "brightGreen": "#99cc99", "brightYellow": "#ffcc66", "brightBlue": "#6699cc", "brightPurple": "#cc99cc", "brightCyan": "#66cccc", "brightWhite": "#ffffff", "background": "#2d2d2d", "foreground": "#cccccc" } ``` Here is the result ![82693215-69dbe180-9c61-11ea-83aa-ca227a404540](https://user-images.githubusercontent.com/34555572/82705833-b1ba3300-9c78-11ea-8611-1baa7e78b373.png)
claunia added the Issue-QuestionArea-SettingsResolution-AnsweredProduct-Terminal labels 2026-01-31 01:31:15 +00:00
claunia commented 2026-01-31 01:31:16 +00:00
Author
Owner
Copy Link

@j4james commented on GitHub (May 23, 2020):

The problem with this color scheme is that the dark and bright colors are identical. This will inevitably result in situations where text is difficult to see, or even completely invisible. It may be fine for your personal usage, but if we're going to include a color scheme in the app by default, there is an expectation that it's going to work reasonably well for all users. Otherwise it's just going to become another source of bug reports.

@j4james commented on GitHub (May 23, 2020): The problem with this color scheme is that the dark and bright colors are identical. This will inevitably result in situations where text is difficult to see, or even completely invisible. It may be fine for your personal usage, but if we're going to include a color scheme in the app by default, there is an expectation that it's going to work reasonably well for all users. Otherwise it's just going to become another source of bug reports.
claunia commented 2026-01-31 01:31:16 +00:00
Author
Owner
Copy Link

@MarcoBarna commented on GitHub (May 23, 2020):

The problem with this color scheme is that the dark and bright colors are identical. This will inevitably result in situations where text is difficult to see, or even completely invisible. It may be fine for your personal usage, but if we're going to include a color scheme in the app by default, there is an expectation that it's going to work reasonably well for all users. Otherwise it's just going to become another source of bug reports.

Make sense. What about a marketplace like in the settings interface? Something like vscode but for the terminal. In this way it would be fairly easily for everyone and you could also have a sync option?

@MarcoBarna commented on GitHub (May 23, 2020): > The problem with this color scheme is that the dark and bright colors are identical. This will inevitably result in situations where text is difficult to see, or even completely invisible. It may be fine for your personal usage, but if we're going to include a color scheme in the app by default, there is an expectation that it's going to work reasonably well for all users. Otherwise it's just going to become another source of bug reports. Make sense. What about a marketplace like in the settings interface? Something like vscode but for the terminal. In this way it would be fairly easily for everyone and you could also have a sync option?
claunia commented 2026-01-31 01:31:17 +00:00
Author
Owner
Copy Link

@j4james commented on GitHub (May 24, 2020):

Make sense. What about a marketplace like in the settings interface?

Yeah, I believe something like that is in the long term plans. See issue #4000 (that's mostly about plugin extensions, but I think it should cover themes and color schemes too).

@j4james commented on GitHub (May 24, 2020): > Make sense. What about a marketplace like in the settings interface? Yeah, I believe something like that is in the long term plans. See issue #4000 (that's mostly about plugin extensions, but I think it should cover themes and color schemes too).
claunia commented 2026-01-31 01:31:17 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jun 23, 2020):

Huh, the bot never tagged this with "Needs-Triage", so this got lost. Sorry about that!

@j4james is right - I think the more long-term solution here is we'll have a better story for sharing schemes, themes, and extensions, similar to how VsCode does it. That's still a while off, though we are starting to lay down some foundations in 2.0.

As far as this particular issue is concerned - I think I'm gonna close this mostly based on the fact that this scheme would suffer the same problems that have plagued us with Solarized. If people want it, they're free to add it manually.

Thanks!

@zadjii-msft commented on GitHub (Jun 23, 2020): Huh, the bot never tagged this with "Needs-Triage", so this got lost. Sorry about that! @j4james is right - I think the more long-term solution here is we'll have a better story for sharing schemes, themes, and extensions, similar to how VsCode does it. That's still a while off, though we are starting to lay down some foundations in 2.0. As far as this particular issue is concerned - I think I'm gonna close this mostly based on the fact that this scheme would suffer the same problems that have plagued us with Solarized. If people want it, they're free to add it manually. Thanks!
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-Question Product-Terminal 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#8509
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?