From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mark Edgington Subject: Re: Arbitrary lisp functions in column-attributes Date: Fri, 1 Nov 2013 15:47:05 -0400 Message-ID: References: <87li19b9yy.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:42786) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VcKh0-00059V-22 for emacs-orgmode@gnu.org; Fri, 01 Nov 2013 15:47:38 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VcKgz-0002bF-3O for emacs-orgmode@gnu.org; Fri, 01 Nov 2013 15:47:38 -0400 Received: from mail-ob0-x234.google.com ([2607:f8b0:4003:c01::234]:52476) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VcKgy-0002b3-US for emacs-orgmode@gnu.org; Fri, 01 Nov 2013 15:47:37 -0400 Received: by mail-ob0-f180.google.com with SMTP id wo20so4921541obc.25 for ; Fri, 01 Nov 2013 12:47:35 -0700 (PDT) In-Reply-To: <87li19b9yy.fsf@gmail.com> 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: emacs-orgmode Hi Aaron, I hadn't actually foreseen using it for column-view so much, but rather for a dynamic-block which generates a column-view of a tree. These are, as far as I understand, read-only. I don't think it would work well with read-write column-views, so if such a function were defined in the :COLUMNS: property, it should either be ignored and not displayed in the R/W column-view, or it could be displayed if there were some way of ensuring that the associated column was R/O. Maybe others have a better idea on how to handle this? I am somewhat partial to the scheme used in org-collector, where columns are defined at the beginning of a dynamic block, and not in the original tree. This way you can have several different dynamic blocks which summarize the tree-data in different ways. It would also allow the column-definitions defined in the tree to be used only for the R/W column-view of that tree. Regards, Mark On Thu, Oct 31, 2013 at 1:56 PM, Aaron Ecay wrote: > Hi Mark, > > This seems like an intriguing idea. I have just one question: how would > this interact with editing in column view? Would function-valued > property columns be read only? Or do you have something different in > mind? > > -- > Aaron Ecay