admin管理员组

文章数量:1352147

On my macbook, I leave VSCode open pretty much 100% of the time and allow it to sleep when I'm not using it (fairly typical use?). Recently, when I wake my mac back up and go to VSCode, all of the open files are marked as modified even though they weren't. See: the little circle over what is usually the X to close the tab.

None of these files were modified before the macbook fell asleep. If I try to close them I'm met with a dialog asking if I want to save. If I try to save, I'm told it failed to save because the content of the file is newer.

It's as if I had a bunch of files open and then checked out an entirely different branch in git in which all of these files were modified. Except they weren't / aren't modified.

Does anyone know why VSCode / Mac thinks all of my open files were modified after sleeping? It's incredibly annoying to have to answer all of the confirmation dialogs each time.

This doesn't just happen in one project / directory. It's all of them which makes me think it's a system / OS-level foible.

本文标签: macosWhy does VSCode mark open files as modified after macbook falls asleepStack Overflow