Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Terminal Vim opens files in REPLACE mode by default #7615

Closed
nickjj opened this issue Sep 12, 2020 · 4 comments
Closed

Terminal Vim opens files in REPLACE mode by default #7615

nickjj opened this issue Sep 12, 2020 · 4 comments
Labels
Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@nickjj
Copy link

nickjj commented 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.

@ghost ghost added Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Tag-Fix Doesn't match tag requirements labels Sep 12, 2020
@j4james
Copy link
Collaborator

j4james commented 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.

@nickjj
Copy link
Author

nickjj commented Sep 12, 2020

Indeed, thanks. There's also more discussion from the Vim side at vim/vim#6365 (comment).

@DHowett
Copy link
Member

DHowett commented Sep 12, 2020

/dup #1637 thanks all!

@ghost
Copy link

ghost commented 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 ghost closed this as completed Sep 12, 2020
@ghost ghost added Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing. and removed Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Tag-Fix Doesn't match tag requirements labels Sep 12, 2020
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.
Projects
None yet
Development

No branches or pull requests

3 participants