Make Delete Scripting Command More Like "Nuke"

[Jeff Bellune]

I'd like to have the delete scripting command work like Nuke.

If I delete user temp files by using Nuke, any file that's open or protected gets silently ignored.

If I delete those same files by script:

Code: Select all

DELETE 0,0,"E:\User\Temp\*"

Then I get the standard Try Again/Cancel warning dialog.

I have UAC turned completely off in Vista 64.

I've noticed that even with Nuke, any open or protected files in the system temp folder (Windows\Temp) will produce the warning dialogs.

Is that because the OS is 64-bit and XY is 32-bit?

I ask that question because another file manager program that-I-don't-like-anywhere-near-as-much-as-XY-for-lots-of-reasons has a 64-bit version with a quiet deletion mode that suppresses even the system temp file warnings.

-Jeff

[jacky]

I'd like to have the delete scripting command work like Nuke.

I think what you're after would be for command delete to have a param to "Skip Locked" which could be nice, yeah.

[Jeff Bellune]

I'd like to have the delete scripting command work like Nuke.

I think what you're after would be for command delete to have a param to "Skip Locked" which could be nice, yeah.

Oooooh. "Skip Locked". I like it a lot!

[Jeff Bellune]

Is adding the "Skip Locked" parameter to the scripting "Delete" command possible? It seems like a nice FR.

-Jeff

[admin]

Is adding the "Skip Locked" parameter to the scripting "Delete" command possible? It seems like a nice FR.

Later. Also "Safe Erase" (what should have been called "Nuke" properly) should/could be added: repeated overwriting with random patterns.

What's FR?? Feature?

[Jeff Bellune]

Is adding the "Skip Locked" parameter to the scripting "Delete" command possible? It seems like a nice FR.

Later. Also "Safe Erase" (what should have been called "Nuke" properly) should/could be added: repeated overwriting with random patterns.

What's FR?? Feature?

Thanks, Don.

Feature Request

-Jeff