emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Bastien <bzg@altern.org>
To: "Andrew M. Nuxoll" <nuxoll@up.edu>
Cc: emacs-orgmode@gnu.org
Subject: Re: Still Wishing for Snooze
Date: Wed, 23 Jan 2013 14:36:27 +0100	[thread overview]
Message-ID: <877gn410o4.fsf@bzg.ath.cx> (raw)
In-Reply-To: <50FD86D4.8080105@up.edu> (Andrew M. Nuxoll's message of "Mon, 21 Jan 2013 10:20:04 -0800")

Hi Andrew,

"Andrew M. Nuxoll" <nuxoll@up.edu> writes:

> 1.  Add a date tag to an entry that indicates that it is "inactive" until a
> certain date.  I'm picturing something like this:
>
> ***** TODO [#B] Verify login to the virtual machines
>       SCHEDULED: <2013-01-11 Tue +1w> DELAY: <2013-01-24 Thu>
>
> 2.  Add a command similar to org-deadline that I can use to attach a delay
> date to a to-do item
>
> 3.  When I display my agenda, items that are delayed are not displayed.
>
> My e-lisp is pretty rusty so *any* advice or help is great.  Could someone
> help point me to the right files and functions I'll need to modify to
> accomplish this?

C-h v org-agenda-ignore TAB will open many doors.

See C-h org-agenda-todo-ignore-timestamp RET for example:

  Non-nil means don't show entries with a timestamp.
  This applies when creating the global todo list.
  Valid values are:
  
  past     Don't show entries for today or in the past.
  
  future   Don't show entries with a timestamp in the future.
           The idea behind this is that if it has a future
           timestamp, you don't want to think about it until the
           date.
  
  all      Don't show any entries with a timestamp in the global todo list.
           The idea behind this is that by setting a timestamp, you
           have already "taken care" of this item.
  
  This variable can also have an integer as a value.  If positive (N),
  todos with a timestamp N or more days in the future will be ignored.  If
  negative (-N), todos with a timestamp N or more days in the past will be
  ignored.  If 0, todos with a timestamp either today or in the future will
  be ignored.  For example, a value of -1 will exclude todos with a
  timestamp in the past (yesterday or earlier), while a value of 7 will
  exclude todos with a timestamp a week or more in the future.
  
  See also `org-agenda-todo-ignore-with-date'.  See also the variable
  `org-agenda-tags-todo-honor-ignore-options' if you want to make his
  option also apply to the tags-todo list.
  
-- 
 Bastien

  parent reply	other threads:[~2013-01-23 13:36 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 [this message]
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
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=877gn410o4.fsf@bzg.ath.cx \
    --to=bzg@altern.org \
    --cc=emacs-orgmode@gnu.org \
    --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 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).