starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-09-25 00:15:10 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

dynamic cursorShape for shell vi mode #6636

New Issue
Closed
opened 2026-01-31 00:43:36 +00:00 by claunia · 4 comments
claunia commented 2026-01-31 00:43:36 +00:00
Owner
Copy Link

Originally created by @mpgarate on GitHub (Feb 27, 2020).

Hello Terminal team 👋

Description of the new feature/enhancement

When normal mode is active in vim or shell vi mode, the cursor stays in the same style ("bar"). On mac and linux terminals the cursor would typically change to something like the "emptyBox" shape for normal mode and "bar" for insert mode.

To reproduce this behavior, we can use Windows Terminal to run cygwin or access a linux machine via ssh and run the following:

set -o vi

Then, pressing escape will enter normal mode where we might expect to see a box highlighting the current letter. Instead we still see the "bar" style, moved one character back. The "box" appearance is helpful to see which character is selected and as a visual aid to know when insert or normal mode is active.

I found a few workarounds for vim using vimrc (i.e. in issue #68) but have not yet seen a suggestion for shell vi mode.

Originally created by @mpgarate on GitHub (Feb 27, 2020). Hello Terminal team 👋 # Description of the new feature/enhancement When normal mode is active in vim or shell vi mode, the cursor stays in the same style ("bar"). On mac and linux terminals the cursor would typically change to something like the "emptyBox" shape for normal mode and "bar" for insert mode. To reproduce this behavior, we can use Windows Terminal to run cygwin or access a linux machine via ssh and run the following: ```sh set -o vi ``` Then, pressing escape will enter normal mode where we might expect to see a box highlighting the current letter. Instead we still see the "bar" style, moved one character back. The "box" appearance is helpful to see which character is selected and as a visual aid to know when insert or normal mode is active. I found a few workarounds for vim using vimrc (i.e. in issue #68) but have not yet seen a suggestion for shell vi mode.
claunia added the Issue-QuestionNeeds-Tag-FixResolution-Answered labels 2026-01-31 00:43:36 +00:00
claunia commented 2026-01-31 00:43:37 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Feb 27, 2020):

Maybe some combo of #4106, #1604 - I could have sworn there was a more specific dupe...

@zadjii-msft commented on GitHub (Feb 27, 2020): Maybe some combo of #4106, #1604 - I could have sworn there was a more specific dupe...
claunia commented 2026-01-31 00:43:37 +00:00
Author
Owner
Copy Link

@jdebp commented on GitHub (Feb 27, 2020):

Windows Terminal already supports the DECSCUSR control sequence with parameters from 1 to 8. There's nothing else that Windows Terminal has to do, here, pace the bug about it not taking effect until flushed. The rest is all at the host end.

The rest is a matter of having the Ss and Se capabilities in your terminfo database records, and a shell that understands those (relatively new, as they were invented in 2011) terminal capabilities. It is almost certainly terminal type and terminfo that is your problem here.

@jdebp commented on GitHub (Feb 27, 2020): Windows Terminal already supports the DECSCUSR control sequence with parameters from 1 to 8. There's nothing else that Windows Terminal has to do, here, pace the bug about it not taking effect until flushed. The rest is all at the host end. The rest is a matter of having the `Ss` and `Se` capabilities in your terminfo database records, and a shell that understands those (relatively new, as they were invented in 2011) terminal capabilities. It is almost certainly terminal type and terminfo that is your problem here.
claunia commented 2026-01-31 00:43:38 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Feb 27, 2020):

Indeed! Thanks @jdebp.

In addition, somebody's put together a solution for versions of readline that do not take Ss and Se into account: https://stackoverflow.com./a/48449104

@DHowett-MSFT commented on GitHub (Feb 27, 2020): Indeed! Thanks @jdebp. In addition, somebody's put together a solution for versions of readline that do not take `Ss` and `Se` into account: https://stackoverflow.com./a/48449104
claunia commented 2026-01-31 00:43:38 +00:00
Author
Owner
Copy Link

@mpgarate commented on GitHub (Feb 28, 2020):

Thank you for the responses. In my case, cygwin with bash 4.4.12 did not work with show-mode-in-prompt, and (as expected) this did not work in an older linux bash 4.2.46 I had available for testing. It will take some more investigation on my part to troubleshoot.

@mpgarate commented on GitHub (Feb 28, 2020): Thank you for the responses. In my case, cygwin with bash 4.4.12 did not work with `show-mode-in-prompt`, and (as expected) this did not work in an older linux bash 4.2.46 I had available for testing. It will take some more investigation on my part to troubleshoot.
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-Question Needs-Tag-Fix Resolution-Answered
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#6636
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?