emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Carsten Dominik <carsten.dominik@gmail.com>
To: "Andrew J. Korty" <ajk@iu.edu>
Cc: Org Mode <emacs-orgmode@gnu.org>
Subject: Re: Speeding up agenda display
Date: Sat, 2 Jan 2010 20:37:45 +0100	[thread overview]
Message-ID: <EAB698C9-F904-49A7-A070-F2566DB7953A@gmail.com> (raw)
In-Reply-To: <FF9E3491-EC4D-4E5C-9B7E-059615FFB9E1@iu.edu>


On Jan 2, 2010, at 3:38 PM, Andrew J. Korty wrote:

> On Jan 2, 2010, at 02:50 , Carsten Dominik wrote:
>
>> You can shave off another .5 seconds by pressing the selection key
>> faster - Org spends 0.46 seconds to wait for your keypress :-)
>
> Good point. :-)
>
> I optimized things a bit more by caching skip positions and  
> schedule, deadline, and tag data for each point a skip function is  
> called in a hash.  An example hash value might be
>
>  (((due-soon . t) (started . nil) (tagged-for-home . t)) . skip- 
> position)
>
> These savings add up when you have several slightly differing  
> agendas in a block agenda.

Hi Andrew,

that is interesting.  I have been thinking about caching often
but always stopped implementing it because, being a plain text
system, there is always the possibility that thinks are being
changed behind the back of the cache.  How are you handling
updating the cache?

- Carsten

  reply	other threads:[~2010-01-02 19:37 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-30 19:06 Speeding up agenda display Andrew J. Korty
2009-12-30 19:20 ` Carsten Dominik
2009-12-30 19:40   ` Andrew J. Korty
2009-12-31  7:45     ` Carsten Dominik
2009-12-31 17:46       ` Andrew J. Korty
2010-01-02  7:50         ` Carsten Dominik
2010-01-02 14:38           ` Andrew J. Korty
2010-01-02 19:37             ` Carsten Dominik [this message]
2010-01-03  3:40               ` Andrew J. Korty
2010-01-03 12:42                 ` 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=EAB698C9-F904-49A7-A070-F2566DB7953A@gmail.com \
    --to=carsten.dominik@gmail.com \
    --cc=ajk@iu.edu \
    --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
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).