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

-ViModeIndicator "Cursor" option not applying correctly on Windows Terminal #3334

Closed
3 tasks done
nlguerra2003 opened this issue Jun 2, 2022 · 1 comment · Fixed by #3374
Closed
3 tasks done

-ViModeIndicator "Cursor" option not applying correctly on Windows Terminal #3334

nlguerra2003 opened this issue Jun 2, 2022 · 1 comment · Fixed by #3374

Comments

@nlguerra2003
Copy link

nlguerra2003 commented Jun 2, 2022

Prerequisites

  • Write a descriptive title.
  • Make sure you are able to repro it on the latest released version
  • Search the existing issues, especially the pinned issues.

Exception report

N/A

Screenshot

N/A

Environment data

PS Version: 7.2.4
PS HostName: ConsoleHost (Windows Terminal)
PSReadLine Version: 2.2.5
PSReadLine EditMode: Vi
OS: 10.0.22621.1 (WinBuild.160101.0800)
BufferWidth: 120
BufferHeight: 30

Steps to reproduce

  • With Vi mode activated, use Set-PSReadLineOption -ViModeIndicator "Cursor"
  • Since the console starts on Insert mode, press scape to change to Normal.

Expected behavior

Like using "pure" powershell: cursor starts as "classic" (Insert mode) and then goes to "block" (Normal mode).

Actual behavior

Cursor stays the same, though it goes left one position.

Note that I've a vertical bar as the WT cursor, but I changed it to "classic" to see what happens and it doesn't work either.

@ghost ghost added the Needs-Triage 🔍 It's a new issue that core contributor team needs to triage. label Jun 2, 2022
@ghost ghost added the In-PR A PR is opened targeting the issue label Jul 6, 2022
@ghost ghost added Resolution-Fixed and removed Needs-Triage 🔍 It's a new issue that core contributor team needs to triage. In-PR A PR is opened targeting the issue labels Jul 8, 2022
@ghost
Copy link

ghost commented Mar 8, 2023

🎉 This issue was addressed in 3374, which has now been successfully released in v2.3.0-beta0. 🎉

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant