From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Greg Novak" Subject: Obliterating schedule/deadline repeaters Date: Fri, 13 Jun 2008 17:24:01 -0700 Message-ID: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1K7JYw-0002ER-2u for emacs-orgmode@gnu.org; Fri, 13 Jun 2008 20:24:10 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1K7JYu-0002DE-Tp for emacs-orgmode@gnu.org; Fri, 13 Jun 2008 20:24:09 -0400 Received: from [199.232.76.173] (port=38492 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1K7JYu-0002D2-Jj for emacs-orgmode@gnu.org; Fri, 13 Jun 2008 20:24:08 -0400 Received: from fk-out-0910.google.com ([209.85.128.190]:33182) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1K7JYu-0002rh-8L for emacs-orgmode@gnu.org; Fri, 13 Jun 2008 20:24:08 -0400 Received: by fk-out-0910.google.com with SMTP id 18so2297990fkq.10 for ; Fri, 13 Jun 2008 17:24:02 -0700 (PDT) Content-Disposition: inline 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 On the whole I'm happily using org-mode. One thing that I'm unhappy with is that when I'm looking at the agenda and decide to reschedule a task that has a repeater, the repeater is obliterated. That is, if the task is: * TODO Oil change SCHEDULED <2008-6-1 +3m> and I think to myself "I'll do that on Saturday, not on Tuesday" then hit C-c C-s and put in the new date, the repeater is obliterated. Ideally, the repeater would just be preserved as-is. Almost as good is if there's some clue in the minibuffer that the task has a repeater and I should remember to include it in the new date. As it stands, I have this in my .emacs file to prevent manual changes to tasks with repeaters---in that case I just look at the org file and change the schedule date manually: (defadvice org-schedule (around gsn/org-prevent-rescheduling-repeated-tasks activate) "If the current task has a repeater, prevent rescheduling it to avoid obliterating the repeater." (if (org-get-repeat) (message "*** Can't reschedule this task without obliterating repeater ***") ad-do-it)) I'm writing the list to see if there's a way to do this and I was just dumb when I read the manual. If not, I guess this is a feature request. I'm using v 6.04c. Best, Greg