Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Console.CursorSize method does not work in terminal but works in conhost. #16027

Closed
stevewpalmer opened this issue Sep 25, 2023 · 3 comments
Closed
Labels
Issue-Bug It either shouldn't be doing this or needs an investigation. Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@stevewpalmer
Copy link

Windows Terminal version

1.17.11461.0

Windows build number

10.0.22621.2283

Other Software

No response

Steps to reproduce

  1. Compile the sample code at https://learn.microsoft.com/en-us/dotnet/api/system.console.cursorsize?view=net-7.0.

  2. Run under Terminal. Note that the cursor size remains what was set in the profile.

  3. Run under conhost.exe (the old cmd.exe). Note that the cursor size changes in response to changes to the CursorSize property.

Expected Behavior

I expected the cursor size to change in response to changes to the property as the documentation for CursorSize says nothing about the functionality being deprecated or impaired under Terminal.

Actual Behavior

The cursor size setting in the terminal profile remains constant and overrides any change to the CursorSize property.

@stevewpalmer stevewpalmer added Issue-Bug It either shouldn't be doing this or needs an investigation. Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting labels Sep 25, 2023
@lhecker
Copy link
Member

lhecker commented Sep 25, 2023

I believe this issue is a duplicate of #7382.
tl;dr: We need to define a custom escape sequence first that communicates from ConPTY (the console API -> VT translator) to Windows Terminal that the cursor size has changed.

@zadjii-msft
Copy link
Member

Yep, sure is /dup #7382

@zadjii-msft zadjii-msft closed this as not planned Won't fix, can't repro, duplicate, stale Sep 25, 2023
@microsoft-github-policy-service
Copy link
Contributor

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@microsoft-github-policy-service microsoft-github-policy-service bot added Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing. and removed Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting labels Sep 25, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue-Bug It either shouldn't be doing this or needs an investigation. Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.
Projects
None yet
Development

No branches or pull requests

3 participants