void wrote: ↑Sun Nov 21, 2021 12:34 am
dupe: will find files with the same name
anywhere in the index. (not the current results)
Hi Void, this is an old post, but I read all the "dupe" posts this morning and my question seem relevant here.
Win7 Everything
1.5.0.1333a(x64)
- Dupe07.png (64.62 KiB) Viewed 7404 times
From your comment it sounds as if Everything considers a basic dupe: to be
an identical name in the filename index.
Hence I see two versions of "Liszt- Years of Pilgrimage".
But my filter asks that size: be taken into account.
But it seems as if Everything says "No, 'Liszt- Years of Pilgrimage' has already joined the club as a duplicate by name, so there is no need to check date, size, and so on".
Everything lists the first track as 74,187Kb but right-click Properties in Explorer says 76,021,760 bytes on disk, duration 1:19:07
Everything lists the next track as 73,956Kb but right-click Properties in Explorer says 75,759,616 bytes on disk, duration 1:18:53
A definition of "duplicate" is open to argument; I have my own intense definition, but here I am more interested in how Everything defines a duplicate.
I note too that the result list seems always to come back in Name sequence ascending, even when Name is not specified by the user.
(1) Is name always factored in when dupe: is used?
(2) If not, how would I tell Everything to disregard name?
(3) Does the sequence of functions presented in the filter (Size: Dupe:, Name: etc) make any difference to execution?
the rube has mentioned Content: but I don't want to go there yet,
(signed) "Struggling but making progress" of Bonavista.