emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Mark Edgington <edgimar@gmail.com>
To: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: Arbitrary lisp functions in column-attributes
Date: Fri, 1 Nov 2013 15:47:05 -0400	[thread overview]
Message-ID: <CAMsBe8oFqA-k0Ski80tVpR5uWZo0EXZWRGYRTbNDdVHyXYAKQg@mail.gmail.com> (raw)
In-Reply-To: <87li19b9yy.fsf@gmail.com>

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 <aaronecay@gmail.com> 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

next prev parent reply	other threads:[~2013-11-01 19:47 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-31 16:41 Arbitrary lisp functions in column-attributes Mark Edgington
2013-10-31 17:56 ` Aaron Ecay
2013-11-01 19:47   ` Mark Edgington [this message]
2013-11-03 22:38     ` Aaron Ecay
2013-11-04  3:09       ` Mark Edgington
  -- strict thread matches above, loose matches on Subject: below --
2013-10-28 17:00 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

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=CAMsBe8oFqA-k0Ski80tVpR5uWZo0EXZWRGYRTbNDdVHyXYAKQg@mail.gmail.com \
    --to=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

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).