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 cursror is always set to the one of Windows Terminal #15050

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

Originally created by @stephane-archer on GitHub (Sep 1, 2021).

Windows Terminal version (or Windows build number)

1.9.1942.0

Other Software

VIM - Vi IMproved 8.1 in WLS

Steps to reproduce

just open vim and you will see the cursor is not showing properly

Expected Behavior

No response

Actual Behavior

I don't see the right cursor when I open vim.

Please note, I'm not reporting a problem with vim and looking for a way to configure it properly.

I'm reporting a bug for this app because vim is working properly with all the other terminal emulators.

Is there a reason why this app doesn't support vim like all the others? Is it expected behavior? Can you explain why you made that decision?

Originally created by @stephane-archer on GitHub (Sep 1, 2021). ### Windows Terminal version (or Windows build number) 1.9.1942.0 ### Other Software VIM - Vi IMproved 8.1 in WLS ### Steps to reproduce just open vim and you will see the cursor is not showing properly ### Expected Behavior _No response_ ### Actual Behavior I don't see the right cursor when I open vim. Please note, I'm not reporting a problem with vim and looking for a way to configure it properly. I'm reporting a bug for this app because vim is working properly with all the other terminal emulators. Is there a reason why this app doesn't support vim like all the others? Is it expected behavior? Can you explain why you made that decision?
claunia added the Resolution-Duplicate label 2026-01-31 04:27:01 +00:00
claunia commented 2026-01-31 04:27:02 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Sep 1, 2021):

Wow, this is a word-for-word /dupe of #8560, including the typo. Please make sure to search before filing new issues.

@zadjii-msft commented on GitHub (Sep 1, 2021): Wow, this is a word-for-word /dupe of #8560, _including the typo_. Please make sure to search before filing new issues.
claunia commented 2026-01-31 04:27:02 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Sep 1, 2021):

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@ghost commented on GitHub (Sep 1, 2021): Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!
claunia commented 2026-01-31 04:27:03 +00:00
Author
Owner
Copy Link

@stephane-archer commented on GitHub (Sep 1, 2021):

I think you missed the important part of the issue/question:

Is there a reason why this app doesn't support vim like all the others? Is it expected behavior? Can you explain why you made that decision?

the issue you mention is looking for a way to configure Vim to adapt to this app, this is not what I'm looking for

@stephane-archer commented on GitHub (Sep 1, 2021): I think you missed the important part of the issue/question: > Is there a reason why this app doesn't support vim like all the others? Is it expected behavior? Can you explain why you made that decision? the issue you mention is looking for a way to configure Vim to adapt to this app, this is not what I'm looking for
claunia commented 2026-01-31 04:27:03 +00:00
Author
Owner
Copy Link

@aguevara commented on GitHub (Sep 27, 2021):

I agree, that other issue was closed with no resolution, this is a bug in WT, vim works properly in any other terminal, it only fails to work properly in WT.

@aguevara commented on GitHub (Sep 27, 2021): I agree, that other issue was closed with no resolution, this is a bug in WT, vim works properly in any other terminal, it only fails to work properly in WT.
claunia commented 2026-01-31 04:27:03 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Sep 27, 2021):

It's not valuable to the community to have multiple instances of the same discussion occurring in multiple places around the repo. It's generally better to consolidate discussion into one place, so people can both identify root causes and workarounds while we work on fixes to the root causes. I literally only just closed #8560 minutes ago, because the root cause of that issue is actually being tracked in #7382. Dup'ing these all to the same bucket help us identify the root cause of issues like this.

@zadjii-msft commented on GitHub (Sep 27, 2021): It's not valuable to the community to have multiple instances of the same discussion occurring in multiple places around the repo. It's generally better to consolidate discussion into one place, so people can both identify root causes and workarounds while we work on fixes to the root causes. I literally only just closed #8560 minutes ago, because the root cause of _that_ issue is actually being tracked in #7382. Dup'ing these all to the same bucket help us identify the root cause of issues like this.
claunia commented 2026-01-31 04:27:04 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Sep 21, 2023):

This thread was duped to #8560, which if you'll read, was eventually duped to #7382, which is still open.

as I said in literally the last comment

@zadjii-msft commented on GitHub (Sep 21, 2023): This thread was duped to #8560, which if you'll read, was eventually duped to #7382, which is still open. _as I said in literally the last comment_
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 Resolution-Duplicate
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#15050
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?