← Back to context

Comment by kgwxd

7 years ago

Just because a folder is currently empty doesnt mean its not used and assumed to exist by some program. Delete shouldnt have been called, period.

I won't try to defend their execution, but I think they're trying to solve a legitimate issue. It's really confusing to an end-user if they see two Documents folders.

And I'm certain that I've personally encountered instances where both Documents folders had the Documents special folder icon (though I'm not sure if I've seen this on Win10, specifically)

  • So move/merge the locations since that is clearly the intention if the user has a redirection setup. A simple message confirming that "there are 2 Documents folders and would you like to move them to a single location" would be sufficient.

    This is just a project management failure that somehow got through, but the fact that it did seems to show major QA issues.

    • Merging the locations can easily get complicated. What if the same file exists in both folders? What if it exists in both folders, but with different contents? What if not only it has different contents, but also the same last modification time?

      2 replies →

  • I have two Documents folders. It's fucking confusing. But I'd think it shouldn't have been possible for them to exist in the first place. Windows Explorer is a mess.

    • I've run into this on a bunch of systems, and it absolutely is a mess. Particularly since Explorer gives all kinds of special status and UI elements to 'Documents' folders - if they just had the same name in different places I'd care way less.

      But the solution to "we screwed up years ago" is definitely not "nuke one instance with no warning and don't even glance at what's there".

      4 replies →

  • I ended up in this situation upgrading from 7 to 8 to 10 (not sure which transition was the culprit).