PSReadLine's -ViModeIndicator "Cursor" doesn't work correctly

[nlguerra2003]

Windows Terminal version

1.12.10983.0

Windows build number

10.0.22621.0

Other Software

PSReadLine

Steps to reproduce

• Activate PSReadLine's Vi mode: Set-PSReadLineOption -EditMode Vi
• Activate "Cursor" as mode indicator: Set-PSReadLineOption -ViModeIndicator Cursor
• Since you start in INSERT mode, just type Esc to change to NORMAL.

Expected Behavior

Cursor should, as it happens in "pure" powershell, be a box in NORMAL mode, and the default one in INSERT (it doesn't matter what cursor you set up in WT).

Actual Behavior

Cursor won't change no matter what mode you select. It will always be the configured cursor.

[zadjii-msft]

Which version of PowerShell and PSReadline are you using/?

[nlguerra2003]

PS Version: 7.2.4
PSReadLine Version: 2.2.5

[juliekoubova]

Happy holidays, folks! Any update on this?

[j4james]

The problem was that PSReadLine was originally using the .NET Console.CursorSize API to change the cursor size, and that relies on the Win32 SetConsoleCursorInfo API, which isn't supported in Windows Terminal (that's more or less tracked in issue #7382).

The good news is that PSReadLine recently merged a PR (PowerShell/PSReadLine#3374) which updates the ViModeIndicator implementation to use escape sequences to change the cursor shape (switching between a block cursor and underscore cursor), and that should work in Windows Terminal.

Unfortunately it doesn't look like that fix has been released yet, but I'm guessing it will likely be included in the next PSReadLine release.

[zadjii-msft]

Sorry, must've lost this in the backlog.

Yep, I'd reckon this is fixed by the aforementioned upstream PsReadline issue.

/dup PowerShell/PSReadLine#3334

[ghost]

Hi! We've identified this issue as a duplicate of one that exists on somebody else's Issue Tracker. Please make sure you subscribe to the referenced external issue for future updates. Thanks for your report!