From: Matthew Lundin <mdl@imapmail.org>
To: Jason Jackson <jason@cvk.ca>
Cc: emacs-orgmode@gnu.org
Subject: Re: [PERF] Slow Org Agenda Custom Commands
Date: Sun, 11 Jan 2009 20:34:02 -0600 [thread overview]
Message-ID: <m2mydxp811.fsf@fastmail.fm> (raw)
In-Reply-To: <2df907590901101608j16f2c5a9xe5bcf5d0c85a75ff@mail.gmail.com> (Jason Jackson's message of "Sun\, 11 Jan 2009 11\:08\:26 +1100")
Hi Jason,
"Jason Jackson" <jason@cvk.ca> writes:
> I'm using the following org agenda custom command, with a relatively small
> org-mode text file, and agenda creation is taking around 3-4 seconds, it
> becomes unbearably worse if I modify stuck-projects to also use properties
> searches)
>
> Is there anything I can change to speed up the commands execution; or
> developer changes to org-mode?
>
> (setq org-agenda-custom-commands
> '(("h" "Next Action"
> (
> (agenda ""
> ((org-agenda-ndays 1)
> (org-agenda-time-grid '())
> (org-deadline-warning-days 5)
> (org-agenda-sorting-strategy '(time-up priority-down))
> (org-agenda-skip-deadline-if-done t)
> (org-agenda-overriding-header "Today's Agenda: ")
> ))
> ;;;;;;; SLOW COMMAND #1
> (tags "@HOME-habit-__IGNORE-SCHEDULED>\"<2000-01-01>\"/TODO|BLOCKED|
> SUBMIT"
> ((org-agenda-sorting-strategy '(priority-down))
> (org-agenda-overriding-header "Unscheduled Todo
> (@Home): ")
> ))
As you suggest, any searches for properties other than TODO, LEVEL,
and CATEGORY can be quite slow.
Have you considered using a todo search and then using secondary
filtering to limit by tag. This would enable you to use either of the
following variables:
- org-agenda-todo-ignore-with-date
- org-agenda-todo-ignore-scheduled
Best,
Matt
next prev parent reply other threads:[~2009-01-12 2:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-11 0:08 [PERF] Slow Org Agenda Custom Commands Jason Jackson
2009-01-12 2:34 ` Matthew Lundin [this message]
2009-01-12 5:56 ` Jason Jackson
2009-01-18 19:50 ` Carsten Dominik
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=m2mydxp811.fsf@fastmail.fm \
--to=mdl@imapmail.org \
--cc=emacs-orgmode@gnu.org \
--cc=jason@cvk.ca \
/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).