Re: Persistent filters in Org mode

[Carsten Dominik <dominik@uva.nl>]

Hi Thomas,

On May 15, 2010, at 11:32 PM, Thomas Morgan wrote:

> Hi, Carsten,
>
> Thanks for your reply.  I've been thinking about this --
> please forgive my lateness...
>
> Do you envision a new variable for a persistent filter,
> independent of `org-agenda-filter'?  As it stands, one can
> only make `org-agenda-filter' persistent or transient by
> toggling `org-agenda-persistent-filters'.  I've been leaving
> this on all the time, because it fits my usage of tags.
> Would it be useful to you and others, though, to keep
> separate persistent and transient filters?
>
> (Note on terminology: reviewing the manual just now I realized
> that `org-agenda-persistent-filters' should probably be renamed
> `org-agenda-persistent-filter', because adding a condition to
> a filter results in a narrowed filter, not several filters.)
>

Hmm, you are right, I was a bit confused and not really clear.

I had first thought that what you had built was to a persistent filter
that one would have to specicfy.  But now I see that all you did
was to not clear the filter when a new agenda command is run.

I think this is good - so if you agree, I will apply your patch
and rename the variable to ...persistent-filter

> The main thing I am missing now is a command to edit the filter
> in the minibuffer.  Or, if there's a separate persistent filter,
> perhaps the command could edit that if given an argument.
>
> It might also be useful to save filters to registers and restore
> them later.

I guess a command to edit the filter, and a dedicated history variable  
for that command would be good enough?  Would you like to make this  
command and send me a combined patch with both changes?

- Carsten