bug#57466: closed (29.0.50; *Messages* buffer stops following after `kill-buffer')

[GNU bug Tracking System]

Your message dated Wed, 31 Aug 2022 05:31:47 +0300
with message-id <83a67lta7g.fsf@gnu.org>
and subject line Re: bug#57466: 29.0.50; *Messages* buffer stops following 
after `kill-buffer'
has caused the debbugs.gnu.org bug report #57466,
regarding 29.0.50; *Messages* buffer stops following after `kill-buffer'
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs@gnu.org.)


-- 
57466: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=57466
GNU Bug Tracking System
Contact help-debbugs@gnu.org with problems
> --- Begin Message ---
>
>
>
> Subject: 
>
> 29.0.50; *Messages* buffer stops following after `kill-buffer'
>
>
>
>
> Date: 
>
> Sun, 28 Aug 2022 19:04:25 +0000
>
>
>
>
>   What happened:
> When you `kill-buffer' on *Messages*, after it remakes itself point no
> longer follows output.
>
>   To reproduce:
> $ emacs -Q
> C-x b
> *Messages* <RET>
> C-x 2
> C-x b
> test <RET>
> C-x k
> *Messages* <RET>
> C-x b
> *Messages* <RET>
> C-x o
> ; You should now be back in the test buffer
> C-n C-p C-n C-p
> ; Run ^this till the last line in *Messages* is off screen.
> ; It no longer follows output.
>
>
>
> --- End Message ---
> --- Begin Message ---
>
>
>
> Subject: 
>
> Re: bug#57466: 29.0.50; *Messages* buffer stops following after `kill-buffer'
>
>
>
>
> Date: 
>
> Wed, 31 Aug 2022 05:31:47 +0300
>
>
>
>
> > Date: Tue, 30 Aug 2022 23:20:46 +0000
> > From: laslydone <laslydone@protonmail.com>
> > Cc: 57466@debbugs.gnu.org
> > 
> > > Thanks, I hope I fixed this now on the master branch.
> > Yes it seems fixed now; built a28ede3a61a70cf83dfcba6c9d314fbb051a3a94
> > and it worked.
>
> Thanks for testing, I'm therefore closing this bug.
>
>
> --- End Message ---