From mboxrd@z Thu Jan 1 00:00:00 1970 From: Carsten Dominik Subject: Re: Speeding up agenda display Date: Sun, 3 Jan 2010 13:42:41 +0100 Message-ID: <9EB0AABC-AF4A-4A86-9F3C-2420B742086B@gmail.com> References: <4D8BBF51-8F5A-47E4-99F4-603E349BDD99@gmail.com> <8CAD865A-01AA-49B7-AEE5-1FF088865282@gmail.com> <4CA37E79-ADED-4127-A358-218B6B522F05@iu.edu> <938BEB0E-6A34-44B5-9164-CE26105E3EEB@gmail.com> Mime-Version: 1.0 (Apple Message framework v936) Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NRPnG-00021c-QP for emacs-orgmode@gnu.org; Sun, 03 Jan 2010 07:42:50 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NRPnC-000212-OU for emacs-orgmode@gnu.org; Sun, 03 Jan 2010 07:42:50 -0500 Received: from [199.232.76.173] (port=53197 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NRPnC-00020z-Lq for emacs-orgmode@gnu.org; Sun, 03 Jan 2010 07:42:46 -0500 Received: from mail-ew0-f224.google.com ([209.85.219.224]:53334) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1NRPnC-0002iB-Cr for emacs-orgmode@gnu.org; Sun, 03 Jan 2010 07:42:46 -0500 Received: by ewy24 with SMTP id 24so17062867ewy.26 for ; Sun, 03 Jan 2010 04:42:44 -0800 (PST) In-Reply-To: List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: "Andrew J. Korty" Cc: Org Mode On Jan 3, 2010, at 4:40 AM, Andrew J. Korty wrote: > On Jan 2, 2010, at 14:37 , Carsten Dominik wrote: > >> 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? > > Well, I'm only using the cache while org-agenda is running -- it > doesn't persist beyond that. So I don't have to worry about the > agenda files changing, but I get no added benefit for subsequent > agenda builds. Ah, OK. thanks. - Carsten