From mboxrd@z Thu Jan 1 00:00:00 1970 From: "George Pearson" Subject: Re: filtering the weekly agenda Date: Wed, 15 Oct 2008 14:49:05 -0400 Message-ID: <48F602E1.12613.DFB6D0@george.canals.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7BIT Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1KqBR2-0005if-Ng for emacs-orgmode@gnu.org; Wed, 15 Oct 2008 14:49:28 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1KqBR0-0005h9-8V for emacs-orgmode@gnu.org; Wed, 15 Oct 2008 14:49:27 -0400 Received: from [199.232.76.173] (port=47245 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KqBR0-0005h2-59 for emacs-orgmode@gnu.org; Wed, 15 Oct 2008 14:49:26 -0400 Received: from shared9.whbdns.com ([75.126.177.135]:45839) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1KqBQw-00038J-W9 for emacs-orgmode@gnu.org; Wed, 15 Oct 2008 14:49:25 -0400 Received: from c-24-128-69-40.hsd1.nh.comcast.net ([24.128.69.40] helo=[192.168.1.103]) by shared9.whbdns.com with esmtpsa (TLSv1:DES-CBC3-SHA:168) (Exim 4.69) (envelope-from ) id 1KqBQv-0003LP-F2 for emacs-orgmode@gnu.org; Wed, 15 Oct 2008 18:49:21 +0000 In-reply-to: <48F5CCCE.5278.C7A46@george.canals.com> Content-description: Mail message body 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: emacs-orgmode@gnu.org OK, I now have a way to do this. I searched this list again with different search terms and found a posting that I had not seen before. This gave me the idea of using a second org file, into which I would put my recurring tasks. I've now done this, and after customizing org-global-properties (for "effort") and org-columns-default-format (to show "effort"), all seems to be working as I wanted. (I had previously used in-file definitions of these, but that did not work across two org files.)