[Resolved] Inconsistency between dm:5min and dm:short

[aviasd]

Hi,
dm:5min and dm:short return very different results.
dm:5min shows the correct results and dm:short returns results for the whole day...
Am I missing something?

[aviasd]

On that note, would it be possible to add time to the date constants (and have the function comparisons respect them)?
i.e min, hour
It would be easier to query something like all files modified between 5 to 10 minutes ago like so:
dm:>5min dm:<10min

Instead of
dm:>=14:05 dm:<=14:10

Or even
dm:5min..10min
instead of
dm:=14:05..14:10

[NotNull]

It would be easier to query something like all files modified between 5 to 10 minutes ago like so:
dm:>5min dm:<10min

Does this work for you?

Code: Select all

dm:5m..10m

[aviasd]

It would be easier to query something like all files modified between 5 to 10 minutes ago like so:
dm:>5min dm:<10min

Does this work for you?

Code: Select all

dm:5m..10m

Actually it does!
I'm sure I've tested it at some point...Guess I didn't...
Thx

[void]

dm:5min matches 5 mins ago or later.

dm:short confuses Everything, short is not a known keyword for dates.
Everything ignores shor and the t causes Everything to match time, in this case time is not defined so the current day is matched.

Date Syntax:

• year
• month/year or year/month depending on locale settings
• day/month/year, month/day/year or year/month/day depending on locale settings
• YYYY[-MM[-DD[Thh[:mm[:ss[.sss]]]]]]
• YYYYMM[DD[Thh[mm[ss[.sss]]]]]

Date Constants:

• today
• yesterday
• <last|current|this|coming|next><year|month|week>
• <last|coming|next><x><years|months|weeks|days|hours|minutes|mins|seconds|secs>
• past[ x ]<year[ s ]|month[ s ]|week[ s ]|day[ s ]|hour[ s ]|minute[ s ]|min[ s ]|second[ s ]|sec[ s ]>
• <prev|previous>[ x ]<year[ s ]|month[ s ]|week[ s ]>
• [ x ]<year[ s ]|month[ s ]|week[ s ]|day[ s ]|hour[ s ]|minute[ s ]|min[ s ]|second[ s ]|sec[ s ]>
• january|february|march|april|may|june|july|august|september|october|november|december
• jan|feb|mar|apr|may|jun|jul|aug|sep|oct|nov|dec
• sunday|monday|tuesday|wednesday|thursday|friday|saturday
• sun|mon|tue|wed|thu|fri|sat
• mtd|ytd
• unknown

I have added support for dm:>5min dm:<10min and dm:5min..10min for the next alpha update.

Currently, Everything will see dm:>5min as
dm:>(5 minutes ago or later)
This will actually look for a date after or later, which will never match anything.

Currently, Everything will see dm:5min..10min as
dm:(5 minutes ago until now)..(10 minutes ago until now)
which is treated as 10 minutes ago until now.

Try the following search:
!dm:5mins dm:10mins
This will match files modified 10 minutes ago or later, but not files modified 5 minutes ago or later.

[aviasd]

Actually it does!

Well, it doesn't, void's response is the correct solution.
Too quick to type for my own good..

I'll look into support for dm:>5min dm:<10min

Cool

Currently, Everything will see dm:>5min as
dm:>(5 minutes ago or later)
This will actually look for a date after or later, which will never match anything.

Currently, Everything will see dm:5min..10min as
dm:(5 minutes ago until now)..(10 minutes ago until now)
which is treated as 10 minutes ago until now.

I guess it's a source for some confusion, a user might expect 5min to mean just 5 minutes, not until now. I.e a point in time , not a range...
Maybe it should be specified in the help...

Try the following search:
!dm:5mins dm:10mins
This will match files modified 10 minutes ago or later, but not files modified 5 minutes ago or later.

Yep, this one works, Thankx

The search syntax in the help does not specify the usage of duration.. it's specified right before the date search syntax so I assumed it relates to dates...
In the help, under functions: the: name:<param> spec, there's no example for duration..

[void]

Duration syntax is for properties like Length: not dates, eg: length:short

However, I will add support for duration to dates, eg: dm:short

Function syntax and examples are still in development.

Thanks for the feedback!

[void]

Everything 1.5.0.1252 fixes the issue with using operators on 5mins.

dm:5mins..10mins should work as expected now.
dm:>5mins should work as expected now (read as greater than 5 mins ago)

I've also added support for duration constants.
For example:
dm:short
dm:medium

[aviasd]

Everything 1.5.0.1252 fixes the issue with using operators on 5mins.

dm:5mins..10mins should work as expected now.
dm:>5mins should work as expected now (read as greater than 5 mins ago)

I've also added support for duration constants.
For example:
dm:short
dm:medium

Confirmed!
constant ranges do not though.. But that's cool.

If only MS, with their 50k developers, would be as attentive and quick.

