From mboxrd@z Thu Jan 1 00:00:00 1970 From: Carsten Dominik Subject: Re: org-mode on sloooow computer Date: Thu, 23 Apr 2009 22:26:22 +0200 Message-ID: <5A8DAF72-27D1-4BC5-B70C-884E2F98620B@gmail.com> References: <87hc0fe35v.fsf@eeepc.chemeng.ucl.ac.uk> Mime-Version: 1.0 (Apple Message framework v930.3) 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 1Lx5V9-0007eQ-A5 for emacs-orgmode@gnu.org; Thu, 23 Apr 2009 16:26:31 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Lx5V4-0007bY-Hx for emacs-orgmode@gnu.org; Thu, 23 Apr 2009 16:26:30 -0400 Received: from [199.232.76.173] (port=56722 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Lx5V4-0007bT-Bf for emacs-orgmode@gnu.org; Thu, 23 Apr 2009 16:26:26 -0400 Received: from mail-ew0-f162.google.com ([209.85.219.162]:41409) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Lx5V3-0003Jl-Uk for emacs-orgmode@gnu.org; Thu, 23 Apr 2009 16:26:26 -0400 Received: by ewy6 with SMTP id 6so738446ewy.42 for ; Thu, 23 Apr 2009 13:26:24 -0700 (PDT) In-Reply-To: <87hc0fe35v.fsf@eeepc.chemeng.ucl.ac.uk> 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: Eric S Fraga Cc: emacs-orgmode@gnu.org 8-10 seconds, that is a lot. On Apr 23, 2009, at 6:38 PM, Eric S Fraga wrote: > Hi, > > I've been using org-mode more and more and, unsurprisingly, it gets > slower and slower due to the increasing amount of data org-mode has to > parse and evaluate. On my desktop systems (and on my full-featured > laptop), this is not yet a problem [1]. On my little netbook (the > original eee pc from Asus which is used primarily for org-mode!), > there > are some annoyances due to the much slower cpu. I'd like to mention > one > that I believe should be easy to fix (for those with much more elisp > expertise than my own...): > > When in agenda view, when org-agenda-goto-date is invoked (typically > with 'j'), the agenda view is regenerated for today's date > regardless of > which date I am currently viewing, before allowing me to input a date. I don't think I can reproduce this. > This seems an unnecessary step and I wonder whether it would be easy > to > change? On my Asus, regenerating the view for my current date (with > todos, scheduled items, etc) takes at least 8 seconds! When I'm > checking out various dates in the future for possible meetings or > whatever, having to wait up to 10 seconds each time I look at a > different date gets a little frustrating. > > I've had a look at org-agenda-goto-date and org-read-date but it's not > immediately apparent to me why the current date's view has to be > generated. - Carsten