You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This one is interesting. I've been working around it the last few days simply by editing the log file in vim, but imagine it's an unintended consequence of the files having a timezone component.
I flew from Singapore to San Francisco this week and it's been messing up my dailies since I got here. =]
To reproduce:
Create initial log and habits file in time zone like GMT +8
Log some stuff
Fly to GMT -7 (or change your system clock... =p )
You will be prompted for days you have already created as the prompt will note :2019-04-12-07:00: or similar.
However, the next day, it will then ask you for the same information again (and write it).
Seems like a bug. I think the issue here is the timezone being asked for when I believe most people simply consider how they've tracked habits on the "subjective day"
lemme know if this is not clear. I imagine my system will simply fix itself when I fly back to SG< but it does seem like a crossing datelines bug.
ciao!
The text was updated successfully, but these errors were encountered:
Hey there,
This one is interesting. I've been working around it the last few days simply by editing the log file in vim, but imagine it's an unintended consequence of the files having a timezone component.
I flew from Singapore to San Francisco this week and it's been messing up my dailies since I got here. =]
To reproduce:
2019-04-12-07:00:
or similar.However, the next day, it will then ask you for the same information again (and write it).
Seems like a bug. I think the issue here is the timezone being asked for when I believe most people simply consider how they've tracked habits on the "subjective day"
lemme know if this is not clear. I imagine my system will simply fix itself when I fly back to SG< but it does seem like a crossing datelines bug.
ciao!
The text was updated successfully, but these errors were encountered: