From: Bastien <firstname.lastname@example.org> To: Marcel van der Boom <email@example.com> Cc: firstname.lastname@example.org Subject: Re: Logbook drawer entries make editing very slow Date: Thu, 18 Apr 2013 12:56:50 +0200 [thread overview] Message-ID: <email@example.com> (raw) In-Reply-To: <firstname.lastname@example.org> (Marcel van der Boom's message of "Wed, 20 Feb 2013 09:03:13 +0100") Hi Marcel, Marcel van der Boom <email@example.com> writes: > I'm using habit-style items a lot in my 'org' routine. A typical entry > would look like this: > > #+BEGIN_SRC org > *** TODO Do something daily > SCHEDULED: <2013-02-20 wo .+1d> > :LOGBOOK: > - State "DONE" from "TODO" [2013-02-19 di 14:01] > - State "DONE" from "TODO" [2013-02-17 zo 12:39] > ... > [lots of entries here] > ... > - State "DONE" from "TODO" [2010-02-25 Thu 13:51] > - State "DONE" from "TODO" [2010-02-10 Wed 15:19] > :END: > :PROPERTIES: > :STYLE: habit > :LAST_REPEAT: [2013-02-19 di 14:01] > :CREATED: <2011-03-25 vr 12:33> > :END: > ...Some description... > #+END > > I have all habits in a file habits.org which is part of the > 'org-agenda-files' list. > > When editing entries in the habits.org file, for example changing the > header, emacs CPU using goes to 100% and every keystroke takes 5-10 > seconds. (org-at-item-p) can be very expensive, because it calls (org-list-in-valid-context-p) which is also expensive and clearly not optimized for every list movements. I found out that the use is still acceptable for 1000-2000 list items, so I won't fix this right now, but something to keep under the radar, yes. In the meantime, cleaning out the logs sometimes is the only suggestion I can make. Thanks for reporting this, -- Bastien
prev parent reply other threads:[~2013-04-18 10:56 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-02-20 8:03 Marcel van der Boom 2013-04-18 10:56 ` Bastien [this message]
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 \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: Logbook drawer entries make editing very slow' \ /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
Code repositories for project(s) associated with this 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).