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

Command prompt: cursor shape won't change from Insert/Overwrite mode #16785

Closed
Hexaae opened this issue Feb 29, 2024 · 3 comments
Closed

Command prompt: cursor shape won't change from Insert/Overwrite mode #16785

Hexaae opened this issue Feb 29, 2024 · 3 comments
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

@Hexaae
Copy link

Hexaae commented Feb 29, 2024

Windows Terminal version

1.19.10573.0

Windows build number

10.0.22631.3155

Other Software

No response

Steps to reproduce

Open MS-DOS command prompt.
Change Insert/Overwrite mode from your physical keyboard.

Expected Behavior

Cursor shape should change to let you notice you're in Insert or Overwrite cursor mode.

Actual Behavior

Cursor shape stays always the same.

@Hexaae Hexaae 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 Feb 29, 2024
@j4james
Copy link
Collaborator

j4james commented Feb 29, 2024

The blocking issue for this is #7382. We need to pass on the request for the overwrite-mode cursor via conpty, which requires an equivalent escape sequence for the half-height block cursor, but there isn't a standard way to achieve that.

It's also worth noting that this particular cursor change is achieved with an internal SetCursorDBMode call, which toggles the "double cursor" mode, independent of the actual cursor size - it's not using the public SetConsoleCursorInfo API. So that's something we need to bear in mind if we want to get this working in conpty.

@carlos-zamora
Copy link
Member

Thanks for filing. We're going to mark this as a /dup of #7382

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 Mar 6, 2024
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