search

surrealroad / alfred-reminders

Manages reminders in Reminders.app
MIT License
674 stars 44 forks source link

`tomorrow` giving the same value as `today` #67

Closed vitorgalvao closed 3 years ago

vitorgalvao commented 6 years ago

Recorded at about 00:40 on Tuesday, December 26:

The value for today is correct, but the one for tomorrow is giving today’s result as well.

vitorgalvao commented 6 years ago

Looking further into it, it seems like some weird caching is going on. If I do tomorrow first, then the roles reverse and both today and tomorrow point to tomorrow’s date.

This means that whichever of the two is run first sets the date as the default for both of them. Then after a period it resets and we’re back to “first one wins”.

YanB25 commented 5 years ago

A quick fix to it can be manually delete the three lines in this file. or, open alfred workflow, double click the Script Filter and delete the three lines of code.

I guess here's how this workflow works. If you assign a time in the past, it will automatically plus the day by one. Say, if it's 14:00 now, and you add a reminder and assign 13:00 to it. Since 13:00 < 14:00, this workflow would run day += 1 and set it to "tomorrow 13:00".

And today always point to "today 12:00". So when use r today in the afternoon, this workflow will incorrectly presume that today is in the past, and so today point to tomorrow.

Just manually delete the day += 1 code can fix.

After the code deleted, today always point to TODAY, tomorrow always point to TOMORROW, and all the exact time like r 13:00 will always point to TODAY 13:00. If you want to remind at tomorrow 13:00, just type r tomorrow 13:00.