Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Separate explorer.confirmDelete into 2 options (Explorer: Confirm Delete) #175760

Closed
Tracked by #203279
RobbyCBennett opened this issue Mar 1, 2023 · 4 comments
Closed
Tracked by #203279
Assignees
Labels
feature-request Request for new features or functionality file-explorer Explorer widget issues

Comments

@RobbyCBennett
Copy link
Contributor

Explorer: Confirm Delete

  • Controls whether the Explorer should ask for confirmation when deleting a file via the trash.

Separate this option into 2 options:

Explorer: Confirm Delete with Trash

  • Controls whether the Explorer should ask for confirmation when deleting a file with the trash.

Explorer: Confirm Delete without Trash

  • Controls whether the Explorer should ask for confirmation when deleting a file without the trash.

Why should this happen? It would allow Linux/WSL users, who have no trash by default to delete things without an intrusive popup. We still have undo and version control, so it still shouldn't result in many problems with accidently deleted files.

@RobbyCBennett
Copy link
Contributor Author

Additionally, adding this option would allow for faster deletion on any operating system. We could disable files.enableTrash to speed up the file operation, then disable the new theoretical option explorer.confirmDeleteWithoutTrash to speed up the UI by removing the popup.

@lramos15 lramos15 added feature-request Request for new features or functionality file-explorer Explorer widget issues labels Dec 4, 2023
@vscodenpa vscodenpa added this to the Backlog Candidates milestone Dec 4, 2023
@vscodenpa
Copy link

This feature request is now a candidate for our backlog. The community has 60 days to upvote the issue. If it receives 20 upvotes we will move it to our backlog. If not, we will close it. To learn more about how we handle feature requests, please see our documentation.

Happy Coding!

@vscodenpa
Copy link

This feature request has not yet received the 20 community upvotes it takes to make to our backlog. 10 days to go. To learn more about how we handle feature requests, please see our documentation.

Happy Coding!

@CHINOBKLING CHINOBKLING mentioned this issue Jan 24, 2024
@vscodenpa
Copy link

🙁 In the last 60 days, this feature request has received less than 20 community upvotes and we closed it. Still a big Thank You to you for taking the time to create this issue! To learn more about how we handle feature requests, please see our documentation.

Happy Coding!

@vscodenpa vscodenpa closed this as not planned Won't fix, can't repro, duplicate, stale Feb 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature-request Request for new features or functionality file-explorer Explorer widget issues
Projects
None yet
Development

No branches or pull requests

3 participants