From: "Andrew M. Nuxoll" <nuxoll@up.edu>
To: Michael Brand <michael.ch.brand@gmail.com>
Cc: Org Mode <emacs-orgmode@gnu.org>
Subject: Re: Still Wishing for Snooze
Date: Fri, 25 Jan 2013 11:30:30 -0800 [thread overview]
Message-ID: <5102DD56.3050907@up.edu> (raw)
In-Reply-To: <CALn3zohwz1wDaVjVx_jw=ueAawM84y43gZrdemTL4OhoO2CB+w@mail.gmail.com>
That looks like a delay period on a SCHEDULED item would work very well
for me. I can see the positive delay period being useful to me as well.
This does look like it would be more difficult to implement because it's
a subtle change to existing code rather than something more modular.
:AMN:
On 01/25/2013 03:10 AM, Michael Brand wrote:
> Hi Andrew
>
> On Thu, Jan 24, 2013 at 11:54 PM, Andrew M. Nuxoll <nuxoll@up.edu> wrote:
>> Here an example scenario that illustrates my problem: Say, at the end of
>> each week I need to sit down and generate a report on my progress to send to
>> the boss. So I have recurring, weekly TODO entry on Friday morning. Well,
>> one week the report is delayed because a coworker was ill and couldn't send
>> me the data I needed on time. So, I have to delay that TODO entry until
>> Monday *just this one time.* I need to get it off my agenda for the day but
>> I don't want to mark is as completed because it's not.
>>
>> Right now the only way to do that is to mark it as completed anyway but make
>> a one-time copy of the TODO item with the new scheduled date. The problem
>> is that I have roughly thirty TODO items per day and, on any given day, I
>> need to delay about 10-20% of them for various reasons. (It's the nature of
>> my job though I don't think it's that unusual.) So making a copy of a TODO
>> item each time is inconvenient because I end up with dozens of copies
>> floating about.
>>
>> Furthermore, a delayed TODO item should have more urgency since it's been
>> delayed. But creating a copy means i can't do that. When Monday rolls
>> around and it's time to prepare that report it shows up in green text like
>> this in my agenda:
>> Scheduled: TODO [#B] Prepare TPS Report
>>
>> but I want it to be in red text like this:
>> Sched. 4x: TODO [#B] Prepare TPS Report
>>
>> This is why I'm looking for a distinct "snooze" or "delay" functionality. I
>> want a TODO item to disappear from the agenda until a specified date and
>> then reappear again waiting to be done with all the urgency associated with
>> that delay.
> Let me only suggest an idea to deal with this, item-based: When the
> DEADLINE “warning period” would be generalized to allow positive
> numbers then it would extend to a “warning and delay period”. Starting
> with:
>
> * TODO [#B] Verify login to the virtual machines
> DEADLINE: <2013-01-22 Tue +1w -0d>
>
> It could be delayed to <2013-01-24 Thu> which means two days later by
> changing the “warning and delay period” to 2d:
>
> * TODO [#B] Verify login to the virtual machines
> DEADLINE: <2013-01-22 Tue +1w 2d>
>
> This would not show up in the agenda until <2013-01-24 Thu>. At that
> date it would be shown with the desirable “In -2 d.:” for overdue to
> get the higher priority. When set to done it would become:
>
> * TODO [#B] Verify login to the virtual machines
> DEADLINE: <2013-01-29 Tue +1w -0d>
>
> Note the change from 2d to -0d: It is important that when the date
> repeats and has a positive warning period aka delay period then it
> must be reset to -0d. Otherwise undesirable suprises are guaranteed.
>
> The same “warning and delay period” could also be allowed for
> SCHEDULED, mainly usable with a positive range for a delay. Probably
> what you would prefer over DEADLINE for your use case. I would even
> allow negative numbers for a warning for SCHEDULED, with a default
> warning period of -0d to reflect current behavior.
>
> Michael
--
Andrew M. Nuxoll Phone: 503-943-7688
Asst Professor of Computer Science Fax: 503-943-7316
University of Portland - MSC #145 Email: nuxoll@up.edu
5000 N. Willamette Blvd Web: http://faculty.up.edu/nuxoll
Portland, OR 97203-5798 Office: Shiley Hall Rm 217
next prev parent reply other threads:[~2013-01-25 19:31 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
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 [this message]
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
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5102DD56.3050907@up.edu \
--to=nuxoll@up.edu \
--cc=emacs-orgmode@gnu.org \
--cc=michael.ch.brand@gmail.com \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).