From mboxrd@z Thu Jan  1 00:00:00 1970
From: Matt Lundin <mdl@imapmail.org>
Subject: Re: Bug: Tag set in agenda need a refresh to be used in a filter
 [7.4]
Date: Thu, 28 Jul 2011 10:19:31 -0500
Message-ID: <87ei1aqvp8.fsf@fastmail.fm>
References: <CA+TMmK=ZdyqQHOnPrmJFbS292QcO44CXkpzA_EG7ycij60XWZQ@mail.gmail.com>
	<87fwlq4u4j.fsf@gnu.org>
Mime-Version: 1.0
Content-Type: text/plain
Return-path: <emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([140.186.70.92]:52588)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <lundin@fastmail.fm>) id 1QmSN6-0000EA-2w
	for emacs-orgmode@gnu.org; Thu, 28 Jul 2011 11:19:36 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <lundin@fastmail.fm>) id 1QmSN5-00089n-3k
	for emacs-orgmode@gnu.org; Thu, 28 Jul 2011 11:19:36 -0400
Received: from out4.smtp.messagingengine.com ([66.111.4.28]:60155)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <lundin@fastmail.fm>) id 1QmSN5-00089b-1S
	for emacs-orgmode@gnu.org; Thu, 28 Jul 2011 11:19:35 -0400
In-Reply-To: <87fwlq4u4j.fsf@gnu.org> (Bastien's message of "Thu, 28 Jul 2011
	11:44:28 +0200")
List-Id: "General discussions about Org-mode." <emacs-orgmode.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=unsubscribe>
List-Archive: </archive/html/emacs-orgmode>
List-Post: <mailto:emacs-orgmode@gnu.org>
List-Help: <mailto:emacs-orgmode-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=subscribe>
Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org
Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org
To: Bastien <bzg@altern.org>
Cc: emacs-orgmode@gnu.org, Nicolas Dudebout <nicolas.dudebout@gatech.edu>

Hi Bastien,

Bastien <bzg@altern.org> writes:

> Nicolas Dudebout <nicolas.dudebout@gatech.edu> writes:
>
>> When filtering with a tag that was just added, the result is not as
>> expected.
>>
>> * Steps *
>> 1 - Go in the agenda view.
>> 2 - Attach a tag <T> to an entry <E>.
>> 3 - Filter using tag <T>.
>> (4 - Refresh the view)
>>
>> * Expected behavior *
>> by doing steps 1-3, entry <E> should appear in the filtered output.
>>
>> * Actual behavior*
>> step 4 is needed to have entry <E> appear.

I would suggest that this *is* the expected behavior. The cost of
refreshing the agenda is relatively expensive - it should not be done on
each filter. 

If we do want to update the agenda after a tag change, then perhaps we
could update the text properties for the line

> This is now fixed in git repo, thanks!

This has the undesirable consequence of slowing down filtering by
triggering an agenda request.

Best,
Matt