Just a note though
dm:>5m gives all the files from now until 5 minutes ago.

in My sense, the query:
dm:>5min = Give me all the files where their modified date is greater than 5 minutes
dm:<5min = Give me all the files where their modified date is lesser than 5 minutes.

So the logic is reversed.(In my mind)
How should the query be read?
dm:>5min = Give me all the files where their modified date is greater than ???? ( 5minutes ago until now ?? - doesn't make sense..)

[void]

constant ranges do not though.. But that's cool.

What happens? dm:very-short, dm:short, dm:medium, dm:long and dm:very-long appear to work ok here.
Remember these expand to a range, eg: dm:short becomes dm:1min..5min (this does not include files modified in the last 1 minute)

So the logic is reversed.(In my mind)
How should the query be read?

When using an operator with dm: (eg: > >= < <= = == !=), Everything will treat the value as exact.
This is true for all search functions, such as size:.

Read:
dm:>5min
as:
dm: a date greater than (exactly 5 minutes ago)


Read:
dm:<5min
as:
dm: a date less than (exactly 5 minutes ago)



Read:
dm:5min..10min
as:
dm: a date between (exactly 5 minutes ago) and (exactly 10 minutes ago)

[aviasd]

constant ranges do not though.. But that's cool.

What happens? dm:very-short, dm:short, dm:medium, dm:long appear, dm:very-long to work ok here.
Remember these expand to a range, eg: dm:short becomes dm:1min..5min (this does not include files modified in the last 1 minute)

My mistake, I was treating ranges as points in time, dm:short..medium - Too early in the morning here..

When using an operator with dm: (eg: > >= < <= = == !=), Everything will treat the value as exact.
This is true for all search functions, such as size:.

Read:
dm:>5min
as:
dm: a date greater than (exactly 5 minutes ago)


Read:
dm:<5min
as:
dm: a date less than (exactly 5 minutes ago)



Read:
dm:5min..10min
as:
dm: a date between (exactly 5 minutes ago) and (exactly 10 minutes ago)

I see. Now it makes sense
I was reading as:
dm:>5min = a date greater than (exactly) 5 minutes and backwards,

You intended it to work as:
Date greater than (exactly) 5 minute and forwards until now.
(
I still think thuogh
dm:>5m dm:<10m
Is clearer than
dm:>10m dm:<5m
)
Different POVs

Another note:
dm:>10m dm:<5m
gives the intended results, but, if I switch the order of the functions:
dm:<5m dm:>10m
I get wrong results (Dunno if it's a bug)

[void]

Thank you for the feedback aviasd,

dm:<5m dm:>10m
I get wrong results (Dunno if it's a bug)

It's a group expansion bug with <5m dm:>10m
I'll work on a fix..

[reitwal]

I tested the following:
dm:5m..10m ok
dm:5h..10h ok
dm:5d..10d ok
dm:5w..10w ok
dm:5month..10month wrong results
dm:5year..10year wrong results

Everything 1.5.0.1252

[void]

Thank you for the bug report reitwal,

Everything is modifying the current date when parsing multiple month values. I will work on a fix.

[NotNull]

Now I think of it, this should be written as:

dm:10m..5m

. From low to high: 10 minutes ago (17:47) to 5 minutes ago (17:52)
For the record: that gives the same results as

dm:5m..10m

[void]

Everything 1.5.0.1253a fixes an issue with dm: using the wrong month or year.

Everything 1.5.0.1253a fixes an issue with group expansion.

Everything was expanding dm:<5m dm:>10m to: dm:5m10m dm:dm:10m
Everything 1.5.0.1253a will no longer expand functions inside <> and space is no longer a valid group expansion operator (only | is accepted now).

Now I think of it, this should be written as:
dm:10m..5m
. From low to high: 10 minutes ago (17:47) to 5 minutes ago (17:52)

The order doesn't matter.
When you use an operator with dm:, values are treated as exact (instead of as a range)
.. is an operator.

Read dm:10m..5m as:
date modified between 10-minutes-ago and 5-minutes-ago

[aviasd]

Everything 1.5.0.1253a fixes an issue with group expansion.
Everything 1.5.0.1253a will no longer expand functions inside <> and space is no longer a valid group expansion operator (only | is accepted now).

Confirmed

Read dm:10m..5m as:
date modified between 10-minutes-ago and 5-minutes-ago

dm:10m..5m is now working the same as dm:<=5m dm:>=10m
Note: Results do not update automatically - There's a need to retype query/<backspace char><char> (Refresh does not refresh results)

[void]

Note: Results do not update automatically - There's a need to retype query/<backspace char><char> (Refresh does not refresh results)

Everything will only track new and modified files/folders when using a relative date/time search.

I will consider an option to re-search every 1 minute when using a relative date/time in your query.
Thanks for the suggestion.

There's a need to retype query/<backspace char><char> (Refresh does not refresh results)

I usually add a space to the end of the query.