In a dupe: scenario, cut/paste across volumes is not reflected

[therube]

In a dupe: scenario, cut/paste across volumes is not reflected.

Was that always the case?



Everything (1411)

dupe-from:P: dupe:size dupe-min:4

on a cut/paste across volumes,
the cut item in the Results List is lost

(as it was, the file names were named differently,
& i was wanting, after the move, to rename them all the
same, but they are all no longer there, so i can only
rename /some/ of them...)

- was that always the case?


i saw, distinct:/unique: will no longer add new results,
but that would seem to be different (& will have to see how that turns out )

[void]

This has always been the case.

dupe: will not add new results.
existing results will be updated in realtime when using dupe:

When the file is moved to another volume, it is not a move, but a copy and delete.
The item is removed from the result list and never readded.

Press F5 to refresh the dupe: search.

unique: and distinct: now behave the same.
The reason for the change is because adding new results doesn't re-apply the unique: or distinct: rules and the results are too confusing.
For example:

distinct:extension

, create a new text document.txt and your end up with two .txt files in your results.

I have on my TODO list to add new results and reapply dupe/distinct/unique rules.

[therube]

adding new results doesn't re-apply the unique: or distinct: rules and the results are too confusing

And I was not confused at all, thinking it was rather obvious what happened.
And, maybe even beneficial, as you see the before & after results, giving you a chance to ponder...