muntedcrocodile@lemmy.world to Programmer Humor@programming.dev · 6 months agoSydney is very concerned about lost datalemmy.worldimagemessage-square16fedilinkarrow-up1205arrow-down17
arrow-up1198arrow-down1imageSydney is very concerned about lost datalemmy.worldmuntedcrocodile@lemmy.world to Programmer Humor@programming.dev · 6 months agomessage-square16fedilink
minus-squareNate@programming.devcakelinkfedilinkEnglisharrow-up4·6 months agoA real answer to your question though, as long as you can get it to reconnect, even if you have to close the window first, it should still have your changes to the file ready to save. These will be cached (somewhere?) unless you close the file.
minus-squaremuntedcrocodile@lemmy.worldOPlinkfedilinkarrow-up6·edit-26 months agoNar the remote died died. Clicking hdd died. Then again code is always better the second time u write it. And nothing cached on the client unfortunatly its all part of the server vscode instance thats on the dead hdd.
minus-squareNate@programming.devcakelinkfedilinkEnglisharrow-up8·6 months agoDamn, when you said remote died I thought you meant lost connection
minus-squaremuntedcrocodile@lemmy.worldOPlinkfedilinkarrow-up2·6 months agoNar im fucked i guess code is always better the second time u write it lol
A real answer to your question though, as long as you can get it to reconnect, even if you have to close the window first, it should still have your changes to the file ready to save. These will be cached (somewhere?) unless you close the file.
Nar the remote died died. Clicking hdd died. Then again code is always better the second time u write it.
And nothing cached on the client unfortunatly its all part of the server vscode instance thats on the dead hdd.
Damn, when you said remote died I thought you meant lost connection
Nar im fucked i guess code is always better the second time u write it lol