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

Cannot see cursor on white background - should have an invert option #9919

New Issue
Open
opened 2026-01-31 02:07:24 +00:00 by claunia · 17 comments
claunia commented 2026-01-31 02:07:24 +00:00
Owner
Copy Link

Originally created by @mangelozzi on GitHub (Jul 29, 2020).

Originally assigned to: @lhecker on GitHub.

Environment

Windows build number: Microsoft Windows [Version 10.0.19041.388]
Windows Terminal version (if applicable): Version: 1.1.2021.0

Steps to reproduce

I have read this post:
https://github.com/microsoft/terminal/issues/1203#issuecomment-632888374
Apparently I am not smart enough to figure this out.

What I don't understand is how to set my cursor to just simply invert the FG and BG?
To me it is silly to set one of them to a fixed colour, and set the other to a foreground of background, cause at some point you will end up with the same colour FG and BG, and then cant read the text.

I use VIM, and I am tired of when the cursor is on white text, I have to guess where I am, type a few chars, delete them, move a little, try again.

I can't find where in the docs does cursorTextColor go (I think its not in the docs)? Under profiles? Under schemes, so I added it to both.

E.g. I have tried various combinations of cursorColor, cursorTextColor set to textForeground, textBackground, and null

Actual behavior

White text on white background

Expected behavior

It seems impossible to have the following (should be default scenario):
Case 1: White text on Black background -> Cursor is Black text on White background
Case 2: Black text on White background -> Cursor is White text on Black background

I must be missing the obvious here?

Originally created by @mangelozzi on GitHub (Jul 29, 2020). Originally assigned to: @lhecker on GitHub. # Environment ```none Windows build number: Microsoft Windows [Version 10.0.19041.388] Windows Terminal version (if applicable): Version: 1.1.2021.0 ``` # Steps to reproduce I have read this post: <https://github.com/microsoft/terminal/issues/1203#issuecomment-632888374> Apparently I am not smart enough to figure this out. What I don't understand is how to set my cursor to just simply invert the FG and BG? To me it is silly to set one of them to a fixed colour, and set the other to a foreground of background, cause at some point you will end up with the same colour FG and BG, and then cant read the text. I use VIM, and I am tired of when the cursor is on white text, I have to guess where I am, type a few chars, delete them, move a little, try again. I can't find where in the docs does `cursorTextColor` go (I think its not in the docs)? Under `profiles`? Under `schemes`, so I added it to both. E.g. I have tried various combinations of `cursorColor`, `cursorTextColor` set to `textForeground`, `textBackground`, and `null` # Actual behavior White text on white background # Expected behavior It seems impossible to have the following (should be default scenario): Case 1: White text on Black background -> Cursor is Black text on White background Case 2: Black text on White background -> Cursor is White text on Black background I must be missing the obvious here?
claunia commented 2026-01-31 02:07:25 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Jul 31, 2020):

Alas! You've unfortunately stumbled into one of our known-bad rendering issues. Sorry about that.

I just had a trip over the repo, and it seems like we did lose track of the request that the cursor simply invert. More info in the spec #6151.

I'm going to make this the master tracking issue for cursor invert.

@DHowett commented on GitHub (Jul 31, 2020): Alas! You've unfortunately stumbled into one of our known-bad rendering issues. Sorry about that. I just had a trip over the repo, and it seems like we did lose track of the request that the cursor simply invert. More info in the spec #6151. I'm going to make this the master tracking issue for cursor invert.
claunia commented 2026-01-31 02:07:25 +00:00
Author
Owner
Copy Link

@bohrshaw commented on GitHub (Sep 7, 2020):

I'm totally set back by this unreadability of cursor text.

@bohrshaw commented on GitHub (Sep 7, 2020): I'm totally set back by this unreadability of cursor text.
claunia commented 2026-01-31 02:07:26 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Oct 9, 2020):

@bohrshaw while it's not as flexible as an inverted cursor, you could always set the cursorColor to something other than white

@zadjii-msft commented on GitHub (Oct 9, 2020): @bohrshaw while it's not as flexible as an inverted cursor, you could always set the [`cursorColor`](https://docs.microsoft.com/en-us/windows/terminal/customize-settings/profile-settings#cursor-color) to something other than white
claunia commented 2026-01-31 02:07:26 +00:00
Author
Owner
Copy Link

@ffes commented on GitHub (Oct 13, 2020):

while it's not as flexible as an inverted cursor, you could always set the cursorColor to something other than white

@zadjii-msft But as long as there is no cursorTextColor (#6161) setting you will still have unreadable chars.

@ffes commented on GitHub (Oct 13, 2020): > while it's not as flexible as an inverted cursor, you could always set the `cursorColor` to something other than white @zadjii-msft But as long as there is no `cursorTextColor` (#6161) setting you will still have unreadable chars.
claunia commented 2026-01-31 02:07:26 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Oct 13, 2020):

