From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bastien Subject: Re: Still Wishing for Snooze Date: Tue, 12 Feb 2013 11:21:29 +0100 Message-ID: <878v6tltna.fsf@bzg.ath.cx> 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> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Return-path: Received: from eggs.gnu.org ([208.118.235.92]:43800) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1U5Czi-0001ri-0K for emacs-orgmode@gnu.org; Tue, 12 Feb 2013 05:21:50 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1U5CzX-0005Md-Rh for emacs-orgmode@gnu.org; Tue, 12 Feb 2013 05:21:45 -0500 Received: from mail-we0-x234.google.com ([2a00:1450:400c:c03::234]:38487) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1U5CzX-0005MT-KI for emacs-orgmode@gnu.org; Tue, 12 Feb 2013 05:21:35 -0500 Received: by mail-we0-f180.google.com with SMTP id k14so5530818wer.11 for ; Tue, 12 Feb 2013 02:21:34 -0800 (PST) In-Reply-To: (Michael Brand's message of "Thu, 7 Feb 2013 16:25:43 +0100") 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: Michael Brand Cc: "Andrew M. Nuxoll" , Org Mode Hi Michael, Michael Brand writes: >> SCHEDULED: <2013-02-07 jeu. -2d> >> >> The item will not be shown today, but in three days. > > For this case I would use: > > SCHEDULED: <2013-02-09 Sat> AFAIU this would not work for what Andrew wants. He wants the scheduled item to be invisible on the 2013-02-07 but to appear on the 2013-02-07 as it is was scheduled on 2013-02-09. My change does this. > It seems I don’t get the point because when a TODO with repeater > > SCHEDULED: <2013-02-01 Fri +1w -3d> > > is set to DONE the delay remains and this way also here I would not > use a delay but: > > SCHEDULED: <2013-02-04 Mon +1w> > > The usefulness of a SCHEDULED delay I see together with a TODO and > repeater to implement an _exception_ (to simplify: exception just for > the first date, before the repetitions). For example > > SCHEDULED: <2013-02-01 Fri +1w -3d> > > would mean: Usually start working on the entry earliest on the first > day of the month except [2013-02-01 Fri] when work can not start > before [2013-02-04 Mon]. It would start to show in the agenda on > [2013-02-04 Mon], [2013-03-01 Fri], [2013-04-01 Mon], [2013-05-01 > Wed], [2013-06-01 Sat] etc. On let’s say [2013-02-05 Tue] it would be > set to DONE and would change to: > > SCHEDULED: <2013-03-01 Fri +1w> > > Note the automatically removed delay. Point well taken -- this is now what adding "--2d" does: use a temporary delay that will not be taken into account for dates later than the next repeater, and that will be deleted when a repeating task is marked as done. Thanks for suggesting this. I think it still makes sense to keep the default behavior: -1d in a scheduled items means "inconditionnally add a delay of one day, even when there is a repeater" -- because perhaps what users want is a global delay for the repeated task. If that's not the case, --2d is just fine too. Thanks for your feedback on this! -- Bastien