Support abandonment of recent folders with unsaved changes

[Clockwork-Muse]

I'm trying to clean up my list of recent folders. And yet, if I had any unsaved changes (including from any temporary "notebook" windows), I get:

The original source is gone. I no longer want whatever files they may have been. Many of these were devcontainers, that have been removed from docker via docker system prune -af --volumes - I'd have to re-clone the repo and rebuild the container to even look at them (however long that takes). Or in other situations the target system may simply be permanently gone for whatever reason (ie, were attached to a remote device that got sent back to a factory).

Can we please get some sort of Abandon button here, to account for that?

[amunger]

when are you getting that pop-up? Do you have repro steps for this?

[Clockwork-Muse]

I'm getting the pop-up when I try to "clean up" my recently closed:

• File -> Open Recent -> More...
• Mouse over the far-right of the line on the dialog box, and an X will appear. Click that X:

Folders with unsaved files will initially have a filled circle in place of the X.

Unfortunately, I don't have a repro to set the situation up at the moment. My guess is that something around the timing of losing connection to the location (devcontainer or remote host) while having unsaved changes means that closing the window doesn't pop up the normal "discard changes" dialog.

[bpasero]

Backups are persisted locally, even for remote workspaces so you should be able to get rid of them by manually deleting the contents in the %APPDATA%\Code\Backups folder, can you check the contents? Make sure to not delete it all if you have any other dirty files you want to preserve though.

[Clockwork-Muse]

Yes, I have contents in %APPDATA$\Code\Backups. Very mysteriously named hash filenames.
Obviously, I can delete these files, but:

1. This isn't a discoverable solution, because I didn't know this was a relevant folder, or even that it existed.
2. It's also not a friendly solution, because there isn't a way to tell what folder this refers to.

[vs-code-engineering]

This feature request is now a candidate for our backlog. The community has 60 days to upvote the issue. If it receives 20 upvotes we will move it to our backlog. If not, we will close it. To learn more about how we handle feature requests, please see our documentation.

Happy Coding!

[1040170566]

I've encountered this issue as well. I have absolutely no idea which file is supposedly unsaved, but the notification persists, causing this workspace to remain on the list. I could choose to ignore it, but it's quite bothersome.

[vs-code-engineering]

This feature request has not yet received the 20 community upvotes it takes to make to our backlog. 10 days to go. To learn more about how we handle feature requests, please see our documentation.

Happy Coding!

[vs-code-engineering]

🙁 In the last 60 days, this feature request has received less than 20 community upvotes and we closed it. Still a big Thank You to you for taking the time to create this issue! To learn more about how we handle feature requests, please see our documentation.

Happy Coding!