From: Thomas Fitzsimmons <fitzsim@fitzsim.org>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: Benjamin Leis <benleis1@gmail.com>, 68653-done@debbugs.gnu.org
Subject: bug#68653: Excorporate: generate better org timestamps
Date: Mon, 19 Feb 2024 09:07:54 -0500 [thread overview]
Message-ID: <m3le7gsg1x.fsf@fitzsim.org> (raw)
In-Reply-To: <87o7ccg0g5.fsf@localhost> (Ihor Radchenko's message of "Mon, 19 Feb 2024 11:25:46 +0000")
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
prev parent reply other threads:[~2024-02-19 14:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-21 19:52 bug#68653: Excorporate: generate better org timestamps Benjamin Leis
2024-02-15 3:38 ` Thomas Fitzsimmons
2024-02-19 11:25 ` Ihor Radchenko
2024-02-19 14:07 ` Thomas Fitzsimmons [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3le7gsg1x.fsf@fitzsim.org \
--to=fitzsim@fitzsim.org \
--cc=68653-done@debbugs.gnu.org \
--cc=benleis1@gmail.com \
--cc=yantar92@posteo.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.