-
-
Notifications
You must be signed in to change notification settings - Fork 816
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
Add --delete flag for file deletion on Windows #871
Comments
See also #387. Proper delete support requires post-order traversal which is not trivial to implement. However, considering the difficulty of doing this on Windows, I think I'm in favour of implementing In the meantime, you can make a wrapper script or batch file or something. Or use CMD/PowerShell's equivalent of |
I would suggest adding such a workaround in README for the time being, it is quite confusing for new users:
works for me. Spawning a lot of processes isn't really the way to do some things on Windows as this is inherently much slower than Linux, and antivirus software such as Windows Defender further slow that down because they perform scanning when a process is spawned. |
Linux users could also benefit from |
As discussed in #387, I think that a |
Ok, I'm happy to revisit this. The restriction to files could be a way to get rid of (some of) the edge cases discussed in #387. |
The equivalent on Windows is $ fd -g "*.orig" -x cmd /c del |
if you are using powershell core you can use the following:
|
I have been here: #538, #585, #253.
On Windows,
del
is used in CMD whileRemove-Item
is used in PowerShell, both are built-in commands.Therefore, there is no anything like a
rm
executable on Windows and-X
or-x
will not work.Currently I have something like this in order to simply delete a file, which is not desirable as it spawns a shell every time, and spawning processes on Windows is much slower than on Linux:
The text was updated successfully, but these errors were encountered: