[debbugs-tracker] bug#14408: closed (24.3.50; *Messages* buffer no longer updates automatically)

[GNU bug Tracking System]

Your message dated Thu, 16 May 2013 21:34:50 +0300
with message-id <address@hidden>
and subject line Re: bug#14408: 24.3.50; *Messages* buffer no longer updates 
automatically
has caused the debbugs.gnu.org bug report #14408,
regarding 24.3.50; *Messages* buffer no longer updates automatically
to be marked as done.

(If you believe you have received this mail in error, please contact
address@hidden)


-- 
14408: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=14408
GNU Bug Tracking System
Contact address@hidden with problems
> --- Begin Message ---
>
>
>
> Subject: 
>
> 24.3.50; *Messages* buffer no longer updates automatically
>
>
>
>
> Date: 
>
> Wed, 15 May 2013 09:03:43 -0400
>
>
>
>
> In Emacs 24.3, I can put the *Messages* and *scratch* buffers side by side, call eval-last-sexp on message calls in *scratch*, and see the message automatically appear in *Messages*.
>
> Using Emacs from trunk, *Messages* is not updated with the message until I either "C-x o" to it or cause some other message to appear (such as "End of buffer" message).
>
>
> --- End Message ---
> --- Begin Message ---
>
>
>
> Subject: 
>
> Re: bug#14408: 24.3.50;	*Messages* buffer no longer updates automatically
>
>
>
>
> Date: 
>
> Thu, 16 May 2013 21:34:50 +0300
>
>
>
>
> > From: Glenn Morris <address@hidden>
> > Cc: Barry OReilly <address@hidden>,  address@hidden
> > Date: Thu, 16 May 2013 13:30:18 -0400
> > 
> > Eli Zaretskii wrote:
> > 
> > > 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.
> > 
> > Current trunk, GNU/Linux, Lucid toolkit:
> > emacs -Q
> > C-x 3
> > C-h e
> > 
> > In scratch, enter "1" and press C-x C-e. No "1" appears in Messages.
> > Press C-x o to select Messages. Now "1" appears.
>
> Thanks.  This is now fixed in trunk revision 112612.
>
>
> --- End Message ---