this post was submitted on 20 Nov 2024
870 points (97.6% liked)

Programmer Humor

19774 readers
11 users here now

Welcome to Programmer Humor!

This is a place where you can post jokes, memes, humor, etc. related to programming!

For sharing awful code theres also Programming Horror.

Rules

founded 2 years ago
MODERATORS
870
submitted 3 weeks ago* (last edited 3 weeks ago) by [email protected] to c/[email protected]
you are viewing a single comment's thread
view the rest of the comments
[–] eating3645 126 points 3 weeks ago (31 children)

Steps to Reproduce:

1.Go near this fucking shit editor.

2.Commit the deadly sin of touching the source control options.

🤣

[–] [email protected] 90 points 3 weeks ago (29 children)
  1. Ignore the scary warning VS Code shows you when you press the button.
[–] Hawke 110 points 3 weeks ago (15 children)

I dunno, “discard changes” is usually not the same as “delete all files”

[–] Starbuck -4 points 3 weeks ago (1 children)

What exactly do you think discard means?

[–] Hawke 70 points 3 weeks ago (3 children)

“Changes” are not the same thing as “files”.

I’d expect that files that are not in version control would not be touched.

[–] [email protected] 12 points 2 weeks ago* (last edited 2 weeks ago)

Yeah. That's discussed in more detail in the code change that resulted from the issue report.

It's a ballsy move by the VSCode team to not only include git clean but to keep it after numerous issue reports.

As others discussed in that thread, git clean has no business being offered in a graphical menu where a git novice may find it.

That said, I do think the expanded warning mesage they added addresses the issue by calling out that whatever git may think, the user is about to lose some files.

[–] EleventhHour 11 points 3 weeks ago* (last edited 3 weeks ago) (2 children)

Apparently, it means changes to the directory structure and what files are in them, not changes within the files themselves. It really ought to be more clear about this.

[–] [email protected] 4 points 2 weeks ago* (last edited 2 weeks ago)

Yeah. They did substantially modify the message to make it much clearer, thankfully.

[–] [email protected] 3 points 2 weeks ago

It means both.

[–] [email protected] 4 points 3 weeks ago* (last edited 3 weeks ago) (2 children)

"Changes" encompass more than you think. Creating / Deleting files are also changes, not just edits to a file.

  • If the change is an edit to a tracked file, "Discard Changes" will reverse the edit.
  • If the change is deleting a tracked file, "Discard Changes" will restore it back.
  • If the change is a new untracked file, "Discard Changes" will remove it as intended.

It can also be all of them at the same time, which is why VSCode uses "Changes" instead of "Files".

[–] Hawke 24 points 2 weeks ago (1 children)

And the terminology is misleading, resulting in problems. shrug.

[–] Eranziel 0 points 2 weeks ago

I find it difficult to lay the blame with VSCode when the terminology belongs to git, which (even 7 years ago) was an industry standard technology.

People using tools they don't understand and plowing ahead through scary warnings will always encounter problems.

[–] candybrie 7 points 2 weeks ago

If the change is a new untracked file

Wasn't the issue that it deleted a bunch of preexisting untracked files? So old untracked files.

load more comments (13 replies)
load more comments (26 replies)
load more comments (27 replies)