From: Carsten Dominik <firstname.lastname@example.org>
To: Pete Phillips <email@example.com>
Cc: Bernt Hansen <firstname.lastname@example.org>, email@example.com
Subject: Re: tags-tree question
Date: Mon, 22 Jun 2009 13:56:38 +0200 [thread overview]
Message-ID: <EB17A047-CE90-4530-BB6C-63A59B4BAE39@gmail.com> (raw)
On Jun 22, 2009, at 11:53 AM, Pete Phillips wrote:
> Hi Bernt
> Bernt> That works for todo list searches only (not tags). There is a
> Bernt> new variable org-agenda-tags-todo-honor-ignore-options which
> Bernt> can set which I think does what you are looking for. I have
> Bernt> this set to t in my setup.
> Thanks for that.
> As far as I can determine this stops any scheduled/deadlines appearing
> *ever*. I want them to appear in my lists 30 days (for example)
> their scheduled/deadline date.
> When you wrote:
>> Bernt> This keeps all tasks with a schedules or deadline date
>> out of
>> Bernt> the list of tasks when searching for next tasks and by
>> Bernt> default deadlines show up on the agenda 30 days before they
>> Bernt> need to be done.
> Did you mean a custom agenda, or only the main agenda ?
> My requirement is to have them start appearing in my custom agendas
> nearer the time.
Pete, what exactly do you meam by "custom agenda" here.
It is a tags/property/todo search? In that case you
could try something like
as a search string
P.S. Nice to know you are still around, still using Org ... :-)
next prev parent reply other threads:[~2009-06-22 11:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-29 14:00 tags-tree question Pete Phillips
2008-10-29 15:52 ` Carsten Dominik
2008-10-29 15:59 ` Carsten Dominik
2008-11-01 12:51 ` Carsten Dominik
2008-11-02 23:20 ` Pete Phillips
2008-11-03 1:51 ` Bernt Hansen
2009-06-21 11:19 ` Pete Phillips
2009-06-21 13:46 ` Bernt Hansen
2009-06-22 9:53 ` Pete Phillips
2009-06-22 11:56 ` Carsten Dominik [this message]
2009-06-22 22:52 ` Pete Phillips
2009-06-23 10:07 ` Carsten Dominik
2009-06-23 8:26 ` Pete Phillips
2009-06-22 12:39 ` Bernt Hansen
2008-11-03 7:44 ` Carsten Dominik
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).