starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-03 21:25:34 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

[FEATURE] Make the retro terminal mode more configurable #20385

New Issue
Closed
opened 2026-01-31 07:12:11 +00:00 by claunia · 2 comments
claunia commented 2026-01-31 07:12:11 +00:00
Owner
Copy Link

Originally created by @skunkmommy on GitHub (Aug 20, 2023).

Description of the new feature/enhancement

Retro terminal mode looks cool, but it also makes text really hard to see on my secondary (which is a crappy old Dell) and doesn't do much of anything on my primary (a 1080p tv, idk size in inches)
I'd like if it were more configurable, so that I could tweak it to be more/less effective.

Proposed technical implementation details (optional)

Allow the following to be changed:

  • Width of scanlines
  • Size of the gap between two scanlines
  • How dark that gap is
  • How much glow is added to text; 0% is none, 100% is current, and 200% is 2x the current amount.

These settings should be applied on a per-monitor basis, since different monitors will need different amounts of tweaking.

Originally created by @skunkmommy on GitHub (Aug 20, 2023). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 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! --> # Description of the new feature/enhancement Retro terminal mode looks cool, but it also makes text really hard to see on my secondary (which is a crappy old Dell) and doesn't do much of anything on my primary (a 1080p tv, idk size in inches) I'd like if it were more configurable, so that I could tweak it to be more/less effective. <!-- A clear and concise description of what the problem is that the new feature would solve. Describe why and how a user would use this new functionality (if applicable). --> # Proposed technical implementation details (optional) Allow the following to be changed: - Width of scanlines - Size of the gap between two scanlines - How dark that gap is - How much glow is added to text; 0% is none, 100% is current, and 200% is 2x the current amount. These settings should be applied on a per-monitor basis, since different monitors will need different amounts of tweaking. <!-- A clear and concise description of what you want to happen. -->
claunia commented 2026-01-31 07:12:14 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Aug 21, 2023):

Good news! The retro shader is just a specific example of custom pixel shaders for the Terminal. You can feel free to grab the source from Retro.hlsl, and modify it however you'd like!

@zadjii-msft commented on GitHub (Aug 21, 2023): Good news! The retro shader is just a specific example of [custom pixel shaders](https://learn.microsoft.com/en-us/windows/terminal/customize-settings/profile-appearance#pixel-shader-effects) for the Terminal. You can feel free to grab the source from [Retro.hlsl](https://github.com/microsoft/terminal/blob/main/samples/PixelShaders/Retro.hlsl), and modify it however you'd like!
claunia commented 2026-01-31 07:12:14 +00:00
Author
Owner
Copy Link

@AdreKiseque commented on GitHub (Dec 30, 2024):

While it is cool we can customize this ourselves, I still think a more user-friendly way to adjust the retro terminal parameters would be good. Personally, I love the retro terminal in concept but find it a little hard on the eyes... but it's not something I use enough to justify the trouble of poking at these advanced configurations.

@AdreKiseque commented on GitHub (Dec 30, 2024): While it is cool we can customize this ourselves, I still think a more user-friendly way to adjust the retro terminal parameters would be good. Personally, I love the retro terminal in concept but find it a little hard on the eyes... but it's not something I use enough to justify the trouble of poking at these advanced configurations.
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 Needs-Triage 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#20385
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?