starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-04 05:35:20 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

vim in PowerShell and cmd sessions ignore cursor settings #6890

New Issue
Closed
opened 2026-01-31 00:49:48 +00:00 by claunia · 3 comments
claunia commented 2026-01-31 00:49:48 +00:00
Owner
Copy Link

Originally created by @parml on GitHub (Mar 15, 2020).

Environment

Windows build number: Microsoft Windows [Version 10.0.19041.113]
Windows Terminal version (if applicable): 0.9.433.0

Any other software?
vim for Windows (installed via chocolatey): 8.2.0381

Steps to reproduce

  1. Edit the vim configuration file ($HOME\_vimrc), append the snippet mentioned here: #4335 comment
  2. Open Windows Terminal
  3. Open new CMD or PowerShell session/tab.
  4. start vim -> vim starts in normal mode
  5. Type i to enter insert mode

Expected behavior

After step 4, according to configuration at step1 vim's cursor should be block
After step 5, according to conf at step 1. vim's cursor should be vertical bar.

Actual behavior

vim's cursor is at all times whatever cursor the terminal has.

Notes

Different vim cursors in normal vs insert modes do work partially in PowerShell and CMD windows (not started as sessions in Windows Terminal). Partially because the configuration at step 1 above is ignored indeed, however block for normal and underscore are the different cursors in the two modes.

This bug report only addresses only vim in PowerShell and CMD sessions in Windows Terminal.
Please refer to #4335 for a solution for vim in WSL sessions) works in both WSL1 and WSL2. There are two problems there as described in #4335 comment2

Thank you for building the soundest terminal on windows.

Originally created by @parml on GitHub (Mar 15, 2020). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING: 1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement. 2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement. 3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number). 4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement. 5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement. All good? Then proceed! --> <!-- This bug tracker is monitored by Windows Terminal development team and other technical folks. **Important: When reporting BSODs or security issues, DO NOT attach memory dumps, logs, or traces to Github issues**. Instead, send dumps/traces to secure@microsoft.com, referencing this GitHub issue. If this is an application crash, please also provide a Feedback Hub submission link so we can find your diagnostic data on the backend. Use the category "Apps > Windows Terminal (Preview)" and choose "Share My Feedback" after submission to get the link. Please use this form and describe your issue, concisely but precisely, with as much detail as possible. --> # Environment ```none Windows build number: Microsoft Windows [Version 10.0.19041.113] Windows Terminal version (if applicable): 0.9.433.0 Any other software? vim for Windows (installed via chocolatey): 8.2.0381 ``` # Steps to reproduce <!-- A description of how to trigger this bug. --> 1. Edit the vim configuration file ($HOME\\_vimrc), append the snippet mentioned here: [#4335 comment](https://github.com/microsoft/terminal/issues/4335#issuecomment-577365966) 2. Open Windows Terminal 3. Open new CMD or PowerShell session/tab. 4. start vim -> vim starts in normal mode 5. Type i to enter insert mode # Expected behavior After step 4, according to configuration at step1 vim's cursor should be block After step 5, according to conf at step 1. vim's cursor should be vertical bar. # Actual behavior vim's cursor is at all times whatever cursor the terminal has. # Notes Different vim cursors in normal vs insert modes do work partially in PowerShell and CMD windows (not started as sessions in Windows Terminal). Partially because the configuration at step 1 above is ignored indeed, however block for normal and underscore are the different cursors in the two modes. This bug report only addresses only vim in PowerShell and CMD sessions in Windows Terminal. Please refer to [#4335](https://github.com/microsoft/terminal/issues/4335) for a solution for vim in WSL sessions) works in both WSL1 and WSL2. There are two problems there as described in [#4335 comment2](https://github.com/microsoft/terminal/issues/4335#issuecomment-599246201) Thank you for building the soundest terminal on windows.
claunia added the Needs-TriageNeeds-Tag-Fix labels 2026-01-31 00:49:48 +00:00
claunia commented 2026-01-31 00:49:49 +00:00
Author
Owner
Copy Link

@jdebp commented on GitHub (Mar 16, 2020):

As I wrote in #4734, Windows Terminal already does what is needed here, pace the flushing problem. One can demonstrate it with CursorShape.ps1, indeed.

Therefore look to vim for the locus of this problem.

@jdebp commented on GitHub (Mar 16, 2020): As I wrote in #4734, Windows Terminal already does what is needed here, pace the flushing problem. One can demonstrate it with [CursorShape.ps1](https://github.com/jdebp/terminal-tests/blob/master/PowerShell/CursorShape.ps1), indeed. Therefore look to vim for the locus of this problem.
claunia commented 2026-01-31 00:49:49 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Mar 16, 2020):

Indeed. Thanks jdepb 😄

@DHowett-MSFT commented on GitHub (Mar 16, 2020): Indeed. Thanks jdepb :smile:
claunia commented 2026-01-31 00:49:49 +00:00
Author
Owner
Copy Link

@parml commented on GitHub (Mar 17, 2020):

@jdebp, thank you for the info.

neovim acts correctly when started (nvim). vim is the culprit in the OP and needs to be taught to act rightly, indeed.

One problem left. When neovim is exited, the Terminal is left with neovim's last cursor before exit (block) instead of underscore that the terminal profile has configured:

"name": "Windows PowerShell",
"cursorShape": "underscore"

and that incorrect cursor is not blinking. This will persist until session killed.

That problem has been reported here too.

Please let me know if neovim exits incorrectly so that I can address that with its team. Thanks.

@parml commented on GitHub (Mar 17, 2020): @jdebp, thank you for the info. neovim acts correctly when started (`nvim`). vim is the culprit in the OP and needs to be taught to act rightly, indeed. One problem left. When neovim is exited, the Terminal is left with neovim's last cursor before exit (block) instead of underscore that the terminal profile has configured: ``` "name": "Windows PowerShell", "cursorShape": "underscore" ``` and that incorrect cursor is not blinking. This will persist until session killed. That problem has been reported [here](https://github.com/microsoft/terminal/issues/4335#issuecomment-591338416) too. Please let me know if neovim exits incorrectly so that I can address that with its team. Thanks.
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 Needs-Tag-Fix Needs-Triage
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#6890
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?