From: Eli Zaretskii <eliz@gnu.org>
To: Barry OReilly <gundaetiapo@gmail.com>
Cc: 14408@debbugs.gnu.org
Subject: bug#14408: 24.3.50; *Messages* buffer no longer updates automatically
Date: Thu, 16 May 2013 20:24:06 +0300 [thread overview]
Message-ID: <831u96u9c9.fsf@gnu.org> (raw)
In-Reply-To: <CAFM41H07VqGwGY1HLv4UYkjE15bULJo==SSj+W6k2S-xoK1MVQ@mail.gmail.com>
> 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.
next prev parent reply other threads:[~2013-05-16 17:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-15 13:03 bug#14408: 24.3.50; *Messages* buffer no longer updates automatically Barry OReilly
[not found] ` <handler.14408.B.13686230477730.ack@debbugs.gnu.org>
2013-05-16 15:37 ` bug#14408: Acknowledgement (24.3.50; *Messages* buffer no longer updates automatically) Barry OReilly
2013-05-16 17:24 ` Eli Zaretskii [this message]
2013-05-16 17:30 ` bug#14408: 24.3.50; *Messages* buffer no longer updates automatically Glenn Morris
2013-05-16 18:21 ` Drew Adams
2013-05-16 18:34 ` Eli Zaretskii
2013-05-16 18:08 ` Barry OReilly
2013-05-16 18:37 ` Eli Zaretskii
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.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=831u96u9c9.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=14408@debbugs.gnu.org \
--cc=gundaetiapo@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.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).