From: Bastien <bzg@altern.org>
To: Thomas Alexander Gerds <tag@biostat.ku.dk>
Cc: emacs-orgmode@gnu.org
Subject: Re: org agenda extensions
Date: Sat, 12 Jan 2013 10:25:46 +0100 [thread overview]
Message-ID: <87k3riah2d.fsf@bzg.ath.cx> (raw)
In-Reply-To: <86k3ribwnf.fsf@biostat.ku.dk> (Thomas Alexander Gerds's message of "Sat, 12 Jan 2013 10:03:48 +0100")
Hi Thomas,
Thomas Alexander Gerds <tag@biostat.ku.dk> writes:
> I feel that your proposal to first create the agenda using the standard
> `org-agenda-format-item' function and then to replace all lines again,
> by calling a suitable function added to `org-agenda-finalize-hook' is
> not very efficient.
Imagine you have a 10000 items agenda file, and you produce a 100
items agenda view. Your method would slow down checking 10000 items
to display properties for 100 items, while my method would slow down
the display of the 100 already available items. So its about 100x
faster.
Please check both methods and let us know what performance you
observe.
> but, since you agree that when `org-agenda-property-list' is nil no harm
> is done, and if your objection mostly is about the name, then how about
>
> `org-agenda-overriding-format-item-function'
My objection is about the method.
> ps: I would volunteer to assist users who copy stuff from the web and of
> course also deliver documentation and examples for
> `org-agenda-property-list'.
Thanks for this -- but as I said, there are performance issues and
design issues (not introducing formatting properties within
org-scan-tags.)
Best,
--
Bastien
next prev parent reply other threads:[~2013-01-12 9:25 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
2013-01-12 9:03 ` Thomas Alexander Gerds
2013-01-12 9:25 ` Bastien [this message]
2013-01-12 9:36 ` Thomas Alexander Gerds
-- strict thread matches above, loose matches on Subject: below --
2013-01-11 13:35 Thomas Alexander Gerds
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=87k3riah2d.fsf@bzg.ath.cx \
--to=bzg@altern.org \
--cc=emacs-orgmode@gnu.org \
--cc=tag@biostat.ku.dk \
/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).