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
Noted when using davmail as a backend.
May apply to other servers.
When adding a full-day event with this syntax 2023-09-07+1d the server does not interpret the request as a full-day event and instead adds a 24-hour event with a timestamp that starts at the last second of the PREVIOUS day.
It does not appear that calendar-cli has any other syntax for adding a full-day event (though I believe plann does). If I am misreading, please let me know.
The text was updated successfully, but these errors were encountered:
The if clause in calendar-cli sees a whole-day event whether the --whole-day option is passed OR the total duration is a multiple of 24 hours.
An event with a +1d time span (whether or not --whole-day is passed at the command line) sent to davmail produces a 24-hour-long event rather than a whole day event.
Other caldav clients can correctly generate a whole-day event in davmail.
EDIT: Thank you for the heads-up, @tobixen. I did miss the fact that the --whole-day option exists. Unfortunately, it does not change the outcome.
Noted when using davmail as a backend.
May apply to other servers.
When adding a full-day event with this syntax
2023-09-07+1d
the server does not interpret the request as a full-day event and instead adds a 24-hour event with a timestamp that starts at the last second of the PREVIOUS day.It does not appear that
calendar-cli
has any other syntax for adding a full-day event (though I believeplann
does). If I am misreading, please let me know.The text was updated successfully, but these errors were encountered: