From mboxrd@z Thu Jan 1 00:00:00 1970 From: Carsten Dominik Subject: Re: Release 6.10 Date: Fri, 24 Oct 2008 17:15:09 +0200 Message-ID: References: Mime-Version: 1.0 (Apple Message framework v929.2) Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1KtONj-00022q-6h for emacs-orgmode@gnu.org; Fri, 24 Oct 2008 11:15:19 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1KtONi-00022Q-5r for emacs-orgmode@gnu.org; Fri, 24 Oct 2008 11:15:18 -0400 Received: from [199.232.76.173] (port=54251 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KtONh-00022N-Vx for emacs-orgmode@gnu.org; Fri, 24 Oct 2008 11:15:18 -0400 Received: from ik-out-1112.google.com ([66.249.90.177]:38298) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1KtONh-0006OX-Bh for emacs-orgmode@gnu.org; Fri, 24 Oct 2008 11:15:18 -0400 Received: by ik-out-1112.google.com with SMTP id c21so725591ika.2 for ; Fri, 24 Oct 2008 08:15:12 -0700 (PDT) In-Reply-To: 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: Manish Cc: emacs-orgmode List Hi Manish, this works just fine for me, can you try to explain again what exactly does not work? - Carsten On Oct 23, 2008, at 4:46 PM, Manish wrote: > On Thu, Oct 23, 2008 at 1:03 PM, Carsten Dominik wrote: > [snip] >> Enhancements to secondary agenda filtering >> ------------------------------------------ >> >> This is, I believe, becoming a killer feature. It allows you >> to define fewer and more general custom agenda commands, and >> then to do the final narrowing to specific tasks you are >> looking for very quickly, much faster than calling a new >> agenda command. >> >> If you have not tries this yet, you should! >> >> * You can now refining the current filter by an additional criterion >> When filtering an existing agenda view with `/', you can >> now narrow down the existing selection by an additional >> condition. Do do this, use `\' instead of `/' to add the >> additional criterion. You can also press `+' or `-' after >> `/' to add a positive or negative condition. A condition >> can be a TAG, or an effort estimate limit, see below. > [snip] > > Thanks for enhancing this already awesome feature. > >> I use this mostly to get rid of TODAY and NEXT tags which I >> apply to select an entry for execution in the near future, >> which I often prefer to specific time scheduling. > > I like this. I end up pushing many of the tasks forward each day. I > think it's better to use standard agenda for timed tasks > (appointments, deadlines etc.) and add another block for tasks tagged > for today and next actions (do anytime tasks.) So I created an agenda > view that has standard agenda, a block of tags query to include tasks > tagged "Today" and another block with tasks tagged "Next". But it > seems filter applies only to the standard agenda block and does not > show any task from the other two blocks. Can it be done at all? > > -- Manish