|Subject:||bug#15957: 24.3.50; Follow mode scrolling broken on Emacs trunk|
|Date:||Mon, 25 Nov 2013 10:19:38 +0100|
committer: Dmitry Antipov <address@hidden>
branch nick: trunk
timestamp: Thu 2013-08-08 08:42:40 +0400
Do not reset window modification event counters excessively.
These leftovers and poor man's tricky methods to catch extra
redisplay's attention are no longer needed.
* frame.c (set_menu_bar_lines_1):
* minibuf.c (read_minibuf_unwind):
* window.c (Fset_window_start, set_window_buffer, window_resize_apply)
(grow_mini_window, shrink_mini_window, window_scroll_pixel_based)
* xdisp.c (redisplay_window): Do not reset last_modified and
I will continue to narrow down the problem in the post-command hook, I'll let you know when I'm done.
> I really doubt that the code in `follow-scroll-up' is broken.I didn't say so.
IIUC we'd have to find out when and where follow-mode expects the
> is designed so that the rearrangement of the other windows (the ones that
> follow the selected window) occur in the post-command hook (to allow
> Follow-mode to act upon all Emacs commands, not only it's special
> function). It appears that something has changed in the display engine, or
> in the way that post-command-hook is called, that makes this mechanism
> fail. This could also account for the difference we see when the function
> is called via a key sequence as compared to via M-x.
selected window to be a certain window and why this sometimes fails. So
maybe you should try the change I suggested.Please do that.
> This is also the reason why reported this as a bug, rather than digging
> into the code myself. However, I could try to add log code to Follow mode,
> to check if I could try to figure out what is going on.
|[Prev in Thread]||Current Thread||[Next in Thread]|