Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Getting rid of the display the end time in ikhal (which is always starting time +1h) #1381

Open
bjce opened this issue Dec 23, 2024 · 1 comment

Comments

@bjce
Copy link

bjce commented Dec 23, 2024

Hello

I inserted an appointment of the type:

BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//PIMUTILS.ORG//NONSGML khal / icalendar //EN
BEGIN:VTIMEZONE
TZID:Europe/Paris
BEGIN:STANDARD
TZNAME:CET
END:STANDARD
BEGIN:DAYLIGHT
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
SUMMARY:blablbla
DTSTART;TZID=Europe/Paris:20250116T220000
DTSTAMP:20241110T180850Z
UID:999999999999999999999999999999999999
END:VEVENT
END:VCALENDAR

Although there is no endtime, ikhal keeps displaying the end time (corresponding to the starting time +1h). How to get rid of the endtime

@bjce bjce changed the title Hello I inserted an appointment of the type: BEGIN:VCALENDAR VERSION:2.0 PRODID:-//PIMUTILS.ORG//NONSGML khal / icalendar //EN BEGIN:VTIMEZONE TZID:Europe/Paris BEGIN:STANDARD TZNAME:CET END:STANDARD BEGIN:DAYLIGHT END:DAYLIGHT END:VTIMEZONE BEGIN:VEVENT SUMMARY:blablbla DTSTART;TZID=Europe/Paris:20250116T220000 DTSTAMP:20241110T180850Z UID:999999999999999999999999999999999999 END:VEVENT END:VCALENDAR Although there is no endtime, ikhal keeps displaying the end time (corresponding to the starting time +1h). How to get rid of the endtime Getting rid of the display the end time (which is always starting time +1h) Dec 23, 2024
@bjce bjce changed the title Getting rid of the display the end time (which is always starting time +1h) Getting rid of the display the end time in ikhal (which is always starting time +1h) Dec 23, 2024
@WhyNotHugo
Copy link
Member

From https://www.rfc-editor.org/rfc/rfc5545#section-3.6.1:

For cases where a "VEVENT" calendar component specifies a "DTSTART" property
with a DATE-TIME value type but no "DTEND" property, the event ends on the same
calendar date and time of day specified by the "DTSTART" property.

It sounds to me like we should default this case to 0h, not 1h.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants