Open ahillio opened 2 years ago
I wondered if a problem in my config file was causing this so I created a new one using khal configure
to test it. The problem still occurs.
Does the event have a timezone? Does it match your local timezone?
Is this one a full-day-event, or a one hour event too?
Thanks for the response! I think the event has a correct timezone. It's not full day, just one hour...
BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//PIMUTILS.ORG//NONSGML khal / icalendar //EN
BEGIN:VTIMEZONE
TZID:America/New_York
BEGIN:DAYLIGHT
DTSTART;VALUE=DATE-TIME:20220313T030000
TZNAME:EDT
TZOFFSETFROM:-0500
TZOFFSETTO:-0400
END:DAYLIGHT
BEGIN:STANDARD
DTSTART;VALUE=DATE-TIME:20221106T010000
TZNAME:EST
TZOFFSETFROM:-0400
TZOFFSETTO:-0500
END:STANDARD
END:VTIMEZONE
BEGIN:VEVENT
SUMMARY:therapy
DTSTART;TZID=America/New_York;VALUE=DATE-TIME:20220830T103000
DTEND;TZID=America/New_York;VALUE=DATE-TIME:20220830T113000
DTSTAMP;VALUE=DATE-TIME:20220829T104829Z
UID:7KKL2O9W65WLPJ0K8481YV7PDMJZL4Y2767P
SEQUENCE:0
CATEGORIES:
END:VEVENT
END:VCALENDAR
I'm in the same timezone as America/NewYork.
That data is from an event that ended earlier today.
khal list --notsarted
lists that event right now, though it should not.
I was using khal-0.10.2 and just upgraded to 0.10.4 (on Ubuntu 20.04) and this problem persists.
khal list --notstarted
shows events that already happened today, a 1-hour event that started and ended this morning (and it's evening now) appears at the top of the list.