From: Eli Zaretskii <eliz@gnu.org>
To: Gerald Wildgruber <wildgruber@tu-berlin.de>
Cc: emacs-devel@gnu.org
Subject: Re: follow-mode: extremely slow in combination with org-mode
Date: Sat, 16 Jun 2018 14:41:13 +0300 [thread overview]
Message-ID: <83r2l7yn52.fsf@gnu.org> (raw)
In-Reply-To: <87zhzvc9km.fsf@tu-berlin.de> (message from Gerald Wildgruber on Sat, 16 Jun 2018 12:25:13 +0200)
> From: Gerald Wildgruber <wildgruber@tu-berlin.de>
> Date: Sat, 16 Jun 2018 12:25:13 +0200
>
> - follow-post-command-hook 7755 41%
> - follow-adjust-window 7755 41%
> - follow-windows-start-end 7732 41%
> - follow-calc-win-end 7732 41%
> + pos-visible-in-window-p 25 0%
> + posn-at-x-y 7 0%
> + window-inside-pixel-edges 3 0%
> + follow-all-followers 4 0%
> follow-avoid-tail-recenter 3 0%
>
> If I understand correctly "follow-calc-win-end" would be the function
> that uses most of cpu time.
Yes, it looks like that. For even more detailed results, repeat the
experiment after loading the uncompiled follow.el.
> Anyone got an idea what's going on here and how to debug that? Are there
> possible optimizations with this situation? Or is this "normal",
> expected behavior, simply due to the number of windows and text
> displayed?
If you "show all" in the Org buffer, do the lags become significantly
smaller?
next prev parent reply other threads:[~2018-06-16 11:41 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-16 10:25 follow-mode: extremely slow in combination with org-mode Gerald Wildgruber
2018-06-16 11:41 ` Eli Zaretskii [this message]
2018-06-16 13:06 ` Gerald Wildgruber
2018-06-16 16:25 ` Eli Zaretskii
2018-06-16 21:05 ` Gerald Wildgruber
2018-06-17 6:57 ` Gerald Wildgruber
2018-06-17 8:12 ` Eli Zaretskii
2018-06-17 11:13 ` Alan Mackenzie
2018-06-17 13:02 ` Eli Zaretskii
2018-06-17 14:56 ` Gerald Wildgruber
2018-06-17 15:10 ` Eli Zaretskii
2018-06-19 12:08 ` Gerald Wildgruber
2018-06-19 16:55 ` Eli Zaretskii
2018-06-19 13:53 ` Gerald Wildgruber
2018-06-17 15:13 ` Eli Zaretskii
2018-06-21 8:25 ` Anders Lindgren
2018-06-27 16:43 ` Gerald Wildgruber
2018-07-09 20:12 ` Anders Lindgren
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83r2l7yn52.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=wildgruber@tu-berlin.de \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.