From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Eric Abrahamsen <eric@ericabrahamsen.net>
Cc: emacs-orgmode@gnu.org
Subject: Re: Easy entry of date ranges
Date: Thu, 27 Aug 2015 10:15:16 +0200 [thread overview]
Message-ID: <87vbc1jgff.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <87io815r7r.fsf@ericabrahamsen.net> (Eric Abrahamsen's message of "Thu, 27 Aug 2015 11:46:00 +0800")
Eric Abrahamsen <eric@ericabrahamsen.net> writes:
> Ken Mankoff <mankoff@gmail.com> writes:
>
>> No, scheduled + deadline is a different use case. The syntax I use,
>> =SCHEDULED: <2020-01-01>--<2020-01-07>=, is valid,
I wouldn't bet on it. I'm sure this can lead to subtle problems. For
example,
* Test
SCHEDULED: <2020-01-01>--<2020-01-07>
(org-entry-get (point-min) "SCHEDULED") => <2020-01-01>, i.e, range end
information is lost.
>>. One (of many) use cases: a week long vacation.
>> This use case is supported by Org since the Agenda helpfully shows
>> "(1/7)", and "(2/7)", etc. before each entry. Everything else is so
>> efficient and has shortcuts, including time ranges, I just hoped I was
>> missing something here. Perhaps it hasn't been implemented yet.
>
> I think what Nicolas means is that, in the sort of use case you're
> outlining above, you should probably be using a plain timestamp.
> SCHEDULED means "I'm going to work on this TODO now", in which case
> a time span doesn't quite make sense -- you start working at the start
> of the span, and you finish when you toggle the keyword to DONE. For
> a vacation, a plain timestamp is more appropriate.
Exactly.
If you know the exact range, use a plain timestamp. SCHEDULED is for
when you know when to start, but not when to end. With
SCHEDULED + DEADLINE, you know when to start, you're not sure when to
end, but it must be done before deadline.
Regards,
next prev parent reply other threads:[~2015-08-27 8:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-26 17:35 Easy entry of date ranges Ken Mankoff
2015-08-26 19:04 ` Nicolas Goaziou
2015-08-26 20:38 ` Ken Mankoff
2015-08-27 3:46 ` Eric Abrahamsen
2015-08-27 8:15 ` Nicolas Goaziou [this message]
2015-08-27 9:36 ` Eric S Fraga
2015-08-27 9:52 ` Rasmus
2015-08-27 11:22 ` Ken Mankoff
2015-08-27 15:33 ` Eric Abrahamsen
2015-08-27 16:14 ` Eric S Fraga
2015-08-27 17:46 ` Miguel Ruiz
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
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87vbc1jgff.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=emacs-orgmode@gnu.org \
--cc=eric@ericabrahamsen.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 public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).