From: Samuel Loury <konubinix@gmail.com>
To: Michael Brand <michael.ch.brand@gmail.com>,
Org Mode <emacs-orgmode@gnu.org>
Cc: "Andrew M. Nuxoll" <nuxoll@up.edu>
Subject: Re: Still Wishing for Snooze
Date: Sat, 09 Feb 2013 19:06:49 +0100 [thread overview]
Message-ID: <8738x5cqfa.fsf@gmail.com> (raw)
In-Reply-To: <CALn3zogd4H5e5Jc08iafJ5Z63XGq-A9rP4c7aphpQZGMs1mEWg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1348 bytes --]
Hi,
Michael Brand <michael.ch.brand@gmail.com> 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’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.
>
> Am I missing something?
>
I quite agree with you. It is also the way I understood it, with the
automatic removal of the -3d.
Only a tiny glitch there, I suppose you guessed it was written
SCHEDULED: <2013-02-01 Fri +1m -3d>
and not
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.
--
Konubinix
GPG Key : 7439106A
Fingerprint: 5993 BE7A DA65 E2D9 06CE 5C36 75D2 3CED 7439 106A
[-- Attachment #2: Type: application/pgp-signature, Size: 489 bytes --]
next prev parent reply other threads:[~2013-02-09 18:19 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-21 18:20 Still Wishing for Snooze Andrew M. Nuxoll
2013-01-23 10:42 ` Samuel Loury
2013-01-23 19:00 ` Andrew M. Nuxoll
2013-01-23 13:36 ` Bastien
2013-01-24 18:49 ` Andrew M. Nuxoll
2013-01-24 22:26 ` Bastien
2013-01-24 22:54 ` Andrew M. Nuxoll
2013-01-25 1:20 ` Eric S Fraga
2013-01-25 10:45 ` Bastien
2013-01-25 19:48 ` Andrew M. Nuxoll
2013-02-07 9:44 ` Bastien
2013-02-07 15:25 ` Michael Brand
2013-02-09 18:06 ` Samuel Loury [this message]
2013-02-09 20:50 ` Michael Brand
2013-02-12 10:21 ` Bastien
2013-02-12 12:29 ` Michael Brand
2013-02-12 13:24 ` Michael Brand
2013-02-12 15:57 ` Bastien
2013-02-12 16:33 ` Bastien
2013-02-12 18:09 ` Michael Brand
2013-02-13 11:09 ` Samuel Loury
2013-02-13 11:14 ` Bastien
2013-02-12 22:35 ` Andrew M. Nuxoll
2013-01-25 11:10 ` Michael Brand
2013-01-25 19:30 ` Andrew M. Nuxoll
2013-02-07 15:24 ` Michael Brand
2013-01-23 15:49 ` Michael Brand
2013-01-23 18:51 ` Andrew M. Nuxoll
2013-01-23 19:37 ` Michael Brand
2013-01-24 20:09 ` Marc-Oliver Ihm
2013-01-26 17:40 ` Marc-Oliver Ihm
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8738x5cqfa.fsf@gmail.com \
--to=konubinix@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=michael.ch.brand@gmail.com \
--cc=nuxoll@up.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.