emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Alexander Baier <lexi.baier@gmail.com>
To: Marvin Doyley <m.doyley@rochester.edu>
Cc: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: Repeating tasks
Date: Mon, 29 Apr 2013 21:56:16 +0200	[thread overview]
Message-ID: <87y5c16rhb.fsf@gmail.com> (raw)
In-Reply-To: <40C61C35-A581-4222-87B9-F567DB76D5CD@rochester.edu> (Marvin Doyley's message of "Mon, 29 Apr 2013 15:20:57 -0400")

Hi Marvin,

Marvin Doyley <m.doyley@rochester.edu> writes:
> org-habit is not what I am looking for.
> I would like to do something like
> * TODO write proposal
> Scheduled:<2013-04-30 Tue 13:00-15:00 >--<2013-06-02 Mon> +2d
> The idea is to repeat this task every other day from 2013-04-30 to 2013-06-02 (from 13:30 to 15:00)
> cheers
> M

Ok, then I think diary sexp should do the trick.  Try the following:

** TODO 13:00-15:00 write proposal
<%%(and (org-block 2013 4 30 2013 6 2) (org-cyclic 2 2013 4 30))>


  reply	other threads:[~2013-04-29 19:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-29 19:20 Repeating tasks Marvin Doyley
2013-04-29 19:56 ` Alexander Baier [this message]
2013-04-29 22:20   ` Marvin Doyley
  -- strict thread matches above, loose matches on Subject: below --
2013-04-29 13:45 Marvin Doyley
2013-04-29 16:51 ` Alexander Baier

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=87y5c16rhb.fsf@gmail.com \
    --to=lexi.baier@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=m.doyley@rochester.edu \


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