From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bastien Subject: Re: properties in agenda prefix Date: Wed, 18 Aug 2010 16:43:36 +0200 Message-ID: <87k4nnzvs6.fsf@altern.org> References: <871v9wxnt0.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from [140.186.70.92] (port=54369 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OlmFR-0004Dk-QK for emacs-orgmode@gnu.org; Wed, 18 Aug 2010 13:16:27 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1OlmFJ-0003ae-Aa for emacs-orgmode@gnu.org; Wed, 18 Aug 2010 13:16:21 -0400 Received: from mail-wy0-f169.google.com ([74.125.82.169]:47649) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1OlmFJ-0003aP-67 for emacs-orgmode@gnu.org; Wed, 18 Aug 2010 13:16:13 -0400 Received: by wyg36 with SMTP id 36so1089226wyg.0 for ; Wed, 18 Aug 2010 10:16:12 -0700 (PDT) In-Reply-To: (Skip Collins's message of "Wed, 18 Aug 2010 08:03:54 -0400") 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: Skip Collins Cc: emacs-orgmode@gnu.org Hi, Skip Collins writes: >> What property would you find useful to have and why? > > CUSTOM_ID could be handy right away. If arbitrary properties were > accessible in agenda prefix, it would enable very flexible agenda > constructs. Consider a setup in which headlines are given a tracking > number that can be used as a reference number outside of org. The > reference number would naturally be a property, not a tag. To get a > nice list that includes the reference number, it must be assigned to > CATEGORY. > > Consider also a group agenda in which items are flagged in the prefix > with the names of their owners. Again, the names must now be assigned > to CATEGORY. Yes, I agree `org-agenda-prefix-format' could use a more general syntax, e.g. allow user-defined properties. > As a design goal, I think would it make sense for agenda and column > modes to have some overlapping features and syntax, including the > ability to access properties. I grasp the general idea but a more concrete use-case would help here again... thanks! -- Bastien