From: Bernt Hansen <bernt@norang.ca>
To: "François Pinard" <pinard@iro.umontreal.ca>
Cc: emacs-orgmode@gnu.org
Subject: Re: Double SCHEDULED: problem
Date: Fri, 02 Mar 2012 12:13:43 -0500 [thread overview]
Message-ID: <87boofhqns.fsf@norang.ca> (raw)
In-Reply-To: <87pqcvrm9r.fsf@iro.umontreal.ca> ("François Pinard"'s message of "Fri, 02 Mar 2012 11:38:24 -0500")
pinard@iro.umontreal.ca (François Pinard) writes:
> Hi, Org friends!
>
> For my employer, I have to fill a "time form" every two weeks for
> salary, and also every month for customer billing. So, I have one
> SCHEDULED: line for each of these recurrences. Last week, the entry
> started like this:
>
>
> ** TODO *Rapport d'heures (Formation) :projet:
> SCHEDULED: <2012-02-27 lun ++2w>
> SCHEDULED: <2012-03-01 dim ++1m>
>
>
> Last Monday, turning the entry to DONE produced the following:
>
>
> ** TODO *Rapport d'heures (Formation) :projet:
> SCHEDULED: <2012-03-12 lun ++2w>
> SCHEDULED: <2012-04-01 dim ++1m>
>
>
> That is, *both* SCHEDULED: lines were advanced, and so, I missed to be
> remembered to do my little filling duty yesterday, which has not been a
> problem because others and I also received an email to that effect.
>
> I wonder if or how Org could have helped me better. I would prefer
> keeping a single entry, because there many lines of contents ( the
> recipe details about how to fill the company form, clocktables,
> logbooks, and such things), which I would not like duplicated.
>
Two SCHEDULED: lines on a single entry is not supported by org-mode
AFAIK. I would create a subtask for each of these
<untested>
* TODO Parent task with the details
All your notes and procedures go here
** TODO Subtask 1
SCHEDULED: <2012-03-12 lun ++2w>
** TODO subtask 2
<2012-04-01 dim ++1m>
HTH,
Bernt
next prev parent reply other threads:[~2012-03-02 17:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-02 16:38 Double SCHEDULED: problem François Pinard
2012-03-02 17:13 ` Bernt Hansen [this message]
2012-03-02 18:28 ` François Pinard
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=87boofhqns.fsf@norang.ca \
--to=bernt@norang.ca \
--cc=emacs-orgmode@gnu.org \
--cc=pinard@iro.umontreal.ca \
/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).