From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Andrew J. Korty" Subject: Re: Speeding up agenda display Date: Sat, 2 Jan 2010 22:40:43 -0500 Message-ID: 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 v1077) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NRHKq-0006Wx-QD for emacs-orgmode@gnu.org; Sat, 02 Jan 2010 22:40:56 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NRHKl-0006W7-UF for emacs-orgmode@gnu.org; Sat, 02 Jan 2010 22:40:56 -0500 Received: from [199.232.76.173] (port=55762 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NRHKl-0006W4-Rs for emacs-orgmode@gnu.org; Sat, 02 Jan 2010 22:40:51 -0500 Received: from belushi.uits.indiana.edu ([129.79.1.188]:33533) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1NRHKk-00060n-L4 for emacs-orgmode@gnu.org; Sat, 02 Jan 2010 22:40:51 -0500 Received: from mail-relay.iu.edu (candy.uits.indiana.edu [129.79.1.201]) by belushi.uits.indiana.edu (8.14.2/8.13.8/IU Messaging Team) with ESMTP id o033ej9i030194 for ; Sat, 2 Jan 2010 22:40:45 -0500 Received: from [10.0.1.3] (cpe-75-184-122-216.indy.res.rr.com [75.184.122.216]) (authenticated bits=0) by mail-relay.iu.edu (8.14.2/8.13.8/IU Messaging Team Submission) with ESMTP id o033ehwA003139 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for ; Sat, 2 Jan 2010 22:40:45 -0500 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: Org Mode 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. ajk=