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

Window Terminal + PowerShell/CMD + vim visualization problem #11453

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

Originally created by @NemoHoHaloAi on GitHub (Nov 17, 2020).

Environment

Windows build number: Microsoft Windows [version 10.0.18363.1198]
Windows Terminal version: Windows Terminal version: 1.4.3141.0
Vim

Steps to reproduce

  1. Open windows terminal
  2. create a powershell or cmd tab
  3. vim something, moving up and down.

this problem show in powershell and cmd but git-bash, so wired.

Expected behavior

wtbug

Actual behavior

vim can work as well.

Originally created by @NemoHoHaloAi on GitHub (Nov 17, 2020). # Environment Windows build number: Microsoft Windows [version 10.0.18363.1198] Windows Terminal version: Windows Terminal version: 1.4.3141.0 Vim # Steps to reproduce 1. Open windows terminal 2. create a powershell or cmd tab 3. vim something, moving up and down. this problem show in powershell and cmd but git-bash, so wired. # Expected behavior ![wtbug](https://user-images.githubusercontent.com/17694712/99333150-5f6e6d80-28bb-11eb-8505-3bb914c8c191.gif) # Actual behavior vim can work as well.
claunia added the Issue-QuestionNeeds-Tag-FixResolution-Answered labels 2026-01-31 02:48:05 +00:00
claunia commented 2026-01-31 02:48:05 +00:00
Author
Owner
Copy Link

@NemoHoHaloAi commented on GitHub (Nov 17, 2020):

Seem like the output buffer problem, but i dont kown how to fix that.

Need help, cuz i really want to use wt+vim.

@NemoHoHaloAi commented on GitHub (Nov 17, 2020): Seem like the output buffer problem, but i dont kown how to fix that. Need help, cuz i really want to use wt+vim.
claunia commented 2026-01-31 02:48:06 +00:00
Author
Owner
Copy Link

@skyline75489 commented on GitHub (Nov 17, 2020):

OK this is not expected. Git bash use its own VT parser so perhaps that's why it's working fine.

Does this happen all the time, or occasionally? Does this happen on WSL or over SSH? Is there any other operation that you have performed that may lead to this? For example, resizing the windows, pane operations?

@skyline75489 commented on GitHub (Nov 17, 2020): OK this is not expected. Git bash use its own VT parser so perhaps that's why it's working fine. Does this happen all the time, or occasionally? Does this happen on WSL or over SSH? Is there any other operation that you have performed that may lead to this? For example, resizing the windows, pane operations?
claunia commented 2026-01-31 02:48:06 +00:00
Author
Owner
Copy Link

@NemoHoHaloAi commented on GitHub (Nov 17, 2020):

Thanks for response.

  • it happen all the time.
  • no another operation, just start windows terminal, and in powershell or cmd windows use vim.
  • in WSL(ubuntu 20.04), it works as well as git-bash.
@NemoHoHaloAi commented on GitHub (Nov 17, 2020): Thanks for response. - it happen all the time. - no another operation, just start windows terminal, and in powershell or cmd windows use vim. - in WSL(ubuntu 20.04), it works as well as git-bash.
claunia commented 2026-01-31 02:48:06 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Nov 17, 2020):

Do you have a vim configuration that resizes the screen?

@DHowett commented on GitHub (Nov 17, 2020): Do you have a vim configuration that resizes the screen?
claunia commented 2026-01-31 02:48:06 +00:00
Author
Owner
Copy Link

@NemoHoHaloAi commented on GitHub (Nov 17, 2020):

Yeah, i had set the vim winpos and lines, that make this problem happen.

Now it is good, so much thanks to you guys, and respect for your great job in windows terminal, really cool tool.

@NemoHoHaloAi commented on GitHub (Nov 17, 2020): Yeah, i had set the vim winpos and lines, that make this problem happen. Now it is good, so much thanks to you guys, and respect for your great job in windows terminal, really cool tool.
claunia commented 2026-01-31 02:48:06 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Nov 17, 2020):

I am glad it helped! I'll close this. It is hard for Terminal to handle resize options right now. 😄

@DHowett commented on GitHub (Nov 17, 2020): I am glad it helped! I'll close this. It is hard for Terminal to handle resize options right now. :smile:
claunia commented 2026-01-31 02:48:06 +00:00
Author
Owner
Copy Link

@NemoHoHaloAi commented on GitHub (Nov 17, 2020):

Keep going!!!😊

@NemoHoHaloAi commented on GitHub (Nov 17, 2020): Keep going!!!😊
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#11453
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?