That's correct. Like I said, it's not as flexible, but it's certainly a helpful reminder for people who like a white background for their terminal.

@zadjii-msft commented on GitHub (Oct 13, 2020): That's correct. Like I said, it's not as flexible, but it's certainly a helpful reminder for people who like a white background for their terminal.
claunia commented 2026-01-31 02:07:27 +00:00
Author
Owner
Copy Link

@mangelozzi commented on GitHub (Oct 14, 2020):

That's correct. Like I said, it's not as flexible, but it's certainly a helpful reminder for people who like a white background for their terminal.

The thing is, when there are popups, or modals, the colors are often inverted to the normal working colour. I prefer darktheme like most terminal uses. But there are times when the background becomes white beyond my control.

@mangelozzi commented on GitHub (Oct 14, 2020): > That's correct. Like I said, it's not as flexible, but it's certainly a helpful reminder for people who like a white background for their terminal. The thing is, when there are popups, or modals, the colors are often inverted to the normal working colour. I prefer darktheme like most terminal uses. But there are times when the background becomes white beyond my control.
claunia commented 2026-01-31 02:07:28 +00:00
Author
Owner
Copy Link

@nickjj commented on GitHub (Oct 19, 2020):

That's correct. Like I said, it's not as flexible, but it's certainly a helpful reminder for people who like a white background for their terminal.

In practice it's still a deal breaker for anyone using terminal Vim because every color is going to clash with how your Vim theme colors up keywords. Even with a dark theme you still run into scenarios where the cursor hides the character under it.

The only workaround I've seen so far is to use the vintage cursor but this has a lot of limitations around dynamically setting the cursor depending on which Vim mode you're in because a thick underline isn't a standard cursor but a block cursor is.

@nickjj commented on GitHub (Oct 19, 2020): > That's correct. Like I said, it's not as flexible, but it's certainly a helpful reminder for people who like a white background for their terminal. In practice it's still a deal breaker for anyone using terminal Vim because every color is going to clash with how your Vim theme colors up keywords. Even with a dark theme you still run into scenarios where the cursor hides the character under it. The only workaround I've seen so far is to use the vintage cursor but this has a lot of limitations around dynamically setting the cursor depending on which Vim mode you're in because a thick underline isn't a standard cursor but a block cursor is.
claunia commented 2026-01-31 02:07:28 +00:00
Author
Owner
Copy Link

@igniscyan commented on GitHub (Feb 1, 2023):

@DHowett Hey there, found this issue since I'm still encountering it. What is the most up to date ticket on this?

@igniscyan commented on GitHub (Feb 1, 2023): @DHowett Hey there, found this issue since I'm still encountering it. What is the most up to date ticket on this?
claunia commented 2026-01-31 02:07:29 +00:00
Author
Owner
Copy Link

@mangelozzi commented on GitHub (Feb 1, 2023):

I think not being able to see the text should be prioritised over fancy effects. Personally I have changed to linux since opening this issue. It was a hard transition having only ever used windows before, but I have never looked back was I perfected my set up.

@mangelozzi commented on GitHub (Feb 1, 2023): I think not being able to see the text should be prioritised over fancy effects. Personally I have changed to linux since opening this issue. It was a hard transition having only ever used windows before, but I have never looked back was I perfected my set up.
claunia commented 2026-01-31 02:07:29 +00:00
Author
Owner
Copy Link

@igniscyan commented on GitHub (Feb 1, 2023):

I think not being able to see the text should be prioritised over fancy effects. Personally I have changed to linux since opening this issue. It was a hard transition having only ever used windows before, but I have never looked back was I perfected my set up.

I've been considering it, but my biggest thing has been that I have lots of windows only software (including games). I may end up just having to get another drive just for Linux dual booting.

Either way, would love to see this fixed!

@igniscyan commented on GitHub (Feb 1, 2023): > I think not being able to see the text should be prioritised over fancy effects. Personally I have changed to linux since opening this issue. It was a hard transition having only ever used windows before, but I have never looked back was I perfected my set up. I've been considering it, but my biggest thing has been that I have lots of windows only software (including games). I may end up just having to get another drive just for Linux dual booting. Either way, would love to see this fixed!
claunia commented 2026-01-31 02:07:30 +00:00
Author
Owner
Copy Link

@lhecker commented on GitHub (May 25, 2023):

