From: Puneeth Chaganti <punchagan@gmail.com>
To: Lawrence Bottorff <borgauf@gmail.com>
Cc: Nick Dokos <ndokos@gmail.com>, emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: New ELPA addition bogs down Emacs
Date: Thu, 12 Feb 2015 04:04:47 +0530 [thread overview]
Message-ID: <CALnw1fTAdw8d5LxLhFbGJsxJsR+1+OL+AQabZyWnhwfYY2uW9Q@mail.gmail.com> (raw)
In-Reply-To: <CAFAhFSVYMjKYoAfKwmRgT5sKb8uKPpkA1cRM4r5d2Rkcqu+rjA@mail.gmail.com>
On Thu, Feb 12, 2015 at 3:26 AM, Lawrence Bottorff <borgauf@gmail.com> wrote:
> Changing to #+STARTUP: showeverything did the trick . . . although I don't
> know why. Why?
One of the reasons I discovered recently was this inconspicuous change
(around v8.2.6) [1], though this may or may not be what is happening
for you.
Calling `org-overview` on large files takes a lot of time and is CPU
intensive. #+STARTUP: showeverything basically turns off a call to
this, when a file is opened -- so, the file is displayed with
everything shown.
Before this change, `org-overview` had a call to `recenter`, and when
a file was opened by visiting `org-agenda`, the file would be opened
in a buried (not currently visible) buffer. This would case `recenter`
to error out (since it expects the buffer to be current), there by
causing an error in `org-overview`. Co-incidentally, this saved all
the CPU cycles. This change removed this "broken" call to `recenter`.
[1] - http://orgmode.org/w/?p=org-mode.git;a=commitdiff;h=b88c5464db2cb0d90d4f30e43b5e08d2b1c1fcea;hp=8cc4e09950594b2abec2502e9218318570595ac5
-- Puneeth
prev parent reply other threads:[~2015-02-11 22:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-11 19:35 New ELPA addition bogs down Emacs Lawrence Bottorff
2015-02-11 20:07 ` Grant Rettke
2015-02-11 21:13 ` Nick Dokos
2015-02-11 21:56 ` Lawrence Bottorff
2015-02-11 22:34 ` Puneeth Chaganti [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 \
--in-reply-to=CALnw1fTAdw8d5LxLhFbGJsxJsR+1+OL+AQabZyWnhwfYY2uW9Q@mail.gmail.com \
--to=punchagan@gmail.com \
--cc=borgauf@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=ndokos@gmail.com \
/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).