From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Alexander Gerds Subject: Re: org agenda extensions Date: Sat, 12 Jan 2013 08:43:40 +0100 Message-ID: <86sj66c0cz.fsf@biostat.ku.dk> References: <87zk0f1yas.fsf@bzg.ath.cx> <86vcb3xx44.fsf@biostat.ku.dk> <87mwweeuaz.fsf@bzg.ath.cx> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([208.118.235.92]:38458) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Ttvkw-0005oY-HC for emacs-orgmode@gnu.org; Sat, 12 Jan 2013 02:44:00 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Ttvko-0006Mh-7L for emacs-orgmode@gnu.org; Sat, 12 Jan 2013 02:43:54 -0500 Received: from mail-la0-f43.google.com ([209.85.215.43]:43165) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Ttvkn-0006LZ-W7 for emacs-orgmode@gnu.org; Sat, 12 Jan 2013 02:43:46 -0500 Received: by mail-la0-f43.google.com with SMTP id eg20so2471741lab.30 for ; Fri, 11 Jan 2013 23:43:44 -0800 (PST) In-Reply-To: <87mwweeuaz.fsf@bzg.ath.cx> (Bastien's message of "Sat, 12 Jan 2013 08:26:12 +0100") List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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 Cc: emacs-orgmode@gnu.org Hi Bastien thanks for looking into this! I understand your general point of view. however, the proposed changes would only slow down agenda creating if org-agenda-property-list is set, right? also, it certainly requires some insights to write org-agenda-overriding-agenda-format which could display non-special properties. hence only a user who knows what she/he is doing would run into this problem. anyway, could you propose a different approach to get this extension? I could write a new function org-scan-properties, but that would require several changes in org-agenda ... thanks again, Thomas ps: one limitation of org-agenda-columns seems to be that columns cannot be activated in two different agenda buffers simulaneously. Bastien writes: > Hi Thomas, > > I've reviewed the proposed change. > > `org-scan-tags' already does many things beyond its name, because > a "tag" here is really a "match", which can include properties -- > see `org-make-tags-matcher' for how the "tags match" is built from > properties).=20=20 > > This is handy for tags view and `org-sparse-tree'. > > In agenda, we don't need to display the properties that are part of > the tag match, as they are part of the agenda headline already. > > I don't think we should let the user add properties to the agenda > lines this way, as (1) it would make the name `org-scan-tags' even > more confusing and (2) it would probably slow down agenda creating > a lot -- `org-scan-tags' is the bottleneck for speed here. > > Also, the whole purpose of `org-agenda-columns' is precisely to see > properties in agenda, so I'd rather let the user interactively decide > if he wants to take the extra mile (and time) or not. > > 'hope this sounds reasonable enough. > > And thanks anyway for this! -- Thomas A. Gerds -- Assoc. Prof. Department of Biostatistics University of Copenhagen, =D8ster Farimagsgade 5, 1014 Copenhagen, Denmark Office: CSS-15.2.07 (Gamle Kommunehospital) tel: 35327914 (sec: 35327901)=20