distinct:/unique: will no longer add new results
dupe: will not add new results.
existing results will be updated in realtime when using dupe:
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.
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...
distinct: unique: dupe:, not updating results is wrong, IMHO.
MUCH prefer the old behavior.
At the least, there should be an .ini to choose.
Current behavior utterly hampers my usages.
---
nope, that is WRONG, IMHO
i would MUCH rather have something unexpected turn up
rather then to have something expected NOT turn up
in 1 window, i renamed a file, knowing that it would
turn up in a different window
in that 2nd window, it was not there, & i'm like, huh?
& i look through Undo, & it shows what i did was what
i expected & so it should be there - but it is not?
& i look through Journal, & it shows what i did was
what i expected & so it should be there - but it is
not?!
& i check my searches, & they look fine too,
& then, after all of that, i'm like, OH, my Filter
includes distinct:, & i think, wasn't there something
about distinct: & so i change to Everything Filter,
& then, like magic, out of the blue, there is the
file that i'd been missing
&... with that, so here we are
not adding results results in far more confusing
then if the results were added - even if that might
(which i can't fathom why) confuse one, momentarily
i can say, oh, i did this, & that is why that happend
that is far different from saying
i did this, & what did happen, where did it go ???
OK, this is absolutely wrong
i use distinct: all the time
i have a window /distinct:/ & i run a command on a file there
& it creates a new file, out.<filename>, & i can no longer see
it cause i have distinct:, so i have to disable/re-enable just
to see, that is wrong.
i'm expecting to see it, i just created it, yet, i cannot find
it, why? it renders anything done in distinct:/unique:,
useless. maybe distinct-lock: for those who want the current
method.
i might have 10 copies of 1000 files, & i am concerned that i
do have them (at all), & not where they might be, so i only
need to /see/ 1,000 file rather then 10,000 files
& when i'm looking to do an action on them, i only need to know
that they are, & when i (especially purposely) create a new file
i (now) no longer know it exists, because distinct: is now
blocking that knowledge from me
& in that respect, totally breaks (my) value of distinct:
what i used to be able to do in 1 tab, i now need to deal
with multiple windows to accomplish (or to regularly jump
back & forth between filters to both be able to see that
i do have & then to filter those results in a more
meaningful manner)
AH !!!
even if you Find <Column> Duplicates, that too locks things.
sorry, that is just so wrong, IMHO, heh.
i dup'd by Length, transcoded a video (so same Length) & when it
was done, i went to compare, but it was nowhere to be seen,
so then i refreshed, which then forced me to
Find <> Duplicates - again, & was on the wrong column,
so then i had to Find <> Duplicates - again, this time on
the correct column, before i got to see my expected file
.)