From: "Andrew M. Nuxoll" <nuxoll@up.edu>
To: Bastien <bzg@altern.org>
Cc: emacs-orgmode@gnu.org
Subject: Re: Still Wishing for Snooze
Date: Thu, 24 Jan 2013 14:54:18 -0800 [thread overview]
Message-ID: <5101BB9A.5000505@up.edu> (raw)
In-Reply-To: <878v7i2p6k.fsf@bzg.ath.cx>
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
next prev parent reply other threads:[~2013-01-24 22:55 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 [this message]
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
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=5101BB9A.5000505@up.edu \
--to=nuxoll@up.edu \
--cc=bzg@altern.org \
--cc=emacs-orgmode@gnu.org \
/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).