Undo replaces file content
See original GitHub issueThis a BUG REPORT
How to reproduce it:
- Open document A
- Open document B
- Type
:wq
(or just close and save file) - Open B again
- You can do some changes or do not (most annoying if you do)
- Press
u
What happened: Content of document B will be replaced on content of A
What did you expect to happen: Nothing
Environment:
- Extension (VsCodeVim) version: 0.11.4
- VSCode version: 1.22.2
- OS version: Arch Linux
Issue Analytics
- State:
- Created 5 years ago
- Reactions:7
- Comments:5 (2 by maintainers)
Top Results From Across the Web
How to Recover Overwritten Word Document & Excel File?
How do I undo an overwritten file? · Navigate to the folder that contained the file. · In the Home tab, click History....
Read more >【Fixed 2023】5 Ways to Recover Overwritten Files from ...
Method 1: How to Undo an Overwritten File Replaced from the Previous Versions? Method 2: Recover Overwritten Files on Windows 10 By Previous...
Read more >undo an accidental file replace - Microsoft Community
i accidentally replaced a powerpoint file. i need to do the replace and get my old file back. how do i do this?...
Read more >How to Recover Overwritten Files - 12 Possible Methods (2022)
To revert a “protected” file to a previous state, right-click on it and choose properties. From there, move to the “Previous versions” tab...
Read more >How to Recover Overwritten Files in Windows 10/8/7 Easily
1. Right-click the file and choose "Properties". · 2. Open the "Previous Version" tab. · 3. Select the latest version and click "Restore"...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
This is a longstanding bug (see https://github.com/VSCodeVim/Vim/issues/2007). Thank you SO MUCH for figuring out a way to reproduce it. As you can see, a lot of people tried without success.
For the record, I needed to really open the documents, i.e. either Ctrl+S or double-click the header. Temporarily opening A did not trigger the bug, a.k.a
:wq
u
This particular issue is fixed in https://github.com/VSCodeVim/Vim/pull/2547