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

[megathread] Cursor shapes in WT UI / conhost UI / VT #20276

New Issue
Open
opened 2026-01-31 07:08:47 +00:00 by claunia · 3 comments
claunia commented 2026-01-31 07:08:47 +00:00
Owner
Copy Link

Originally created by @alabuzhev on GitHub (Jul 22, 2023).

Description of the new feature/enhancement

There are so many of them, and all the sets are slightly different:

WT:
image

Conhost:
image

VT:
image

There are quite a few inconsistencies:

  1. Terminology:
    • vintage / legacy
    • underscore / underline
    • bar / vertical bar
    • solid box / filled box / block
  2. UI order.
  3. Feature set: conhost does not have "double underscore"
  4. VT access: "vintage", "double underscore" and "empty box" are not exposed and cannot be set programmatically.
  5. UI access: non-blinking versions are not exposed.
  6. API behavior:
    • SetConsoleCursorInfo resets cursor to "legacy" in conhost if the size is different from the initial one, but not in WT (I understand why, but still).

I'm not saying that all those are bugs that should be fixed, but perhaps the situation could be improved.

maintainer tracking space

### Tasks
- [ ] #7827
- [ ] #7382 
- [ ] #1379
Originally created by @alabuzhev on GitHub (Jul 22, 2023). # Description of the new feature/enhancement There are so many of them, and all the sets are slightly different: WT: ![image](https://github.com/microsoft/terminal/assets/11453922/99e55654-de4f-4fbf-a225-f033a4c6d034) Conhost: ![image](https://github.com/microsoft/terminal/assets/11453922/eea4731e-8b9e-4e9d-88ac-773e1c383dce) [VT](https://learn.microsoft.com/en-us/windows/console/console-virtual-terminal-sequences#cursor-shape): ![image](https://github.com/microsoft/terminal/assets/11453922/978fb0e3-e55b-4ab8-9878-85365a88701d) --------- There are quite a few inconsistencies: 1. Terminology: - vintage / legacy - underscore / underline - bar / vertical bar - solid box / filled box / block 2. UI order. 3. Feature set: conhost does not have "double underscore" 4. VT access: "vintage", "double underscore" and "empty box" are not exposed and cannot be set programmatically. 5. UI access: non-blinking versions are not exposed. 6. API behavior: - [SetConsoleCursorInfo](https://learn.microsoft.com/en-us/windows/console/setconsolecursorinfo) resets cursor to "legacy" in conhost if the size is different from the initial one, but not in WT (I understand why, but still). I'm not saying that all those are bugs that should be fixed, but perhaps the situation could be improved. ---- _maintainer tracking space_ ```[tasklist] ### Tasks - [ ] #7827 - [ ] #7382 - [ ] #1379 ```
claunia added the Needs-Tag-FixProduct-MetaIssue-Scenario labels 2026-01-31 07:08:48 +00:00
claunia commented 2026-01-31 07:08:48 +00:00
Author
Owner
Copy Link

@j4james commented on GitHub (Jul 22, 2023):

The "double underscore" cursor was a user contributed feature (PR #7827), and I don't think something like that is generally expected to be ported to conhost as well. Although it doesn't seem like it would require much more work - the GDI support was already done as far as I can see.

Extending the DECSCUSR sequence to support non-standard cursor styles is tracked in #7382.

Adding a UI setting to control the cursor blinking in WT is tracked in #1379.

Getting SetConsoleCursorInfo to work on WT the same as it does in conhost is also essentially covered by #7382 I think.

@j4james commented on GitHub (Jul 22, 2023): The "double underscore" cursor was a user contributed feature (PR #7827), and I don't think something like that is generally expected to be ported to conhost as well. Although it doesn't seem like it would require much more work - the GDI support was already done as far as I can see. Extending the `DECSCUSR` sequence to support non-standard cursor styles is tracked in #7382. Adding a UI setting to control the cursor blinking in WT is tracked in #1379. Getting `SetConsoleCursorInfo` to work on WT the same as it does in conhost is also essentially covered by #7382 I think.
claunia commented 2026-01-31 07:08:49 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jul 24, 2023):

That does seem like a pretty comprehensive answer. Anything missed/?

@zadjii-msft commented on GitHub (Jul 24, 2023): That does seem like a pretty comprehensive answer. Anything missed/?
claunia commented 2026-01-31 07:08:49 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jul 24, 2023):

(we're gonna leave this open because it's a pretty good megathread for tracking purposes. Thanks!)

@zadjii-msft commented on GitHub (Jul 24, 2023): (we're gonna leave this open because it's a pretty good megathread for tracking purposes. 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 Issue-Scenario Needs-Tag-Fix Product-Meta
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#20276
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?