From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bastien Subject: Re: org agenda extensions Date: Sat, 12 Jan 2013 09:43:30 +0100 Message-ID: <87fw26u6z1.fsf@bzg.ath.cx> References: <87zk0f1yas.fsf@bzg.ath.cx> <86vcb3xx44.fsf@biostat.ku.dk> <87mwweeuaz.fsf@bzg.ath.cx> <86sj66c0cz.fsf@biostat.ku.dk> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([208.118.235.92]:49426) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Ttwo5-0002fa-GD for emacs-orgmode@gnu.org; Sat, 12 Jan 2013 03:51:16 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Ttwo2-000773-Un for emacs-orgmode@gnu.org; Sat, 12 Jan 2013 03:51:13 -0500 Received: from mail-wg0-f44.google.com ([74.125.82.44]:39546) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Ttwo2-00076x-OV for emacs-orgmode@gnu.org; Sat, 12 Jan 2013 03:51:10 -0500 Received: by mail-wg0-f44.google.com with SMTP id dr12so1166071wgb.11 for ; Sat, 12 Jan 2013 00:51:10 -0800 (PST) In-Reply-To: <86sj66c0cz.fsf@biostat.ku.dk> (Thomas Alexander Gerds's message of "Sat, 12 Jan 2013 08:43:40 +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: Thomas Alexander Gerds Cc: emacs-orgmode@gnu.org Hi Thomas, Thomas Alexander Gerds writes: > 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? Right. > also, it certainly requires some insights to write > org-agenda-overriding-agenda-format which could display non-special (`org-agenda-overriding-agenda-format' is a confusing name IMHO.) > properties. hence only a user who knows what she/he is doing would run > into this problem. Many users just copy stuff from the web, and some are not really knowing what they do. > anyway, could you propose a different approach to get this > extension? You can write a function for `org-agenda-finalize-hook' which would go through the agenda lines, get the properties and display them. That's a far better approach. > ps: one limitation of org-agenda-columns seems to be that columns > cannot be activated in two different agenda buffers simulaneously. Yes, we can work on this. Best, -- Bastien