-
Notifications
You must be signed in to change notification settings - Fork 364
Unable to delete files over network on macOS #1046
Comments
I believe on macOS Trash is enabled by the existence of a sudo mkdir /.Trash-1000
sudo chown user:user ./Trash-1000 (This actually looks like #345; if so, sorry for asking you to create a new issue. I didn't find #345 in time as it's missing the mac label.) |
Not a problem, thanks for the fast replies. When I delete files via Finder they get permanently deleted and not put in the trash (which is expected) If however you are on the server and delete a file they are put in the trash which makes sense to me. I wouldn't actually want deleted files/folders put into a remote trash folder as someone would need to clear out the trash otherwise it could become a very large trash folder. A good solution would be for Atom to try and move it to trash but if that isn't possible show a permanent delete button or something similar that allows the files to be deleted. Perhaps this could be considered for the next version? |
@naterexw It doesn't work for me; anyone resolve this? |
I still have this problem (and the linked solution has a broken link now) |
I also have this problem (OS X 10.14.3, Atom 1.34.0) Edit: After reading the linked Windows issue it appears there is no intention to fix this behaviour in the core editor. The workaround is to install the permanent-delete package. |
Open your IDE |
Description
I have a project loaded over a local network and I am not able to delete files, I get an error "Is Trash enabled on the volume where the files are stored"
It looks like the issue is simply that the networked machine doesn't have a trash bin however this means that any file that I need to delete needs to be done via Finder.
This seems very similar to #856 but I was asked to open a new bug for macOS by @50Wliu
Steps to Reproduce
Expected behavior: [File should be deleted]
Actual behavior: [Error is shown.]
Reproduces how often: [100%]
Versions
Atom 1.16.0-beta0 x64
macOS Sierra 10.12.3
The text was updated successfully, but these errors were encountered: