From mboxrd@z Thu Jan  1 00:00:00 1970
From: Bastien <bzg@altern.org>
Subject: Re: Block agendas and filtering
Date: Tue, 19 Mar 2013 18:32:32 +0100
Message-ID: <877gl3rzik.fsf@bzg.ath.cx>
References: <5136BC01.8060302@gmail.com>
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 ([208.118.235.92]:37008)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <bastienguerry@gmail.com>) id 1UI1gU-0002jq-20
	for emacs-orgmode@gnu.org; Tue, 19 Mar 2013 14:54:59 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <bastienguerry@gmail.com>) id 1UI1gQ-0002JJ-Ua
	for emacs-orgmode@gnu.org; Tue, 19 Mar 2013 14:54:53 -0400
Received: from mail-we0-x22b.google.com ([2a00:1450:400c:c03::22b]:44022)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <bastienguerry@gmail.com>) id 1UI1gQ-0002IN-MQ
	for emacs-orgmode@gnu.org; Tue, 19 Mar 2013 14:54:50 -0400
Received: by mail-we0-f171.google.com with SMTP id r3so260823wey.2
	for <emacs-orgmode@gnu.org>; Tue, 19 Mar 2013 11:54:49 -0700 (PDT)
In-Reply-To: <5136BC01.8060302@gmail.com> (Thomas Moyer's message of "Tue, 05
	Mar 2013 22:46:09 -0500")
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: <http://lists.gnu.org/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: Thomas Moyer <tommoyer@gmail.com>
Cc: emacs-orgmode@gnu.org

Hi Thomas,

Thomas Moyer <tommoyer@gmail.com> writes:

> What I want is a block agenda, using two agenda blocks. The first will
> *exclude* the entrys tagged as :chores: and the second will *include*
> any entry that is tagged with :chores:.
>
> Is there a way to accomplish this with tags, or maybe properties?

In your agenda custom command first block:

  ...
  (org-agenda-tag-filter ("+Tag"))
  ...

In your agenda custom command second block:

  ...
  (org-agenda-tag-filter ("-Tag"))
  ...

Not tested, but it should work -- not the -/+ before the tag itself,
that's what conditions tag filtering out/in.

HTH,

-- 
 Bastien