dupe:dm, tolerance ?

[therube]

dupe:dm

must take "seconds" into consideration
- is there a tolerance or exclusion setting ?


(in my case, i only cared about mm/dd/yy
as in i wanted to see all mm/dd/yy colored the same [& seconds, milliseconds throws that off])

[NotNull]

Add this to your search query:

Code: Select all

column1:=FORMAT_FILETIME($date-modified:,YYYYMMDD) add-column:column1

And work on Column 1.


(can't help you with dupes and colour grouping )

[therube]

"40510101" - what's up with that ?!.

(Heh. Yes, 01-01-4051 is a kind of magic date.
It has the propensity to cause some programs to crash.
So I keep files with that date on hand, just in case .)


Not very convenient nor efficient, but.

It's not that a big deal (that the work-around is actually not as good), but in general, I'd think that someone sorting by "date", may want to see same "dates", days, grouped (colored) together (in a logical sense).


As it is I might not have ever done a dupe:dm particularly. Instead, used dupe:sha1 (which I'd indexed for particular data).
& then, simply sorted by the Date column (& so never ran across the issue before). But then, I had the "smart" idea to see what dupe:dm might do (however differently). [I found out .]

[NotNull]

There might be other solutions, but this is the one that came to my (admitted: twisted) mind.

[void]

dupe:dm takes the full 100-nanoseconds into consideration.

Please consider the "Day Modified" property.

To show the Day Modified column:

• In Everything, right click the result list column header and click Add columns....
• Search for:
  day
• select day Day Modified and click OK.

To find duplicate day modified values:

• Right click the Day Modified column header and click Find Day Modified Duplicates.

-or-

Search for:

dupe:day-modified

Gathering the day modified value can take a few minutes.