From: Bastien <firstname.lastname@example.org>
To: Thomas Alexander Gerds <email@example.com>
Subject: Re: org agenda extensions
Date: Sat, 12 Jan 2013 09:43:30 +0100 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
In-Reply-To: <email@example.com> (Thomas Alexander Gerds's message of "Sat, 12 Jan 2013 08:43:40 +0100")
Thomas Alexander Gerds <firstname.lastname@example.org> 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?
> 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
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.
next prev parent reply other threads:[~2013-01-12 8:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-11 10:47 org agenda extensions Thomas Alexander Gerds
2013-01-11 16:26 ` Bastien
2013-01-11 20:50 ` Thomas Alexander Gerds
2013-01-12 7:26 ` Bastien
2013-01-12 7:43 ` Thomas Alexander Gerds
2013-01-12 8:43 ` Bastien [this message]
2013-01-12 9:03 ` Thomas Alexander Gerds
2013-01-12 9:25 ` Bastien
2013-01-12 9:36 ` Thomas Alexander Gerds
2013-01-11 13:35 Thomas Alexander Gerds
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).