[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#68653: Excorporate: generate better org timestamps
From: |
Thomas Fitzsimmons |
Subject: |
bug#68653: Excorporate: generate better org timestamps |
Date: |
Mon, 19 Feb 2024 09:07:54 -0500 |
User-agent: |
Gnus/5.13 (Gnus v5.13) |
Hi Ihor,
Ihor Radchenko <yantar92@posteo.net> writes:
> Thomas Fitzsimmons <fitzsim@fitzsim.org> writes:
>
>> Thank you for the patch. From my testing, when org-schedule is passed a
>> start and end date separated by "--", it only includes the start date in
>> the range.
>
> Note that Org mode schedule does not support date ranges.
> It is recommended to use bare active timestamps for scheduling.
> See "Important" note in
> https://orgmode.org/manual/Deadlines-and-Scheduling.html
>
>> Unless I am missing something, an Org date range cannot express an end
>> timestamp on a different day.
>
> Org date range does allow multi-day ranges.
> See https://orgmode.org/manual/Timestamps.html#index-timerange
OK, I was focusing on:
(org-schedule nil "<2024-08-23 Fri>--<2024-08-26 Mon>")
SCHEDULED: <2024-08-23 Fri>
"Scheduled to <2024-08-23 Fri>"
Thank you for clarifying this. I think it is worth preserving the
multi-day behaviour in Excorporate, but Benjamin's patch is a nice
addition for same-day ranges.
I pushed the amended patch, and I am closing this bug report.
The change will go out with Excorporate 1.1.2 sometime today.
Thank you,
Thomas