emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Andreas Leha <andreas.leha@med.uni-goettingen.de>
To: emacs-orgmode@gnu.org
Subject: Re: Requesting some help with scheduled repeated tasks
Date: Tue, 27 Jan 2015 06:09:14 +0000	[thread overview]
Message-ID: <olu4mrc21rp.fsf@med.uni-goettingen.de> (raw)
In-Reply-To: CAAP45ez=CF1Rg=ztrdg_TdtOYKovLT1tj1q-YuL-vp4VAzqHSQ@mail.gmail.com

Hi Sagar,

Sagar Shankar <sagar@scubed.in> writes:
> Thanks Christopher, the latter option seems to accomplish what I
> require though not very elegant

I though so first, too.  But by now I came to like that approach a lot.
It provides so much flexibility with the individual instances (like
moving, keeping notes, cancellation, etc.).

Give it some time and maybe you'll like it in the end ;-)


> With Regards,
> Sagar
> On Mon, Jan 26, 2015 at 6:49 PM, Christopher Witte
> <chris@witte.net.au> wrote:
>     Hi Sagar,
>     I think you either want a repeating task see
>     http://orgmode.org/manual/Repeated-tasks.html
>     or to use org-clone-subtree-with-time-shift see
>     http://orgmode.org/manual/Structure-editing.html#Structure-editing
>     I think repeated tasks repeat for ever, so from your description
>     org-clone-subtree-with-time-shift might be better.
>     I hope that helps,
>     Chris.
>     On 26 January 2015 at 14:13, Sagar Shankar <sagar@scubed.in>
>     wrote:
>         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

  reply	other threads:[~2015-01-27  6:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-26 13:13 Requesting some help with scheduled repeated tasks Sagar Shankar
2015-01-26 13:19 ` Christopher Witte
2015-01-27  5:56   ` Sagar Shankar
2015-01-27  6:09     ` Andreas Leha [this message]
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:

  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=olu4mrc21rp.fsf@med.uni-goettingen.de \
    --to=andreas.leha@med.uni-goettingen.de \
    --cc=emacs-orgmode@gnu.org \


* 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


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).