From mboxrd@z Thu Jan 1 00:00:00 1970 From: Memnon Anon Subject: Re: Question about end date for a scheduled task Date: Tue, 5 Jan 2010 15:01:02 +0000 (UTC) Message-ID: <87pr5otx42.fsf@mean.albasani.net> References: <6d0ff11001040723n69d844depead00d5d4959ff62@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NSAui-0005A3-W9 for emacs-orgmode@gnu.org; Tue, 05 Jan 2010 10:01:41 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NSAue-00059D-5z for emacs-orgmode@gnu.org; Tue, 05 Jan 2010 10:01:40 -0500 Received: from [199.232.76.173] (port=41704 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NSAue-00059A-2I for emacs-orgmode@gnu.org; Tue, 05 Jan 2010 10:01:36 -0500 Received: from lo.gmane.org ([80.91.229.12]:49918) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1NSAud-0000x1-L0 for emacs-orgmode@gnu.org; Tue, 05 Jan 2010 10:01:35 -0500 Received: from list by lo.gmane.org with local (Exim 4.50) id 1NSAuV-0008FA-3k for emacs-orgmode@gnu.org; Tue, 05 Jan 2010 16:01:27 +0100 Received: from e178230251.adsl.alicedsl.de ([85.178.230.251]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 05 Jan 2010 16:01:27 +0100 Received: from gegendosenfleisch by e178230251.adsl.alicedsl.de with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 05 Jan 2010 16:01:27 +0100 List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: emacs-orgmode@gnu.org Avinash Kulkarni writes: > Hi, Is there a way to specify when a particular task should stop > repeating? For instance, I need to backup the server in my office once > a week for the next 3 weeks, after which the employee in charge will > take it over again. Right now, I just added it as a C-x C-s +1w > scheduled task, but this causes it to show up on my agenda even after > the third week. Is archiving this task the only option? For a task only repeated 3 times, I settled on giving each instance a separate entry. If it is a complex item with several subitems, the command org-clone-subtree-with-time-shift command helps a lot. ,----[ (info "(org)Structure editing") ] | `C-c C-x c' | Clone a subtree by making a number of sibling copies of it. You | will be prompted for the number of copies to make, and you can | also specify if any timestamps in the entry should be shifted. | This can be useful, for example, to create a number of tasks | related to a series of lectures to prepare. For more details, see | the docstring of the command `org-clone-subtree-with-time-shift'. `---- hth