From: Matthew Lundin <mdl@imapmail.org>
To: Carsten Dominik <carsten.dominik@gmail.com>
Cc: "Łukasz Stelmach" <lukasz.stelmach@iem.pw.edu.pl>,
"Matt Lundin" <mdl@imapmail.org>,
emacs-orgmode@gnu.org
Subject: Re: search for DEADLINE in warning period
Date: Thu, 11 Feb 2010 09:07:25 -0500 [thread overview]
Message-ID: <87tytn6f36.fsf@fastmail.fm> (raw)
In-Reply-To: <870BCCDC-702F-46E6-A40B-2AF4BECF7C54@gmail.com> (Carsten Dominik's message of "Wed, 10 Feb 2010 13:19:12 +0100")
Carsten Dominik <carsten.dominik@gmail.com> writes:
> On Feb 9, 2010, at 3:48 PM, Matt Lundin wrote:
>>
>> Interesting. The docstring for org-agenda-todo-ignore-deadlines
>> seems to
>> suggest otherwise. Is this documentation inaccurate?
>>
>> ,----
>> | Documentation:
>> | Non-nil means don't show near deadline entries in the global todo
>> list.
>> | Near means closer than `org-deadline-warning-days' days.
>> | The idea behind this is that such items will appear in the agenda
>> anyway.
>> | See also `org-agenda-todo-ignore-with-date'.
>> | See also the variable `org-agenda-tags-todo-honor-ignore-options'.
>> `----
>
> This ist just to explain what "near" means in the sentence before.
> I have improved the docstring, thanks.
>
Thanks for the explanation Carsten. That explains why setting the value
to 'near produced the expected behavior. But I see now that "t" does the
same thing.
Best,
Matt
next prev parent reply other threads:[~2010-02-11 14:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-09 12:00 search for DEADLINE in warning period Łukasz Stelmach
2010-02-09 12:28 ` Bernt Hansen
2010-02-09 14:17 ` Łukasz Stelmach
2010-02-09 14:22 ` Carsten Dominik
2010-02-09 14:48 ` Matt Lundin
2010-02-10 12:19 ` Carsten Dominik
2010-02-10 18:41 ` Łukasz Stelmach
2010-02-11 16:07 ` Carsten Dominik
2010-02-11 17:39 ` Łukasz Stelmach
2010-02-11 14:07 ` Matthew Lundin [this message]
2010-02-09 13:49 ` Matt Lundin
2010-02-09 13:58 ` Łukasz Stelmach
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=87tytn6f36.fsf@fastmail.fm \
--to=mdl@imapmail.org \
--cc=carsten.dominik@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=lukasz.stelmach@iem.pw.edu.pl \
/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).