[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#14408: 24.3.50; *Messages* buffer no longer updates automatically
From: |
Eli Zaretskii |
Subject: |
bug#14408: 24.3.50; *Messages* buffer no longer updates automatically |
Date: |
Thu, 16 May 2013 20:24:06 +0300 |
> Date: Thu, 16 May 2013 11:37:51 -0400
> From: Barry OReilly <gundaetiapo@gmail.com>
>
> Git bisected the Emacs repo at Savannah to:
>
> 046fb9fbdc0ee0c26e0063ce5ee94bead46ee98d is the first bad commit
> commit 046fb9fbdc0ee0c26e0063ce5ee94bead46ee98d
> Author: Dmitry Antipov <dmantipov@yandex.ru>
> Date: Tue Dec 11 13:51:12 2012 +0400
>
> * buffer.c (Fset_buffer_multibyte): Do not force redisplay
> if changed buffer is not shown in a window.
> * insdel.c (prepare_to_modify_buffer): Likewise.
> * window.c (replace_buffer_in_windows_safely): Do nothing
> if buffer is not shown in a window.
> (Fforce_window_update): Likewise if string or buffer argument
> is passed.
Could you show a precise recipe for reproducing this, starting with
"emacs -Q"? I tried to reproduce with today's trunk, but couldn't.
Perhaps I don't understand what you mean by "side by side" or don't
invoke eval-last-sexp as you do.
Does the problem depend on the frame/window size? Does it appear in
"emacs -nw" as well as in GUI sessions? And what OS is that?
Thanks.