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

Terminal Vim opens files in REPLACE mode by default #10609

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

Originally created by @nickjj on GitHub (Sep 12, 2020).

Environment

Windows build number: Microsoft Windows [Version 10.0.19041.508]
Windows Terminal version (if applicable): Windows Terminal Preview / Version: 1.3.2382.0

It's also worth pointing out the problem exists with the regular stable release of Windows Terminal too.

Steps to reproduce

  1. Within Ubuntu 20.04 LTS WSL 2 install Vim with sudo apt-get update && sudo apt-get install vim-gtk
  2. touch test.txt
  3. vim test.txt
  4. Notice that you're in REPLACE mode instead of NORMAL mode

Expected behavior

When opening a file you should be in NORMAL mode by default.

Actual behavior

You're in REPLACE mode by default instead of NORMAL mode.

I believe this is specific to MS terminal because this problem doesn't happen with wsltty (another Windows terminal). I've also never seen this problem happen in native Linux on any terminal with the same vimrc file that I use.

The workaround for now is to set set t_u7= in your vimrc, but this conflicts with other terminals so it's not a bullet proof solution.

The interesting thing is the issue doesn't happen if you run vim -u NONE which disables user specific configuration, but this thread on StackOverflow makes it seem like it definitely is something stemming from the Windows terminal in the end https://superuser.com/a/1525060.

Originally created by @nickjj on GitHub (Sep 12, 2020). # Environment ```none Windows build number: Microsoft Windows [Version 10.0.19041.508] Windows Terminal version (if applicable): Windows Terminal Preview / Version: 1.3.2382.0 ``` It's also worth pointing out the problem exists with the regular stable release of Windows Terminal too. # Steps to reproduce 1. Within Ubuntu 20.04 LTS WSL 2 install Vim with `sudo apt-get update && sudo apt-get install vim-gtk` 2. `touch test.txt` 3. `vim test.txt` 4. Notice that you're in REPLACE mode instead of NORMAL mode # Expected behavior When opening a file you should be in NORMAL mode by default. # Actual behavior You're in REPLACE mode by default instead of NORMAL mode. --- I believe this is specific to MS terminal because this problem doesn't happen with wsltty (another Windows terminal). I've also never seen this problem happen in native Linux on any terminal with the same vimrc file that I use. The workaround for now is to set `set t_u7=` in your vimrc, but this conflicts with other terminals so it's not a bullet proof solution. The interesting thing is the issue doesn't happen if you run `vim -u NONE` which disables user specific configuration, but this thread on StackOverflow makes it seem like it definitely is something stemming from the Windows terminal in the end https://superuser.com/a/1525060.
claunia added the Resolution-Duplicate label 2026-01-31 02:25:39 +00:00
claunia commented 2026-01-31 02:25:40 +00:00
Author
Owner
Copy Link

@j4james commented on GitHub (Sep 12, 2020):

I'm guessing this is the same problem as issue #1637, which was recently fixed in PR #7583. The fix should be available in the next preview release.

@j4james commented on GitHub (Sep 12, 2020): I'm guessing this is the same problem as issue #1637, which was recently fixed in PR #7583. The fix should be available in the next preview release.
claunia commented 2026-01-31 02:25:40 +00:00
Author
Owner
Copy Link

@nickjj commented on GitHub (Sep 12, 2020):

Indeed, thanks. There's also more discussion from the Vim side at https://github.com/vim/vim/issues/6365#issuecomment-652353135.

@nickjj commented on GitHub (Sep 12, 2020): Indeed, thanks. There's also more discussion from the Vim side at https://github.com/vim/vim/issues/6365#issuecomment-652353135.
claunia commented 2026-01-31 02:25:40 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Sep 12, 2020):

/dup #1637 thanks all!

@DHowett commented on GitHub (Sep 12, 2020): /dup #1637 thanks all!
claunia commented 2026-01-31 02:25:40 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Sep 12, 2020):

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 12, 2020): 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!
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#10609
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?