emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Carsten Dominik <carsten.dominik@gmail.com>
To: Adam Spiers <orgmode@adamspiers.org>
Cc: org-mode mailing list <emacs-orgmode@gnu.org>
Subject: Re: FR: per-session caching of *Org Agenda* buffer
Date: Tue, 15 Jan 2008 12:48:16 +0100	[thread overview]
Message-ID: <1BE9BE1C-CCD3-4D41-A643-D06ACE4085AB@gmail.com> (raw)
In-Reply-To: <20071229231323.GA20947@atlantic.linksys.moosehall>


On Dec 30, 2007, at 12:13 AM, Adam Spiers wrote:

> For me at least, generation of the *Org Agenda* buffer takes a good
> 1.5 seconds or so each time, on a pretty decent machine.  This isn't
> too bad, and is at least in part due to my tendency for Structured
> Procrastination which leads to very long TODO.org files (and lots of
> posts to this list ;-)
>
> However, I think it would be pretty easy to smash this 1.5s down to
> 0.01s or quicker in the majority of cases, simply by implementing a
> basic Makefile-like awareness of all the dependencies which form
> inputs into the process of generating the *Org Agenda* buffer.  Then,
> while the first generation after emacs startup would still be slow,
> any subsequent generation would be instant as long as none of the
> dependent inputs (agenda files, custom variables etc.,
> day/week/month/grid/log etc. view modes) had changed since the last
> generation, since it would simply be a matter of redisplaying the
> existing *Org Agenda* buffer.
>
> It sounds doable to me, and in fact pretty easy.  The only tricky bit
> might be figuring out whether any relevant variables had changed.  Are
> there any other inputs to the generation process I've missed?

Hi Adam,

yes, Org-mode is slow an creating agendas from long files.  First of  
all,
have you compiled org.el?  That might already help.

2nd, I don't think at all that this is simple, unless you keep  
redisplaying
the exact same agenda all the time, in which case it is easier to just
switch back to the agenda buffer.

Improving the speed of agenda creation would require an internal  
representation
of all the data and deriving the agenda stuff from that.  I don't want  
to
go there, so why do you think this is simple?

- Carsten

>
>
>
> _______________________________________________
> Emacs-orgmode mailing list
> Remember: use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode

      reply	other threads:[~2008-01-15 11:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-29 23:13 FR: per-session caching of *Org Agenda* buffer Adam Spiers
2008-01-15 11:48 ` Carsten Dominik [this message]

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=1BE9BE1C-CCD3-4D41-A643-D06ACE4085AB@gmail.com \
    --to=carsten.dominik@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=orgmode@adamspiers.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).