From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Sebastien Vauban" Subject: Re: How to improve Org startup time? Date: Wed, 30 Jan 2013 23:36:37 +0100 Message-ID: <86sj5iwb62.fsf@somewhere.org> References: <867gmviujs.fsf@somewhere.org> <87txpzoagt.fsf@bzg.ath.cx> <86d2wndo4x.fsf@somewhere.org> <874nhyab4s.fsf@bzg.ath.cx> Mime-Version: 1.0 Content-Type: text/plain Return-path: 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-mXXj517/zsQ@public.gmane.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org-mXXj517/zsQ@public.gmane.org To: emacs-orgmode-mXXj517/zsQ@public.gmane.org Hi Bastien, Bastien wrote: > put your .emacs on diet :) More seriously, I would start by checking > org-agenda-to-appt documentation. It should be on your system. If it is not, > check online. I tried to filter to only "timestamp" entries with the following: #+begin_src emacs-lisp (org-agenda-to-appt nil nil '(:timestamp)) #+end_src But that does not work -- no error, but no event added to the appt list! I must not understand the &rest parameter, I guess. > That's what really slows down your config. Yes and no. Yes, because it's currently run at startup time, even if I put that command inside an eval-after-load "org-agenda" (as `org-agenda' is ultimately called when `org-clock-persist' is set). No, because no running that does not change the fact that, sooner or later, the Org agenda files will have to be loaded and scanned through. Not having that done at startup simply _add_ another 16 seconds delay to the computation of the first agenda view; not a gain IMO. > Then, when this is done, I would try to use only those hooks that are really > necessary. Are you referring to something in particular? Best regards, Seb -- Sebastien Vauban