You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 15, 2022. It is now read-only.
I have Windows 10, project is on samba network share on Ubuntu server 20.04
Can't delete files due of this "is there recycle bin on the drive where files are stored".
I added "delete permanently package" - now shift-del asks if i want to delete permanently, - I accept, get no error messages but file still does not disappear. I can delete file on explorer tho with no any problem.,
User logged in has full permissions on samba share.
Running Atom as administrator doesn't seem to make difference.
As this would be so such a wonderful software - Couldn't you guys just add option in the preferences if user wants be able to
"[X] Delete files without using recycle bin" without hacking it. I'd very much rather code with Atom instead of that horrible visual studio code piece of crap
The text was updated successfully, but these errors were encountered:
I added a PR that allows deleting things permanently. I have seen this error too, and it is very annoying. So, #1373 should give a way to avoid the error.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I have Windows 10, project is on samba network share on Ubuntu server 20.04
Can't delete files due of this "is there recycle bin on the drive where files are stored".
I added "delete permanently package" - now shift-del asks if i want to delete permanently, - I accept, get no error messages but file still does not disappear. I can delete file on explorer tho with no any problem.,
As this would be so such a wonderful software - Couldn't you guys just add option in the preferences if user wants be able to
"[X] Delete files without using recycle bin" without hacking it. I'd very much rather code with Atom instead of that horrible visual studio code piece of crap
The text was updated successfully, but these errors were encountered: