tags-tree question

tags-tree question

[Pete Phillips]

Hi

I have a bunch of org-agenda-custom-commands I have been using for
years, but today wanted to try to use the tags-tree setup to get a bit
more context in some views.

I tried this:

  ("S" tags-tree "Office/NEXT|LaptopS/NEXT")

(meaning I want only NEXT TODO type lines tagged with Office or tagged
with LaptopS).

When I execute this I appear to get a buffer with lines tagged with
Office in the hierarchy, and any lines at or below that with the TODO
type of NEXT.

Now I know I have some lines in this file such as:

**** NEXT Send owen an email re: meeting  :LaptopS:

but this doesn't come up in the buffer.

Can someone clarify whether it is possible to do thesetypes of searches
with tags-tree, and if so where am I going wrong ?

Cheers
Pete

Re: tags-tree question

[Carsten Dominik]

Hi Pete,

since the TODO part i this logic was only implemented very late,
the logic is unfortunately a bit strange:  "/" has the
lowest priority, and only on is allowed.

So I believe this should be your search string.

  "Office|LaptopS/NEXT"

It really should be the other way round... :-(

With a speed penalty, you can also write

"Office+TODO=\"NEXT\"|LaptopS+TODO=\"NEXT\""

which uses the property API access to TODO keywords.


A generalized logic are, and also lisp forms for searches are
on my list, as are so many other things......

HTH

- Carsten

On Oct 29, 2008, at 3:00 PM, Pete Phillips wrote:

> Hi
>
> I have a bunch of org-agenda-custom-commands I have been using for
> years, but today wanted to try to use the tags-tree setup to get a bit
> more context in some views.
>
> I tried this:
>
>  ("S" tags-tree "Office/NEXT|LaptopS/NEXT")
>
> (meaning I want only NEXT TODO type lines tagged with Office or tagged
> with LaptopS).
>
> When I execute this I appear to get a buffer with lines tagged with
> Office in the hierarchy, and any lines at or below that with the TODO
> type of NEXT.
>
> Now I know I have some lines in this file such as:
>
> **** NEXT Send owen an email re: meeting  :LaptopS:
>
> but this doesn't come up in the buffer.
>
> Can someone clarify whether it is possible to do thesetypes of  
> searches
> with tags-tree, and if so where am I going wrong ?
>
> Cheers
> Pete
>
>
> _______________________________________________
> Emacs-orgmode mailing list
> Remember: use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: tags-tree question

[Carsten Dominik]

Oh my, I am starting to type like a monkey, this gets really  
embarrassing.
Let me try again:

-------------------------------------------------------------------

Hi Pete,

since the TODO part in match views was only implemented very late,
the logic is unfortunately a bit strange:  "/" has the
lowest priority, and only one such operator is allowed.

For your particular case, there is still a way to write this:

"Office|LaptopS/NEXT"

It really should be the other way round, with "|" as the lowest
priority, and more than two terms allowed. :-(

With a speed penalty, you can also write

"Office+TODO=\"NEXT\"|LaptopS+TODO=\"NEXT\""

which uses the property access to TODO keywords.

A generalized logic is on my list, just like Lisp forms for
searches, and so many other things....

HTH

- Carsten

> On Oct 29, 2008, at 3:00 PM, Pete Phillips wrote:
>
>> Hi
>>
>> I have a bunch of org-agenda-custom-commands I have been using for
>> years, but today wanted to try to use the tags-tree setup to get a  
>> bit
>> more context in some views.
>>
>> I tried this:
>>
>> ("S" tags-tree "Office/NEXT|LaptopS/NEXT")
>>
>> (meaning I want only NEXT TODO type lines tagged with Office or  
>> tagged
>> with LaptopS).
>>
>> When I execute this I appear to get a buffer with lines tagged with
>> Office in the hierarchy, and any lines at or below that with the TODO
>> type of NEXT.
>>
>> Now I know I have some lines in this file such as:
>>
>> **** NEXT Send owen an email re: meeting  :LaptopS:
>>
>> but this doesn't come up in the buffer.
>>
>> Can someone clarify whether it is possible to do thesetypes of  
>> searches
>> with tags-tree, and if so where am I going wrong ?
>>
>> Cheers
>> Pete
>>
>>
>> _______________________________________________
>> Emacs-orgmode mailing list
>> Remember: use `Reply All' to send replies to the list.
>> Emacs-orgmode@gnu.org
>> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
>

Re: tags-tree question

[Carsten Dominik]

On Oct 29, 2008, at 4:52 PM, Carsten Dominik wrote:

> Hi Pete,
>
> since the TODO part i this logic was only implemented very late,
> the logic is unfortunately a bit strange:  "/" has the
> lowest priority, and only on is allowed.
>
> So I believe this should be your search string.
>
> "Office|LaptopS/NEXT"
>
> It really should be the other way round... :-(
>
> With a speed penalty, you can also write
>
> "Office+TODO=\"NEXT\"|LaptopS+TODO=\"NEXT\""

I have now removed the speed-penalty on this syntax.
So if, during a tag search, you use property-like expressions
for TODO, LEVEL, or CATEGORY, there will be no speed penalty
involved.  If you access any other properties, there will be
a one-time penalty.  Once you have paid that penalty for a
single property, it is cheap to test additional properties
(unless inheritance is involved).

I have also improved the documentation related to this.

- Carsten

Re: tags-tree question

[Pete Phillips]

Hi Carsten

    Carsten> I have now removed the speed-penalty on this syntax.  So
    Carsten> if, during a tag search, you use property-like expressions
    Carsten> for TODO, LEVEL, or CATEGORY, there will be no speed
    Carsten> penalty involved.  If you access any other properties,
    Carsten> there will be a one-time penalty.  Once you have paid that
    Carsten> penalty for a single property, it is cheap to test
    Carsten> additional properties (unless inheritance is involved).

Many thanks for doing this. I haven't had the chance to try it out yet
(been too busy actually getting things off my Home list this w/e! - oh -
and letting fireworks off tonight as well <grin>) but your solution from
last week using the non-intuitive method worked perfectly for me anyhow.

On a related question, is it possible to set up an
org-agenda-custom-command to pick out a set of tags, all of which have
NEXT as a todo-type, and which either have no scheduled date, OR which
have a scheduled or deadline date less than or equal to 1 month in the
future.

For example, show lines with 

    NEXT and (Home | LaptopH | DIY) 

where either there is no scheduled (or perhaps, deadline) date OR 

	Scheduled Date <= today + 1 month

My thinking on this is that sometimes I have next actions (such as
cutting my pampas grass every january), which would be set up like this:

*** NEXT Cut pampass grass :DIY:
SCHEDULED: <2009-01-12 Thu>

My current setup uses this:

 ("h" "Home Stuff (Next)"
  ((tags "Home//NEXT" nil)
   (tags "DIY//NEXT" nil)
   (tags "LaptopH//NEXT" nil)
  nil)

The problem at the moment is that it shows up all year in my Home Stuff
(Next) list (which searches for Home|LaptopH|DIY with NEXT todotypes),
but I only want it to start showing up about a month before the date I
have decided I need to do it. At the moment, NEXT items which I will
need to do, but which I can't do anything about until nearer the time,
clutter up my action lists.

Is there any way to do this ?

Cheers,
Pete

Re: tags-tree question

[Bernt Hansen]

Pete Phillips <pete@smtl.co.uk> writes:

> On a related question, is it possible to set up an
> org-agenda-custom-command to pick out a set of tags, all of which have
> NEXT as a todo-type, and which either have no scheduled date, OR which
> have a scheduled or deadline date less than or equal to 1 month in the
> future.
>
> For example, show lines with 
>
>     NEXT and (Home | LaptopH | DIY) 
>
> where either there is no scheduled (or perhaps, deadline) date OR 
>
> 	Scheduled Date <= today + 1 month
>
> My thinking on this is that sometimes I have next actions (such as
> cutting my pampas grass every january), which would be set up like this:
>
> *** NEXT Cut pampass grass :DIY:
> SCHEDULED: <2009-01-12 Thu>
>
> My current setup uses this:
>
>  ("h" "Home Stuff (Next)"
>   ((tags "Home//NEXT" nil)
>    (tags "DIY//NEXT" nil)
>    (tags "LaptopH//NEXT" nil)
>   nil)
>
> The problem at the moment is that it shows up all year in my Home Stuff
> (Next) list (which searches for Home|LaptopH|DIY with NEXT todotypes),
> but I only want it to start showing up about a month before the date I
> have decided I need to do it. At the moment, NEXT items which I will
> need to do, but which I can't do anything about until nearer the time,
> clutter up my action lists.
>
> Is there any way to do this ?

Hi Pete,

For this do something like the following:

Set a deadline date on 

*** NEXT Cut pampass grass :DIY:
DEADLINE: <2009-01-12 Thu>

and

(setq org-agenda-todo-ignore-with-date t)

This keeps all tasks with a schedules or deadline date out of the list
of tasks when searching for next tasks and by default deadlines show up
on the agenda 30 days before they need to be done.

I find I'm using DEADLINE: a lot more then SCHEDULED: in my tasks.

In this case your custom agenda command to match NEXT tasks will not
list the tasks with dates (ever) and those tasks will show up on the
agenda 30 days before they need to be complete.  You can control when
they show up individually using dates such as

DEADLINE: <2009-01-12 Thu -60d>

This works great for me.

Regards,
Bernt

Re: tags-tree question

[Carsten Dominik]

Hi Pete,

there is currently no way o say "today plus 1 month" in a query.  The  
rest of it would be possible.

- Carsten

On Nov 3, 2008, at 12:20 AM, Pete Phillips wrote:

> Hi Carsten
>
>    Carsten> I have now removed the speed-penalty on this syntax.  So
>    Carsten> if, during a tag search, you use property-like expressions
>    Carsten> for TODO, LEVEL, or CATEGORY, there will be no speed
>    Carsten> penalty involved.  If you access any other properties,
>    Carsten> there will be a one-time penalty.  Once you have paid that
>    Carsten> penalty for a single property, it is cheap to test
>    Carsten> additional properties (unless inheritance is involved).
>
> Many thanks for doing this. I haven't had the chance to try it out yet
> (been too busy actually getting things off my Home list this w/e! -  
> oh -
> and letting fireworks off tonight as well <grin>) but your solution  
> from
> last week using the non-intuitive method worked perfectly for me  
> anyhow.
>
> On a related question, is it possible to set up an
> org-agenda-custom-command to pick out a set of tags, all of which have
> NEXT as a todo-type, and which either have no scheduled date, OR which
> have a scheduled or deadline date less than or equal to 1 month in the
> future.
>
> For example, show lines with
>
>    NEXT and (Home | LaptopH | DIY)
>
> where either there is no scheduled (or perhaps, deadline) date OR
>
> 	Scheduled Date <= today + 1 month
>
> My thinking on this is that sometimes I have next actions (such as
> cutting my pampas grass every january), which would be set up like  
> this:
>
> *** NEXT Cut pampass grass :DIY:
> SCHEDULED: <2009-01-12 Thu>
>
> My current setup uses this:
>
> ("h" "Home Stuff (Next)"
>  ((tags "Home//NEXT" nil)
>   (tags "DIY//NEXT" nil)
>   (tags "LaptopH//NEXT" nil)
>  nil)
>
> The problem at the moment is that it shows up all year in my Home  
> Stuff
> (Next) list (which searches for Home|LaptopH|DIY with NEXT todotypes),
> but I only want it to start showing up about a month before the date I
> have decided I need to do it. At the moment, NEXT items which I will
> need to do, but which I can't do anything about until nearer the time,
> clutter up my action lists.
>
> Is there any way to do this ?
>
> Cheers,
> Pete
>

Re: tags-tree question

[Pete Phillips]

Afternoon all.

Last Nov I asked on the list if it was possible to have TODO items with
a scheduled/deadline date more than 30 (or some fixed number) of days in
the future to NOT show up on my custom agenda. The reason being that I
don't want to be distracted when I look at my custom Home list by a task
for next January until closer to the time. I have added my original
email to the bottom of this in case you have forgotten it!  :-)

Bernt's reply was:

>>>>> "Bernt" == Bernt Hansen <bernt@norang.ca> writes:

    Bernt> Hi Pete,
    Bernt> For this do something like the following:
    Bernt> Set a deadline date on

    Bernt> *** NEXT Cut pampass grass :DIY: DEADLINE: <2009-01-12 Thu>

    Bernt> and

    Bernt> (setq org-agenda-todo-ignore-with-date t)

    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.

    Bernt> I find I'm using DEADLINE: a lot more then SCHEDULED: in my
    Bernt> tasks.

    Bernt> In this case your custom agenda command to match NEXT tasks
    Bernt> will not list the tasks with dates (ever) and those tasks
    Bernt> will show up on the agenda 30 days before they need to be
    Bernt> complete.  

I couldn't get this to work at the time but have been trying to sort
this issue out again over the last few days. 

Having set:

       (setq org-agenda-todo-ignore-with-date t)

I can see that scheduled items for next January (cutting my pampas
grass) are kept out of the pre-configured 

  ^C a t 

command (list of all TODO entries) - so this does in fact work - my
pampas grass entry doesn't show. However, my custom agenda command for
Home does show it.

(see my orig email below for details on the custom agenda).

So it appears to me that there is a difference in how the
org-agenda-todo-ignore-with-date variable behaves in the pre-configured
TODO list and my custom view.

Is there something simple I'm missing or is this a bug ?

Cheers
Pete
---------------------------------------------------

Pete Phillips <pete@smtl.co.uk> writes:

 Pete> > On a related question, is it possible to set up an
 Pete> > org-agenda-custom-command to pick out a set of tags, all of which have
 Pete> > NEXT as a todo-type, and which either have no scheduled date, OR which
 Pete> > have a scheduled or deadline date less than or equal to 1 month in the
 Pete> > future.
 Pete> >
 Pete> > For example, show lines with 
 Pete> >
 Pete> >     NEXT and (Home | LaptopH | DIY) 
 Pete> >
 Pete> > where either there is no scheduled (or perhaps, deadline) date OR 
 Pete> >
 Pete> > 	Scheduled Date <= today + 1 month
 Pete> >
 Pete> > My thinking on this is that sometimes I have next actions (such as
 Pete> > cutting my pampas grass every january), which would be set up like this:
 Pete> >
 Pete> > *** NEXT Cut pampass grass :DIY:
 Pete> > SCHEDULED: <2009-01-12 Thu>
 Pete> >
 Pete> > My current setup uses this:
 Pete> >
 Pete> >  ("h" "Home Stuff (Next)"
 Pete> >   ((tags "Home//NEXT" nil)
 Pete> >    (tags "DIY//NEXT" nil)
 Pete> >    (tags "LaptopH//NEXT" nil)
 Pete> >   nil)
 Pete> >
 Pete> > The problem at the moment is that it shows up all year in my Home Stuff
 Pete> > (Next) list (which searches for Home|LaptopH|DIY with NEXT todotypes),
 Pete> > but I only want it to start showing up about a month before the date I
 Pete> > have decided I need to do it. At the moment, NEXT items which I will
 Pete> > need to do, but which I can't do anything about until nearer the time,
 Pete> > clutter up my action lists.
 Pete> >
 Pete> > Is there any way to do this ?

 Bernt> Hi Pete,
 Bernt> 
 Bernt> For this do something like the following:
 Bernt> 
 Bernt> Set a deadline date on 
 Bernt> 
 Bernt> *** NEXT Cut pampass grass :DIY:
 Bernt> DEADLINE: <2009-01-12 Thu>
 Bernt> 
 Bernt> and
 Bernt> 
 Bernt> (setq org-agenda-todo-ignore-with-date t)
 Bernt> 
 Bernt> This keeps all tasks with a schedules or deadline date out of the list
 Bernt> of tasks when searching for next tasks and by default deadlines show up
 Bernt> on the agenda 30 days before they need to be done.
 Bernt> 
 Bernt> I find I'm using DEADLINE: a lot more then SCHEDULED: in my tasks.
 Bernt> 
 Bernt> In this case your custom agenda command to match NEXT tasks will not
 Bernt> list the tasks with dates (ever) and those tasks will show up on the
 Bernt> agenda 30 days before they need to be complete.  You can control when
 Bernt> they show up individually using dates such as
 Bernt> 
 Bernt> DEADLINE: <2009-01-12 Thu -60d>
 Bernt> 
 Bernt> This works great for me.
 Bernt> 
 Bernt> Regards,
 Bernt> Bernt

Re: tags-tree question

[Bernt Hansen]

Hi Pete,

That works for todo list searches only (not tags).  There is a new
variable org-agenda-tags-todo-honor-ignore-options which you can set
which I think does what you are looking for.  I have this set to t in my
setup.

HTH,
Bernt


Pete Phillips <pete@smtl.co.uk> writes:

> Afternoon all.
>
> Last Nov I asked on the list if it was possible to have TODO items with
> a scheduled/deadline date more than 30 (or some fixed number) of days in
> the future to NOT show up on my custom agenda. The reason being that I
> don't want to be distracted when I look at my custom Home list by a task
> for next January until closer to the time. I have added my original
> email to the bottom of this in case you have forgotten it!  :-)
>
> Bernt's reply was:
>
>>>>>> "Bernt" == Bernt Hansen <bernt@norang.ca> writes:
>
>     Bernt> Hi Pete,
>     Bernt> For this do something like the following:
>     Bernt> Set a deadline date on
>
>     Bernt> *** NEXT Cut pampass grass :DIY: DEADLINE: <2009-01-12 Thu>
>
>     Bernt> and
>
>     Bernt> (setq org-agenda-todo-ignore-with-date t)
>
>     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.
>
>     Bernt> I find I'm using DEADLINE: a lot more then SCHEDULED: in my
>     Bernt> tasks.
>
>     Bernt> In this case your custom agenda command to match NEXT tasks
>     Bernt> will not list the tasks with dates (ever) and those tasks
>     Bernt> will show up on the agenda 30 days before they need to be
>     Bernt> complete.  
>
> I couldn't get this to work at the time but have been trying to sort
> this issue out again over the last few days. 
>
> Having set:
>
>        (setq org-agenda-todo-ignore-with-date t)
>
> I can see that scheduled items for next January (cutting my pampas
> grass) are kept out of the pre-configured 
>
>   ^C a t 
>
> command (list of all TODO entries) - so this does in fact work - my
> pampas grass entry doesn't show. However, my custom agenda command for
> Home does show it.
>
> (see my orig email below for details on the custom agenda).
>
> So it appears to me that there is a difference in how the
> org-agenda-todo-ignore-with-date variable behaves in the pre-configured
> TODO list and my custom view.
>
> Is there something simple I'm missing or is this a bug ?
>
> Cheers
> Pete
> ---------------------------------------------------
>
> Pete Phillips <pete@smtl.co.uk> writes:
>
>  Pete> > On a related question, is it possible to set up an
>  Pete> > org-agenda-custom-command to pick out a set of tags, all of which have
>  Pete> > NEXT as a todo-type, and which either have no scheduled date, OR which
>  Pete> > have a scheduled or deadline date less than or equal to 1 month in the
>  Pete> > future.
>  Pete> >
>  Pete> > For example, show lines with 
>  Pete> >
>  Pete> >     NEXT and (Home | LaptopH | DIY) 
>  Pete> >
>  Pete> > where either there is no scheduled (or perhaps, deadline) date OR 
>  Pete> >
>  Pete> > 	Scheduled Date <= today + 1 month
>  Pete> >
>  Pete> > My thinking on this is that sometimes I have next actions (such as
>  Pete> > cutting my pampas grass every january), which would be set up like this:
>  Pete> >
>  Pete> > *** NEXT Cut pampass grass :DIY:
>  Pete> > SCHEDULED: <2009-01-12 Thu>
>  Pete> >
>  Pete> > My current setup uses this:
>  Pete> >
>  Pete> >  ("h" "Home Stuff (Next)"
>  Pete> >   ((tags "Home//NEXT" nil)
>  Pete> >    (tags "DIY//NEXT" nil)
>  Pete> >    (tags "LaptopH//NEXT" nil)
>  Pete> >   nil)
>  Pete> >
>  Pete> > The problem at the moment is that it shows up all year in my Home Stuff
>  Pete> > (Next) list (which searches for Home|LaptopH|DIY with NEXT todotypes),
>  Pete> > but I only want it to start showing up about a month before the date I
>  Pete> > have decided I need to do it. At the moment, NEXT items which I will
>  Pete> > need to do, but which I can't do anything about until nearer the time,
>  Pete> > clutter up my action lists.
>  Pete> >
>  Pete> > Is there any way to do this ?
>
>  Bernt> Hi Pete,
>  Bernt> 
>  Bernt> For this do something like the following:
>  Bernt> 
>  Bernt> Set a deadline date on 
>  Bernt> 
>  Bernt> *** NEXT Cut pampass grass :DIY:
>  Bernt> DEADLINE: <2009-01-12 Thu>
>  Bernt> 
>  Bernt> and
>  Bernt> 
>  Bernt> (setq org-agenda-todo-ignore-with-date t)
>  Bernt> 
>  Bernt> This keeps all tasks with a schedules or deadline date out of the list
>  Bernt> of tasks when searching for next tasks and by default deadlines show up
>  Bernt> on the agenda 30 days before they need to be done.
>  Bernt> 
>  Bernt> I find I'm using DEADLINE: a lot more then SCHEDULED: in my tasks.
>  Bernt> 
>  Bernt> In this case your custom agenda command to match NEXT tasks will not
>  Bernt> list the tasks with dates (ever) and those tasks will show up on the
>  Bernt> agenda 30 days before they need to be complete.  You can control when
>  Bernt> they show up individually using dates such as
>  Bernt> 
>  Bernt> DEADLINE: <2009-01-12 Thu -60d>
>  Bernt> 
>  Bernt> This works great for me.
>  Bernt> 
>  Bernt> Regards,
>  Bernt> Bernt

Re: tags-tree question

[Pete Phillips]

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 you
 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)  before
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.

Cheers
Pete

Re: tags-tree question

[Carsten Dominik]

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  
> you
> 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)   
> before
> 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


       TODO="TODO"+DEADLINE<"<+1m>"

as a search string

HTH

- Carsten

P.S. Nice to know you are still around, still using Org ... :-)




>
> Cheers
> Pete

Re: tags-tree question

[Bernt Hansen]

Pete Phillips <pete@smtl.co.uk> writes:

> 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 you
>  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)  before
> their scheduled/deadline date.

Hi Pete

This keeps them off the global todo lists and tags searches.  They still
show up on the agenda when you look at daily and weekly views
org-deadline-warning-days before the deadline.  You can also set custom
warning dates individually on tasks as in

   DEADLINE: <2009-07-01 Wed +1m -3d> 

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

I meant the global todo list and the results of tags searches (C-c a t,
C-c a m)  The tasks show up on your dated agenda with C-c a a.

The _only_ place I see tasks with dates is in the C-c a a view.

HTH,
Bernt

Re: tags-tree question

[Pete Phillips]

Evening to you all 

>>>>> "Carsten" == Carsten Dominik <carsten.dominik@gmail.com> writes:

    Carsten> Pete, what exactly do you meam by "custom agenda" here.  

I mean it's one of my org-agenda-custom-commands. This is my (probably
overly) complex setup to list any of the things I do at home, which have
a TODO="NEXT" action associated with them. 

  ("h" "Home Stuff (Next)"
   ((tags-todo "Home//NEXT" nil)
    (tags-todo "DIY//NEXT" nil)
    (tags-todo "Karen//NEXT" nil)
    (tags-todo "PhoneH//NEXT" nil)
    (tags-todo "LaptopH//NEXT" nil)
    (tags-todo "WaitingH//NEXT" nil)
    (tags-todo "SometimeH//NEXT" nil))
   nil)

Some of these actions will have SCHEDULED or DEADLINE dates associated
with them and I only want to see those actions 30 days (or perhaps 60
days) before the date. Anything without a DEADLine or SCHEDULED date I
want to see in the list.

    Carsten> It is a tags/property/todo search?  In that case you could
    Carsten> try something like
    Carsten>       TODO="TODO"+DEADLINE<"<+1m>"
    Carsten> as a search string

OK - promising - this looks like it may do what I want:

 ("h" "Home Stuff (Next)"
 (
  (tags-todo "TODO=\"NEXT\"+Home+DEADLINE<\"<+1m>\"" nil)
  (tags-todo "TODO=\"NEXT\"+Home+DEADLINE=\"\"" nil)
  (tags-todo "TODO=\"NEXT\"+Home+SCHEDULED<\"<+1m>\"" nil)
  (tags-todo "TODO=\"NEXT\"+Home+SCHEDULED=\"\"" nil)

etc

I.e., find me NEXT items with the tag of Home, with a deadline within
the next month, AND find me NEXT items with the Home tag, where there is
no DEADLINE, AND ....

But that does seem very complex. (it also feels slow).

    Carsten> HTH

It does. At least i know there is a way to do it.  The question now is -
is there an easier way ?

    Carsten> - Carsten

    Carsten> P.S. Nice to know you are still around, still using Org
    Carsten> ... :-)

:-) 

I haven't stopped using org-mode - it is the lubricant which oils the
wheels of my life.  I have just reduced the time I can spend reading and
responding to mailing list emails. :-( Still grazing on the list though.

Cheers
Pete

Re: tags-tree question

[Pete Phillips]

Morning guys.

>>>>> "Pete" == Pete Phillips <pete.phillips <at> smtl.co.uk> writes:

 Pete> Some of these actions will have SCHEDULED or DEADLINE dates associated
 Pete> with them and I only want to see those actions 30 days (or perhaps 60
 Pete> days) before the date. Anything without a DEADLine or SCHEDULED date I
 Pete> want to see in the list.

    Carsten> It is a tags/property/todo search?  In that case you could
    Carsten> try something like
    Carsten>       TODO="TODO"+DEADLINE<"<+1m>"
    Carsten> as a search string

 Pete> OK - promising - this looks like it may do what I want:

 Pete>  ("h" "Home Stuff (Next)"
 Pete>  (
 Pete>   (tags-todo "TODO=\"NEXT\"+Home+DEADLINE<\"<+1m>\"" nil)
 Pete>   (tags-todo "TODO=\"NEXT\"+Home+DEADLINE=\"\"" nil)
 Pete>   (tags-todo "TODO=\"NEXT\"+Home+SCHEDULED<\"<+1m>\"" nil)
 Pete>   (tags-todo "TODO=\"NEXT\"+Home+SCHEDULED=\"\"" nil)

 Pete> etc

 Pete> I.e., find me NEXT items with the tag of Home, with a deadline within
 Pete> the next month, AND find me NEXT items with the Home tag, where there is
 Pete> no DEADLINE, AND ....

Hmm - not sure this does what I want. Can you tell me if the expression:

 (tags-todo "TODO=\"NEXT\"+Home+SCHEDULED=\"\"" nil)

looks for a TODO=NEXT, with TAG=Home and *no* SCHEDULED date ?
(i.e. there is no SCHEDULED: <xxxx-xx-xx > line associated with that
item) ?

My results are confusing at the moment. I can see some SCHEDULED items
when I wouldn't expect to.

 Pete> But that does seem very complex. (it also feels slow).

Yeah - taking around 30-40 seconds to build the buffer.  Are there any
potential speedups ?

Pete

Re: tags-tree question

[Carsten Dominik]

On Jun 23, 2009, at 12:52 AM, Pete Phillips wrote:

> Evening to you all
>
>>>>>> "Carsten" == Carsten Dominik <carsten.dominik@gmail.com> writes:
>
>    Carsten> Pete, what exactly do you meam by "custom agenda" here.
>
> I mean it's one of my org-agenda-custom-commands. This is my (probably
> overly) complex setup to list any of the things I do at home, which  
> have
> a TODO="NEXT" action associated with them.
>
>  ("h" "Home Stuff (Next)"
>   ((tags-todo "Home//NEXT" nil)
>    (tags-todo "DIY//NEXT" nil)
>    (tags-todo "Karen//NEXT" nil)
>    (tags-todo "PhoneH//NEXT" nil)
>    (tags-todo "LaptopH//NEXT" nil)
>    (tags-todo "WaitingH//NEXT" nil)
>    (tags-todo "SometimeH//NEXT" nil))
>   nil)
>
> Some of these actions will have SCHEDULED or DEADLINE dates associated
> with them and I only want to see those actions 30 days (or perhaps 60
> days) before the date. Anything without a DEADLine or SCHEDULED date I
> want to see in the list.
>
>    Carsten> It is a tags/property/todo search?  In that case you could
>    Carsten> try something like
>    Carsten>       TODO="TODO"+DEADLINE<"<+1m>"
>    Carsten> as a search string
>
> OK - promising - this looks like it may do what I want:
>
> ("h" "Home Stuff (Next)"
> (
>  (tags-todo "TODO=\"NEXT\"+Home+DEADLINE<\"<+1m>\"" nil)
>  (tags-todo "TODO=\"NEXT\"+Home+DEADLINE=\"\"" nil)
>  (tags-todo "TODO=\"NEXT\"+Home+SCHEDULED<\"<+1m>\"" nil)
>  (tags-todo "TODO=\"NEXT\"+Home+SCHEDULED=\"\"" nil)
>
> etc
>
> I.e., find me NEXT items with the tag of Home, with a deadline within
> the next month, AND find me NEXT items with the Home tag, where  
> there is
> no DEADLINE, AND ....
>
> But that does seem very complex. (it also feels slow).
>
>    Carsten> HTH
>
> It does. At least i know there is a way to do it.  The question now  
> is -
> is there an easier way ?

Not currently, no.  And yes, it will be slow because of accessing  
properties
(DEADLINE counts as a property in this case).

You could construct a faster way by using org-agenda-skip and looking  
for
the deadline yourself.  That might actually work quite well and  
reasonably fast.

Let me know if you need help to put this together.

- Carsten

>
>    Carsten> - Carsten
>
>    Carsten> P.S. Nice to know you are still around, still using Org
>    Carsten> ... :-)
>
> :-)
>
> I haven't stopped using org-mode - it is the lubricant which oils the
> wheels of my life.  I have just reduced the time I can spend reading  
> and
> responding to mailing list emails. :-( Still grazing on the list  
> though.
>
> Cheers
> Pete
>
>
>