Unsaved file lost when clicking the "restart to update" message in bottom bar #30665
Closed
raymonde
started this conversation in
Feature Requests
Replies: 6 comments 3 replies
|
The same behaviour happened to me after updating to 202.0. |
2 replies
|
Jesus Effing Christ... |
0 replies
|
Seems like this is still an issue. Just lost a buffer to an update. |
0 replies
|
Thanks for reaching out. We want to better support our community, and the best way for us to do that is through our official Discord. The team is active there and happy to help. We’re closing the “Help and General Q&A” category on GitHub Discussions and directing all support questions to Discord going forward. |
0 replies
|
very disappointing; lost a few good files. |
0 replies
|
You can recover workspace state from SQLite DB zed keeps (ask claude), but yeah, very disappointing DUX. Clicked restart to update, and boom, unsaved buffers gone. Luckily managed to recover with Claude. |
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Not sure if this is a bug or a feature request at this point in the Zed development cycle.
I had an unsaved file buffer open. Note that this was a new file buffer that had never been saved, not an existing file with unsaved edits, if that makes a difference in the flow.
I clicked on an upgrade message in the bottom bar of the Zed window. The message was something like "click to restart and update". Zed restarted and updated, but I was surprised that the unsaved file buffer was not restored. I would have expected either a prompt before restarting to save the buffer, or for it to be restored from a temp file automatically.
Is the expected behavior at this point (185.15 -> 185.16)? I'm trying to calibrate how careful to be with data in Zed. Thanks.
All reactions