emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Bastien <bzg@gnu.org>
To: Mark Edgington <edgimar@gmail.com>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: Arbitrary lisp functions in column-attributes
Date: Wed, 06 Nov 2013 09:20:13 +0100	[thread overview]
Message-ID: <87d2mdewca.fsf@bzg.ath.cx> (raw)
In-Reply-To: <CAMsBe8qDKDqm+U7eb4zLewrSgSjqBPOYZgnQ=WDAjfLUVf2Uig@mail.gmail.com> (Mark Edgington's message of "Wed, 6 Nov 2013 00:02:01 -0500")

Hi Mark,

Mark Edgington <edgimar@gmail.com> writes:

> Wouldn't the output of a function be something mutually exclusive with
> summary types?  In other words, a column can be defined to use a
> summary type, or it could be defined (with the proposed idea) as the
> output of a function, but not both at the same time.

So your proposal boils down to allowing arbitrary summary types,
with user defined functions?  If so, that seems useful and consistent
to me, I may have a look at some point.

> One other difference has to do with the "default value" when a
> property isn't defined -- org-collector sets the default value to 0,
> while for column-view it seems to be an empty string.  I therefore
> modified org-collector to make it easier to set this default value
> when defining a dynamic block:

Thanks -- can you submit the patch following the guidelines on
http://orgmode.org/worg/org-contribute.html (using git format-patch
and adding a commit message with a proper ChangeLog) ?

Thanks in advance,

-- 
 Bastien

  reply	other threads:[~2013-11-06 12:25 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-28 17:00 Arbitrary lisp functions in column-attributes Mark Edgington
2013-11-04 12:08 ` Bastien
2013-11-04 17:56   ` Mark Edgington
2013-11-05 21:06     ` Bastien
2013-11-06  5:02       ` Mark Edgington
2013-11-06  8:20         ` Bastien [this message]
  -- strict thread matches above, loose matches on Subject: below --
2013-10-31 16:41 Mark Edgington
2013-10-31 17:56 ` Aaron Ecay
2013-11-01 19:47   ` Mark Edgington
2013-11-03 22:38     ` Aaron Ecay
2013-11-04  3:09       ` Mark Edgington

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87d2mdewca.fsf@bzg.ath.cx \
    --to=bzg@gnu.org \
    --cc=edgimar@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).