Re: Still Wishing for Snooze

["Andrew M. Nuxoll" <nuxoll@up.edu>]

Bastien:

Thanks for your patience and continued assistance.

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.

Any help would be appreciated.

:AMN:



On 01/24/2013 02:26 PM, Bastien wrote:
> Hi Andrew,
>
> "Andrew M. Nuxoll" <nuxoll@up.edu> writes:
>
>> My first problem is that C-h is mapped to backspace on my computer.
>> I presume (C-h v) means view help on a particular item.
> C-h v is normally bound to `describe-variable'.
>
> So you can run this:
>
> M-x describe-variable RET org-agenda-todo-ignore-timestamp RET
>
>> My second problem is that org-agenda-ignore is not a valid prefix for
>> anything in my version of org-mode.
> In recent Emacsen, the completion mechanism is clever enough to know
> what to do when entering
>
> M-x describe-variable RET org-agenda-ignore TAB
>
> On the first TAB, it offers "org-agenda-t-ignore-"
>
> If you complete "org-agenda-todo-ignore-" and press TAB again,
> you should see five variables.
>
>> (I have version 7.9.3d
>> installed.).  I *think* you intended to point me to variables that
>> begin with org-agenda-todo-ignore instead.  Can you confirm this is
>> so?
> I do :)
>
>> My third problem is that I can not figure out how to use these
>> variables to accomplish my purpose.  I think part of the problem is
>> that I am using custom agenda commands.  The relevant code snippet
>> for the command I use most is here:
>>      (setq org-agenda-custom-commands
>>       '(
>>         ("o" "Today's Tasks"
>>          ((agenda "" ((org-agenda-ndays 1)))  ;; limits the agenda
>> display to a single day
>>           (todo "TODO"))
>>          ((org-agenda-compact-blocks t)
>>           ))
>>           etc...
> Try this:
>
> (setq org-agenda-custom-commands
>        '(("X" "Todo test" todo "TODO"
>           ((org-agenda-todo-ignore-scheduled 2)))))
>
> When listing todos, the ones that are 2 days or more in the future
> will be ignored.
>
> You can also use this for tags-todo if
> `org-agenda-tags-todo-honor-ignore-options' is set to t.
>
> We don't have `org-agenda-agenda-honor-ignore-options' so
> this is not relevant in agenda-type views.  Maybe we can
> consider this.
>
> In your case, this does not solve your problem, since you
> want an item-based decision, not an agenda-based one.
>
> But... my first question would be...
>
> ***** TODO [#B] Verify login to the virtual machines
>        SCHEDULED: <2013-01-11 Tue +1w> DELAY: <2013-01-24 Thu>
>
> why not simply have this instead:
>
> ***** TODO [#B] Verify login to the virtual machines
>        SCHEDULED: <2013-01-25 Fri +1w>
>
> ?
>
> Maybe I miss something obvious in your workflow, and maybe
> this is something needed more widely.  Let us know!
>   
>> Would you please give me some more information?
> Hope that helps,
>


-- 
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