Dāvis

It's DST related, currently Chronic almost always breaks on DST change... There are dozens of similar bugs, it will be fixed some day.

Chronic doesn't really support such complex queries and mostly it's luck based whether it will get it correct :D anyway this works fine in my `rewrite` branch, but it's nowhere...

with "works fine in my rewrite branch" I mean, it works there as it should producing correct output - feature already implemented there :)

I'm not sure what you mean? It looks correct to me. ``` ruby # by default, :context => :future and :hours24 => nil # which means it will take best...

I already mentioned `by default, :context => :future and :hours24 => nil` so you just pass `:hours24 => true` ;)

yeah I think this can be used, what do you @leejarvis think? also might as well merge `beta` branch in master and release it as [there are some fixes](/mojombo/chronic/compare/beta) and...

Don't worry about fixing, there's ongoing rewrite of large part of Chronic and I know how big mess current code is. Also actually this is fixed in my rewrite branch...

It's a known bug #230, #272 and it's fixed on `master` (with #243) but haven't released yet.

I've been thinking about such feature for next version as I also find this needed and useful, but I haven't decided yet about best implementation.

I don't recommend working much on current `master` branch because those changes will have to be reworked for next version, I've `rewrite` branch in progress, see #278 and definitions are...