FYI you'll find that the new Windows Terminal Preview 1.18 will have practically fixed this issue, even if it doesn't implement inverted cursors just yet. I intend to add an invert cursor option in 1.19.
(Note however that 1.18 has a known issue with a small number of fonts. If you're affected by this, I've put a temporary workaround here: https://github.com/microsoft/terminal/issues/15199#issuecomment-1562785741.)

@lhecker commented on GitHub (May 25, 2023): FYI you'll find that the new Windows Terminal Preview 1.18 will have practically fixed this issue, even if it doesn't implement inverted cursors just yet. I intend to add an invert cursor option in 1.19. (Note however that 1.18 has a known issue with a small number of fonts. If you're affected by this, I've put a temporary workaround here: https://github.com/microsoft/terminal/issues/15199#issuecomment-1562785741.)
claunia commented 2026-01-31 02:07:30 +00:00
Author
Owner
Copy Link

@lhecker commented on GitHub (May 26, 2023):

I just realized that I once again mixed up invert and reverse. 😵‍💫 Invert is 1-color whereas reverse is swap(foreground, background) and I mix them up every single time.

Windows Terminal Preview 1.18 has an invert option: Just set the cursor color to #ffffff. The text renderer will ensure that the cursor text will always remain visible. I'll use this issue to track invert and explicit cursor text colors, but technically, at least going by the title, we can close it.

@lhecker commented on GitHub (May 26, 2023): I just realized that I once again mixed up invert and reverse. 😵‍💫 Invert is `1-color` whereas reverse is `swap(foreground, background)` and I mix them up every single time. Windows Terminal Preview 1.18 has an invert option: Just set the cursor color to `#ffffff`. The text renderer will ensure that the cursor text will always remain visible. I'll use this issue to track invert and explicit cursor text colors, but technically, at least going by the title, we can close it.
claunia commented 2026-01-31 02:07:30 +00:00
Author
Owner
Copy Link

@mangelozzi commented on GitHub (Sep 19, 2023):

3yrs later, I still can't see the cursor. I switched to Linux, but have recently returned to using Windows due to work laptop. The version in the app store in v.117 and one still can't see the cursor. Amazing.

@mangelozzi commented on GitHub (Sep 19, 2023): 3yrs later, I still can't see the cursor. I switched to Linux, but have recently returned to using Windows due to work laptop. The version in the app store in v.117 and one still can't see the cursor. Amazing.
claunia commented 2026-01-31 02:07:31 +00:00
Author
Owner
Copy Link

@lhecker commented on GitHub (Sep 19, 2023):

@mangelozzi

image

@lhecker commented on GitHub (Sep 19, 2023): @mangelozzi ![image](https://github.com/microsoft/terminal/assets/2256941/581dcd6e-8aee-4fc6-9da3-5627605cf638)
claunia commented 2026-01-31 02:07:31 +00:00
Author
Owner
Copy Link

@mangelozzi commented on GitHub (Sep 26, 2023):

@mangelozzi

image

The version in the app store in v.117 and one still can't see the cursor

@mangelozzi commented on GitHub (Sep 26, 2023): > @mangelozzi > > ![image](https://user-images.githubusercontent.com/2256941/268914485-581dcd6e-8aee-4fc6-9da3-5627605cf638.png) > The version in the **app store** in v.117 and one still can't see the cursor
claunia commented 2026-01-31 02:07:31 +00:00
Author
Owner
Copy Link

@lhecker commented on GitHub (Sep 26, 2023):

I'm not sure if you're intentionally ignoring parts of what I wrote so I'll mark your comments and my responses as off-topic, because at this point I'm starting to be a little bit annoyed by this.

Just to be entirely clear: Right now the feature is available in "Windows Terminal Preview". Not "Windows Terminal". You will find it in the "Microsoft Store" (= app store) and it will be version 1.18.

In a few days 1.18 will be available as non-Preview and you'll be able to use the new AtlasEngine with the fixed cursors there if you manually opt into it (it's off by default in non-Preview and enabled by default in Preview).

@lhecker commented on GitHub (Sep 26, 2023): I'm not sure if you're intentionally ignoring parts of what I wrote so I'll mark your comments and my responses as off-topic, because at this point I'm starting to be a little bit annoyed by this. Just to be entirely clear: Right now the feature is available in "Windows Terminal **_Preview_**". Not "Windows Terminal". You _will_ find it in the "Microsoft Store" (= app store) and it _will_ be version 1.18. In a few days 1.18 will be available as non-Preview and you'll be able to use the new AtlasEngine with the fixed cursors there if you manually opt into it (it's off by default in non-Preview and enabled by default in Preview).
claunia commented 2026-01-31 02:07:32 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Aug 22, 2024):

Since we now have cursor inversion and a forced contrast distance for solid cursor colors, I'm going to change the priority on this bug to 2 and move it to the 1.23 milestone.

@DHowett commented on GitHub (Aug 22, 2024): Since we now have cursor inversion and a forced contrast distance for solid cursor colors, I'm going to change the priority on this bug to 2 and move it to the 1.23 milestone.
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-Accessibility Area-Rendering Issue-Task Priority-2 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#9919
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?