From: Carsten Dominik <carsten.dominik@gmail.com>
To: Eric S Fraga <e.fraga@ucl.ac.uk>
Cc: emacs-orgmode@gnu.org
Subject: Re: org-mode on sloooow computer
Date: Thu, 23 Apr 2009 22:26:22 +0200 [thread overview]
Message-ID: <5A8DAF72-27D1-4BC5-B70C-884E2F98620B@gmail.com> (raw)
In-Reply-To: <87hc0fe35v.fsf@eeepc.chemeng.ucl.ac.uk>
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
next prev parent reply other threads:[~2009-04-23 20:26 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-23 16:38 org-mode on sloooow computer Eric S Fraga
2009-04-23 19:15 ` Sven Bretfeld
2009-04-23 20:30 ` Carsten Dominik
2009-04-24 9:22 ` Eric S Fraga
2009-04-24 9:42 ` Carsten Dominik
2009-04-24 9:51 ` Eric S Fraga, Eric S Fraga
2009-04-24 10:25 ` Eric S Fraga
2009-04-24 11:35 ` Carsten Dominik
2009-04-24 12:51 ` Matthew Lundin
2009-04-24 15:27 ` Leo
2009-04-24 15:57 ` Nick Dokos
2009-04-24 16:22 ` Leo
2009-04-25 4:06 ` Samuel Wales
2009-04-23 20:26 ` Carsten Dominik [this message]
2009-04-23 22:10 ` Eric S Fraga, Eric S Fraga
2009-04-24 5:03 ` Carsten Dominik
2009-04-24 8:24 ` Eric S Fraga, Eric S Fraga
2009-04-24 9:01 ` Carsten Dominik
2009-04-24 13:37 ` Rainer Stengele
2009-04-24 13:49 ` Carsten Dominik
2009-04-24 15:47 ` Eric S Fraga, Eric S Fraga
2009-04-24 18:25 ` Carsten Dominik
2009-04-24 22:26 ` Eric S Fraga, Eric S Fraga
2009-04-25 3:51 ` Carsten Dominik
2009-04-25 8:19 ` Eric S Fraga, Eric S Fraga
2009-04-25 16:25 ` Bernt Hansen
2009-04-30 14:13 ` Carsten Dominik
2009-04-24 14:47 ` Carsten Dominik
2009-04-28 10:33 ` Rainer Stengele
2009-04-30 14:14 ` Carsten Dominik
2009-08-31 17:49 ` Daniel Martins
2009-08-31 18:02 ` Leo
2009-08-31 18:12 ` Daniel Martins
2009-08-31 18:41 ` Matt Lundin
2009-08-31 21:03 ` Daniel Martins
2009-08-31 21:11 ` Leo
2009-08-31 21:25 ` Daniel Martins
2009-09-01 4:20 ` Carsten Dominik
2009-09-01 13:15 ` Daniel Martins
2009-09-02 7:15 ` Carsten Dominik
2009-08-31 18:14 ` Matt Lundin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5A8DAF72-27D1-4BC5-B70C-884E2F98620B@gmail.com \
--to=carsten.dominik@gmail.com \
--cc=e.fraga@ucl.ac.uk \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).