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

Terminal + PowerShell 7 + Vim = Trouble on Win 10 #20349

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

Originally created by @alan-isaac on GitHub (Aug 8, 2023).

Windows Terminal version

1.17.11461.0

Windows build number

10.0.19045.0

Other Software

Vim 9.0 in PowerShell 7

Steps to reproduce

Launch Windows Terminal from the Win 10 Start menu. My default terminal shell is PowerShell 7, which loads fine. (By default, I run as admin.) I experience no problems running PS commands here. However, inside this PS7 terminal shell enter vim C:\temp\temp.txt (a simple ASCII text file) and suddenly things go badly awry, even though the file seems to load normally into a Vim buffer.

Expected Behavior

Vim should behave normally, as it does within PowerShell 7 when not using Windows Terminal.

Actual Behavior

To give just one example, suppose the first thing I do after loading temp.txt into a Vim bugger (see: Steps to Reproduce) is to press v (to enter visual mode). The line the cursor is on disappears and seems to be deleted. As far as I can tell (?) however, something has happened to the screen drawing.

I do NOT have this problem when I launch PS 7 from the Start menu and then start Vim in exactly the same way. So adding Terminal into this mix produces the problem.

Originally created by @alan-isaac on GitHub (Aug 8, 2023). ### Windows Terminal version 1.17.11461.0 ### Windows build number 10.0.19045.0 ### Other Software Vim 9.0 in PowerShell 7 ### Steps to reproduce Launch Windows Terminal from the Win 10 Start menu. My default terminal shell is PowerShell 7, which loads fine. (By default, I run as admin.) I experience no problems running PS commands here. However, inside this PS7 terminal shell enter `vim C:\temp\temp.txt` (a simple ASCII text file) and suddenly things go badly awry, even though the file seems to load normally into a Vim buffer. ### Expected Behavior Vim should behave normally, as it does within PowerShell 7 when not using Windows Terminal. ### Actual Behavior To give just one example, suppose the first thing I do after loading temp.txt into a Vim bugger (see: Steps to Reproduce) is to press `v` (to enter visual mode). The line the cursor is on disappears and seems to be deleted. As far as I can tell (?) however, something has happened to the screen drawing. I do NOT have this problem when I launch PS 7 from the Start menu and then start Vim in exactly the same way. So adding Terminal into this mix produces the problem.
claunia added the Needs-TriageIssue-BugNeeds-Attention labels 2026-01-31 07:11:05 +00:00
claunia commented 2026-01-31 07:11:06 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Aug 9, 2023):

Oh oh oh now that I've slept on this, I bet this is #14512. Can you try Terminal Preview (v1.18), and set that as your Default Terminal, and try again/?

(xlinking https://superuser.com/questions/1800860/tricks-to-using-terminalpowershellvim?noredirect=1#comment2827168_1800860)

@zadjii-msft commented on GitHub (Aug 9, 2023): Oh oh oh now that I've slept on this, I bet this is #14512. Can you try [Terminal Preview](https://aka.ms/terminal-preview) (v1.18), and set that as your Default Terminal, and try again/? (xlinking https://superuser.com/questions/1800860/tricks-to-using-terminalpowershellvim?noredirect=1#comment2827168_1800860)
claunia commented 2026-01-31 07:11:06 +00:00
Author
Owner
Copy Link

@microsoft-github-policy-service[bot] commented on GitHub (Aug 13, 2023):

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.

@microsoft-github-policy-service[bot] commented on GitHub (Aug 13, 2023): This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for **4 days**. It will be closed if no further activity occurs **within 3 days of this comment**.
claunia commented 2026-01-31 07:11:07 +00:00
Author
Owner
Copy Link

@alan-isaac commented on GitHub (Aug 16, 2023):

Apologies, I've been away. The problem remains in Windows Terminal Preview Version: 1.18.1462.0 + PowerShell 7 + Vim 9.

@alan-isaac commented on GitHub (Aug 16, 2023): Apologies, I've been away. The problem remains in Windows Terminal Preview Version: 1.18.1462.0 + PowerShell 7 + Vim 9.
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-Bug Needs-Attention 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#20349
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?