From mboxrd@z Thu Jan 1 00:00:00 1970 From: Samuel Loury Subject: Re: Still Wishing for Snooze Date: Sat, 09 Feb 2013 19:06:49 +0100 Message-ID: <8738x5cqfa.fsf@gmail.com> 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: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature" Return-path: Received: from eggs.gnu.org ([208.118.235.92]:58282) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1U4F0w-0007YX-5o for emacs-orgmode@gnu.org; Sat, 09 Feb 2013 13:19:03 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1U4F0u-0007Vu-Sk for emacs-orgmode@gnu.org; Sat, 09 Feb 2013 13:19:02 -0500 Received: from mail-wg0-f53.google.com ([74.125.82.53]:41827) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1U4EuK-0006FQ-6U for emacs-orgmode@gnu.org; Sat, 09 Feb 2013 13:12:12 -0500 Received: by mail-wg0-f53.google.com with SMTP id fn15so3794349wgb.20 for ; Sat, 09 Feb 2013 10:12:10 -0800 (PST) In-Reply-To: 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 , Org Mode Cc: "Andrew M. Nuxoll" --=-=-= Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Hi, Michael Brand writes: > 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=E2=80=99s say [2013-02-05 Tue] it woul= d be > set to DONE and would change to: > > SCHEDULED: <2013-03-01 Fri +1w> > > Note the automatically removed delay. > > Am I missing something? > I quite agree with you. It is also the way I understood it, with the automatic removal of the -3d.=20 Only a tiny glitch there, I suppose you guessed it was written SCHEDULED: <2013-02-01 Fri +1m -3d> and not=20 SCHEDULED: <2013-02-01 Fri +1w -3d> Because your description is about a monthly repeated event while the example shows a weekly event. It is really nothing but I think someone might find it confusing. =2D-=20 Konubinix GPG Key : 7439106A Fingerprint: 5993 BE7A DA65 E2D9 06CE 5C36 75D2 3CED 7439 106A --=-=-= Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) iQEcBAEBAgAGBQJRFpA5AAoJEHXSPO10ORBqdskH/2/rIaodSHl2cVPMLB5ZaGu4 Ueu+y6384h5+/CPF3YBzWd7YOWXvcUk6sM/YN+Uo3Wncr2rRVCwLb8zh8jcoTUwk RJzZHmVF5Nv4n7m0Imytk5ylnepQNOxl2Ebsl/138OfO3cm9h2cXgjzhwoGiGMc+ NMcQGdnA5O3GJNFwpHkj6cD9/nj+xZlt6a38D+hwhvOUt1FoX4JjnaM+/yLnuMs6 FX+rjmb6qfm6op+ZmbWNl6qGhvQPrJsdr8W1eK6tCcM4q9A3k9sk6fUHx1NqplA+ MVfMaGzaoJ23ZZ4ckJq+yvd/m0SvmjyIhznaU8BKDB33LrYsRjA0eQReXsv2QQ8= =oK31 -----END PGP SIGNATURE----- --=-=-=--