emacs-orgmode
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Orgmode] Help with agenda-custom commands


From: Paul Holcomb
Subject: Re: [Orgmode] Help with agenda-custom commands
Date: Tue, 30 Sep 2008 11:40:46 -0500
User-agent: Mutt/1.4.2i

On Sun, Sep 28, 2008 at 07:16:41AM +0200, Carsten Dominik wrote:

> >*) Is there a simple way to construct an agenda view that:
> > -shows all past scheduled events for one TODO keyword only
> > -skips for all others

> I have not tested this, but you might be able to use the general tags/ 
> property/todo matcher
> on `C-c a m' like this:
> 
> SCHEDULED<"<today>"/!+MYTODOKEYWORD

 This works, but not for a day or week view.  

 On the positive side, while I was trying to figure out how to do
 this, I've started to rethink how I'm using the different date
 keywords.

 I was originally trying to overload the meaning of SCHEDULED.  Making
 a TODO item that starts in the future and then will continue showing
 up until done (as in the manual) for "WAITING" items, but also as a
 TODO item that starts in the future, but then should become a normal
 TODO item for everything not a "WAITING" item.
 
 I think a better approach to the second one is going to be using a
 property like ACTIVEON, like so:

  :PROPERTIES:
  :ACTIVEON:       <2008-10-01 Wed>
  :END:

 I'm still at the idea stage here, but think it could work with a hook
 similar to org-expiry.el or org-depend.el

> >*) Using a defconst symbol or function that evaluates to a stringp
> >in place of an actual string in for the match field.
> >
> > It seems like the evaluation order is at fault, but I couldn't get  
> >further.
> 
> indeed, currently the match entry is not evaluated.  I guess we could  
> do that, but it would involve changing several functions.  I would  
> need a convincing use case before I invest the time.  How would you  
> want to use this?

 Totally not important.  I was just trying to clean up some of my
 agenda functions and feared I was missing something basic.

-- 
Paul Holcomb                               *pholcomb    \@      cpoint  net*
GPG key fingerprint          2B62 05AE EE74 845A 705F  D716 28C4 FE1C 088F CFAC




reply via email to

[Prev in Thread] Current Thread [Next in Thread]