[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: follow-mode: extremely slow in combination with org-mode

From: Anders Lindgren
Subject: Re: follow-mode: extremely slow in combination with org-mode
Date: Thu, 21 Jun 2018 10:25:39 +0200


There can be a number of reasons why follow-mode is slow. The main problem is that is it's time consuming to recompute the window state, and even more time consuming when aligning the windows. For simple commands like point movement, follow-mode assumes that the content of the buffers hasn't changed and retain the existing layout, whereas for other commands (including self-insert-command), everything is recomputed and realigned.

However, I use six side by side windows, and a small font, giving me a total of almost 800 consecutive lines, and it typically runs fine without any noticeable lag.

There are a number of factors that can have a negative impact on follow-mode:

- It run slower on a 32 bit binary than on a 64 bit binary (at least under Windows). (For this reason, I used Emacs 22 at work for many years, until prebuilt 64 bit binaries of modern Emacs versions were available.)

- Follow-mode is has problems when the width of the windows differ, especially if you have long lines that spill over from one window to another. I've written a support package to set up side-by-side windows in a pixel-perfect way, https://github.com/Lindydancer/multicolumn -- please try if and see if follow-mode runs more smoothly.

One thing that I have had on my wish-list for a very long time (20+ years) is that normal typing should use and update the cache, to speed things up. Of course, this only work as long as the editing doesn't change the layout, like when inserting a newline or make a line so long that it wraps. Unfortunately, I don't think that I will have time for it anytime soon, but I'm happy to share my ideas if someone else is willing to make a try.

What made me curious that you said that the slow-down only occurs with org-mode. My guess is that invisible text makes it harder for Emacs to calculate window layout properties.

    Anders Lindgren (I wrote follow-mode when I was a student, in the mid 1990:s)

On Sat, Jun 16, 2018 at 12:25 PM, Gerald Wildgruber <address@hidden> wrote:


I have got a problem with enormous lag while entering text in buffers
with emacs follow-mode enabled.

I'm using emacs (git checkout v. 27.0.50) and Org mode (git checkout

My work is solely text-based, using org-mode. A typical setup is to use
a maximized or full screen emacs frame split into five windows
positioned vertically one next to the other on a 40" 4k display. All
five windows display one and the same file, that is opened using emacs
follow-mode, so that every window is displaying a portion of the same
file in a continuous manner (simultaneously displaying up to 45kb of
text in one frame, an entire paper).

Unfortunately, with this setup there is terrible lag with every single
key input (on a very fast quad core machine); every key stroke produces
a 100% processor load.

If I deactivate follow-mode, the problem disappears. It also gets better
if I enable text-mode instead of org-mode.

I then used the elisp profiler (M-x profiler-start/report) to find out
which function uses most cpu time while editing text in said setup. Here
is the result:

Collapsed, the report looks like that:

+ command-execute                                                8789  47%
+ follow-post-command-hook                                       7755  41%
+ ...                                                            1976  10%
+ redisplay_internal (C function)                                 104   0%
+ yas--post-command-handler                                        40   0%
+ timer-event-handler                                              20   0%
  tooltip-hide                                                      7   0%

And somewhat expanded:

- 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.

I then did additional profiling with the elp library, adding relevant
functions under "Command-execute" and "follow-post-command-hook" to
elp-function-list, edited text, and then did M-x elp-results. It showed
again that "follow-calc-win-end" by far used most of cpu time.

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



Sent with mu4e

reply via email to

[Prev in Thread] Current Thread [Next in Thread]