From mboxrd@z Thu Jan 1 00:00:00 1970 From: Marcelo de Moraes Serpa Subject: Cached agenda views? Date: Thu, 6 Sep 2012 08:54:04 -0500 Message-ID: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=90e6ba25dc2f0c56ea04c908d372 Return-path: Received: from eggs.gnu.org ([208.118.235.92]:36598) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1T9cXA-0000mu-Qj for emacs-orgmode@gnu.org; Thu, 06 Sep 2012 09:54:22 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1T9cWz-0000WY-Se for emacs-orgmode@gnu.org; Thu, 06 Sep 2012 09:54:16 -0400 Received: from mail-ie0-f169.google.com ([209.85.223.169]:54461) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1T9cWz-0000Vw-M1 for emacs-orgmode@gnu.org; Thu, 06 Sep 2012 09:54:05 -0400 Received: by iec9 with SMTP id 9so3532721iec.0 for ; Thu, 06 Sep 2012 06:54:04 -0700 (PDT) List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Org Mode --90e6ba25dc2f0c56ea04c908d372 Content-Type: text/plain; charset=ISO-8859-1 Hi list, It's a known fact that the more files you put into the agenda, the more likely it is to become slower. I've started using Memacs a few weeks ago, and my agenda is still very useable, but significantly slower than before (due to the big amount of temporal data being processed from my gmail emails and git logs). I was wondering if it would be possible to NOT regenerate the agenda everytime. I think this would mean parsing the org files and dumping the elisp objects created somehow. This way, when visiting the agenda again, it would be loaded from the objects dump and would not go through the parsing of all the agenda files again, unless forced by the user; or within a specific time, via a cron or internal emacs timer. This would also, in theory, allow the agenda to be constantly regenerated in a background worker process. What do you think? Cheers, - Marcelo. --90e6ba25dc2f0c56ea04c908d372 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi list,

It's a known fact that the more files you p= ut into the agenda, the more likely it is to become slower. I've starte= d using Memacs a few weeks ago, and my agenda is still very useable, but si= gnificantly slower than before (due to the big amount of temporal data bein= g processed from my gmail emails and git logs).

I was wondering if it would be possible to NOT regenera= te the agenda everytime.=A0

I think this would mea= n parsing the org files and dumping the elisp objects created somehow. This= way, when visiting the agenda again, it would be loaded from the objects d= ump and would not go through the parsing of all the agenda files again, unl= ess forced by the user; or within a=A0specific=A0time, via a cron or intern= al emacs timer. This would also, in theory, allow the agenda to be constant= ly regenerated in a background worker process.

What do you think?

Cheers,

- Marcelo.



--90e6ba25dc2f0c56ea04c908d372--