> <2024-02-22 18:30-20:00> is a valid timestamp. Agenda not handling it is > an oversight that should be fixed.
Thanks for checking this. If the agenda could parse these, great. However, with a workaround (C-c C-c on the timestamp), I can handle this for now. Incidentally, org-lint says the following: 4422 low Potentially malformed timestamp <2024-02-22 18:30-20:00>. Parsed as: <2024-02-22 Thu 18:30-20:00> which helped me catch a few other timestamps. Best wishes, Stephen
