Repository navigation
Description
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:
#1203 (comment)
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?
Activity
DHowett commentedon 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.
[-]Cannot see cursor on white background[/-][+]Cannot see cursor on white background - should have an invert option[/+]bohrshaw commentedon Sep 7, 2020
I'm totally set back by this unreadability of cursor text.
zadjii-msft commentedon Oct 9, 2020
Bohr Shaw (@bohrshaw) while it's not as flexible as an inverted cursor, you could always set the
cursorColorto something other than whiteffes commentedon Oct 13, 2020
Mike Griese (@zadjii-msft) But as long as there is no
cursorTextColor(#6161) setting you will still have unreadable chars.17 remaining items
mangelozzi commentedon Sep 19, 2023
lhecker commentedon Sep 19, 2023
mangelozzi commentedon Sep 26, 2023
lhecker commentedon 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).
DHowett commentedon 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.