deleted a chunk of my work the other day by pressing Ctrl z in windows explorer. my project was without source control installed (cuz it was in Dev stage), and Ctrl shit z/Ctrl y hotkeys didn't work, so that chunk was just gone, persished forever... or so I though. I remembered vs code having a file history under some panel. found it, and here it was - at least some of the latest history of my file. lesson learned: even in Dev where nothing is yet working, finish your day of coding with a commit to a remote repo.

[–] GreenKnight23@lemmy.world 10 points 16 hours ago (6 children)

all I'm learning from these stories is to stay far far away from vscode.

[–] Cethin@lemmy.zip 2 points 12 hours ago (1 children)

(VS)Code(ium) is great. (VSCode is MS fork of the OSS Codium.) It's a popular editor with a lot of plugin for just about every language. It has an integrated console. It can do basic Version control (and you can use the console for anything more). It's my favorite editor/IDE (not technically and IDE, at least out of the box). Just don't do things you don't understand. It's that simple. The OP fucked around, and they found out what it does the hard way. It's really easy to use if you have a basic understanding of things though.

[–] Txmyx 2 points 10 hours ago

/((vs)|(visual ?studio)):? ?(cod(e|ium)?)/igm

load more comments (4 replies)

load more comments (7 replies)