From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michael Brand Subject: Re: Still Wishing for Snooze Date: Tue, 12 Feb 2013 19:09:03 +0100 Message-ID: References: <50FD86D4.8080105@up.edu> <877gn410o4.fsf@bzg.ath.cx> <51018250.2050404@up.edu> <878v7i2p6k.fsf@bzg.ath.cx> <5101BB9A.5000505@up.edu> <87sj5py20d.fsf@bzg.ath.cx> <5102E176.3070005@up.edu> <871ucs1mr4.fsf@bzg.ath.cx> <878v6tltna.fsf@bzg.ath.cx> <87621xija1.fsf@bzg.ath.cx> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Return-path: Received: from eggs.gnu.org ([208.118.235.92]:59018) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1U5KI4-0006Cq-D0 for emacs-orgmode@gnu.org; Tue, 12 Feb 2013 13:09:13 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1U5KHw-00016j-Nm for emacs-orgmode@gnu.org; Tue, 12 Feb 2013 13:09:12 -0500 Received: from mail-lb0-f171.google.com ([209.85.217.171]:63554) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1U5KHw-00016Q-Ei for emacs-orgmode@gnu.org; Tue, 12 Feb 2013 13:09:04 -0500 Received: by mail-lb0-f171.google.com with SMTP id gg13so328348lbb.30 for ; Tue, 12 Feb 2013 10:09:03 -0800 (PST) In-Reply-To: <87621xija1.fsf@bzg.ath.cx> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Bastien Cc: "Andrew M. Nuxoll" , Org Mode Hi Bastien On Tue, Feb 12, 2013 at 5:33 PM, Bastien wrote: > This should be fixed now. Thanks for the clear example and the > testing. Thank you for fixing the bugs and mainly for the --2d delay for repeated SCHEDULED. To summarize my point of view of this thread: Originally I wanted to use such a delay primarily for repeated DEADLINE. But as I had to realize, to me such a delay seems not simple enough to use with warning periods other than -0d. Maybe I will adapt my usage of SCHEDULED a bit so that I can use repeated SCHEDULED with the new --2d delay, instead of my current not delayable repeated DEADLINE with -0d. Michael