@waitingsong can you clarify what kind of VIM extension you have installed?

vim 0.12
https://marketplace.visualstudio.com/items?itemName=vscodevim.vim

@xconverge @jpoon any hints what this command does in your extension that could cause this?

It might be a good idea to disable all plugins, then enable just VSCodeVim. I also see ESlint in the settings which does something onSave... Maybe The vim remap is saving and closing while the eslint extension is doing something in between those 2 commands

i have disabled all other plugins except
vscode-language-pack-zh-hans and vim.
have tried under empty folder without package.json, eslint.json, tslint.json ,node_module ...etc, only create one file index.ts, still zero after shift zz.

its no problem with vsc version 1.20, but problem with 1.23.1

Ok I can reproduce this as well, I am not really sure where the bug resides but I have a workaround for you...

        {
            "before": [
                "Z",
                "Z"
            ],
            "after": [],
            "commands": [
                {
                    "command": ":wq",
                    "args": []
                },
            ]
        },

This at least performs the desired action somewhat atomically so there is no issue (even though the underlying commands being done here are the same as what you have in your remapping, there is a time delay between them in :wq). In the vim extension, we are still calling the commands with an await, but I wonder if VSCode is returning instantly when a save is called, yet not actually being performed until the buffer is already cleared thus resulting in saving a cleared buffer?

Not sure what you want to do here @bpasero

@xconverge it works. thanks a lot

The issue here was that:

• a file is not dirty
• a file is being saved (e.g. through a command or Ctrl+S)
• a save participant is running (asynchronously, potentially long running)
• a file is closed without waiting for the save to be finished
• the save participant comes back and now wants to save the file
• the file's underlying model has been disposed meanwhile and will now return an empty string as content
• we store an empty string as contents to the file

The fix is now to not save the file if the underlying model has been disposed meanwhile. In other words, it is not possible to save a (non-dirty) file and close it right after without waiting for the save to finish.

This was only an issue when the file was not dirty, because if the file is dirty, we prompt the user before closing the file to either save or revert it.

This was a cool example of how responsive you (the vscode devs) have been with this product. Thanks a lot! A cool example of OSS as well with an efficient issue comment section! (Until this comment ;) )

Verified I could reproduce without the fix and it no longer reproduces with the fix.

What version is the fix in? I’ve had this problem many times on prior and current version (as of 6/8/18) of vscode.

@joeandaverde This fix is in 1.24.0 and yesterday's insiders build. If you are on these or newer builds, could you open a new bug report?

I saw this issue in 1.24.0 and 1.23.1

I thought it was an issue with Prettier. Unfortunately, I am unable to reproduce.

prettier/prettier-vscode#489