From mboxrd@z Thu Jan 1 00:00:00 1970 From: Carsten Dominik Subject: Re: Persistent filters in Org mode Date: Wed, 19 May 2010 11:46:56 +0200 Message-ID: References: <87mxwd7j90.fsf@ziiuu.com> <78236561-007D-4F32-AAA0-578773001D21@gmail.com> <874oi83l7q.fsf@ziiuu.com> Mime-Version: 1.0 (Apple Message framework v936) Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Return-path: Received: from [140.186.70.92] (port=38661 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OEgK1-0000PJ-0J for emacs-orgmode@gnu.org; Wed, 19 May 2010 06:16:21 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1OEgJn-0004PI-FG for emacs-orgmode@gnu.org; Wed, 19 May 2010 06:16:16 -0400 Received: from paard.ic.uva.nl ([145.18.40.182]:40866) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1OEgJn-0004Op-3J for emacs-orgmode@gnu.org; Wed, 19 May 2010 06:16:03 -0400 In-Reply-To: <874oi83l7q.fsf@ziiuu.com> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Thomas Morgan Cc: emacs-orgmode@gnu.org 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