From: Sagar Shankar <sagar@scubed.in>
To: emacs-orgmode@gnu.org
Subject: Requesting some help with scheduled repeated tasks
Date: Mon, 26 Jan 2015 18:43:15 +0530 [thread overview]
Message-ID: <CAAP45exRXUD6+hUy1=dFd=DgxnR1d9Jkb2Bvtf8OSYma-7qjxA@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1302 bytes --]
Hi all, been using Org-Mode for just over a month now and have stumbled
into something that I cannot still figure out how to implement.
I want to set aside a fixed amount of time each day (say 2 hours) at a
specific time(18-00-20:00 say) to work on a specific task. I want this task
to repeat for 7 days and for state changes (from TODO to DONE) to be
tracked for those 7 days. The latter while ideal, is also optional, as in a
base case, I'd be happy to just get the task automatically marked TODO 7
times in my Agenda till the 7 days are over.
Right now, I've tried using the following syntax:
** TODO Work on XYZ
SCHEDULED: <2015-01-21 Wed 20:30-21:30>-- <2015-01-28 Wed 20:30-21:30>
When I mark this as complete for today, all the other occurrences are also
marked as DONE, which I do not want. Another confusing factor is that
instead of counting 7 occurrences of this task, Org counts it as 8 (which
is another thing I'd love to get explained)
I know tracking repeated tasks is best suited for Org-Habits but I cannot
find anywhere in the documentation for that module, a parameter that allows
me to track habits for only 7 times or 8 times say, and for that habit to
be inserted into the agenda at a specific time only.
Would really appreciate some advice!
Thanks for your time,
Sagar
[-- Attachment #2: Type: text/html, Size: 1551 bytes --]
next reply other threads:[~2015-01-26 13:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-26 13:13 Sagar Shankar [this message]
2015-01-26 13:19 ` Requesting some help with scheduled repeated tasks Christopher Witte
2015-01-27 5:56 ` Sagar Shankar
2015-01-27 6:09 ` Andreas Leha
2015-01-27 10:25 ` Samuel Loury
2015-01-26 15:59 ` Loris Bennett
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='CAAP45exRXUD6+hUy1=dFd=DgxnR1d9Jkb2Bvtf8OSYma-7qjxA@mail.gmail.com' \
--to=sagar@scubed.in \
--cc=emacs-orgmode@gnu.org \
/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.