emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Rick Hanson <cryptorick@gmail.com>
To: Darlan Cavalcante Moreira <darcamo@gmail.com>,
	Brian van den Broek <brian.van.den.broek@gmail.com>
Cc: Org-mode Mailing List <emacs-orgmode@gnu.org>
Subject: Re: Repeated tasks, but only for a limited period (of time)
Date: Tue, 12 Mar 2013 15:54:32 -0400	[thread overview]
Message-ID: <CAC10T-mM0MdX8DkaRKs9DTDNSkLvTaYRrwrnLqkYRzH+0uN2EQ@mail.gmail.com> (raw)
In-Reply-To: <513f5f6e.02b6ec0a.69dd.ffff8157@mx.google.com>

Based your advices, I used org-clone-subtree-with-time-shift for my
application today -- worked like a charm.  Thanks to the both of you!

Best, --Rick

On Tue, Mar 12, 2013 at 12:58 PM, Brian van den Broek
<brian.van.den.broek@gmail.com> wrote:
> Hi Rick,
> I know of no way to do exactly what you are after. But, for things
> like that, I make one headline task and then apply M-x
> org-clone-subtree-with-time-shift to get the desired number of
> distinct tasks. Perhaps that will suit your needs.
> Best,
> Brian vdB

On Tue, Mar 12, 2013 at 1:01 PM, Darlan Cavalcante Moreira
<darcamo@gmail.com> wrote:
> Instead of using a repeater you can clone the task. Just create the task
> the way you like it (with a schedule and a deadline) for the first day and
> then call 'M-x org-clone-subtree-with-time-shift'.  Org-mode will ask you
> the number of clones it should create and the time shift. Just specify the
> time shift as '1d' and you are done.
> --
> Darlan
> At Tue, 12 Mar 2013 11:06:30 -0400,
> Rick Hanson wrote:
>> [1  <text/plain; ISO-8859-1 (7bit)>]
>> Hi everyone,
>> I've already RTFMed for this, but I still don't see how to do the following.
>> Fact: I can add a repeater to a time stamp (like "+1d") in org-mode so that
>> a task shows up in my agenda as an every day item.
>> Question: Can I restrict this repetition to, say, 1 week?
>> For instance, I have a task I have to perform every day this week, /but
>> only for this week/.  So if I were to pull up my agenda for this week, I
>> should see the task posted every day of this week, but if I then hit the
>> "f" key to go forward a week, I should *not* see that task in this (the
>> following) week.
>> This is a not deal-breaker if not possible.  I can just get rid if the task
>> at the end of the week (but it's state, of course, that I have to keep in
>> my mind, instead of committing it to the magic of org-mode).
>> Thanks a lot of any help!  (My apologies if it's in the manual and I missed
>> it.)
>> Best, --Rick
>> [2  <text/html; ISO-8859-1 (quoted-printable)>]

  reply	other threads:[~2013-03-12 21:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-12 15:06 Repeated tasks, but only for a limited period (of time) Rick Hanson
2013-03-12 16:58 ` Brian van den Broek
2013-03-12 17:01 ` Darlan Cavalcante Moreira
2013-03-12 19:54   ` Rick Hanson [this message]
2013-03-13  8:59     ` Bastien
2013-03-13 14:42       ` Rick Hanson

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=CAC10T-mM0MdX8DkaRKs9DTDNSkLvTaYRrwrnLqkYRzH+0uN2EQ@mail.gmail.com \
    --to=cryptorick@gmail.com \
    --cc=brian.van.den.broek@gmail.com \
    --cc=darcamo@gmail.com \
    --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).