bug#56773: closed (29.0.50; (readablep UNREADABLE) causes strange things)

[GNU bug Tracking System]

Your message dated Thu, 28 Jul 2022 10:53:57 +0800
with message-id <87sfmmq75m.fsf@yahoo.com>
and subject line Re: bug#56773: 29.0.50; (readablep UNREADABLE) causes strange 
things
has caused the debbugs.gnu.org bug report #56773,
regarding 29.0.50; (readablep UNREADABLE) causes strange things
to be marked as done.

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


-- 
56773: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=56773
GNU Bug Tracking System
Contact help-debbugs@gnu.org with problems
> --- Begin Message ---
>
>
>
> Subject: 
>
> 29.0.50; (readablep UNREADABLE) causes strange things
>
>
>
>
> Date: 
>
> Tue, 26 Jul 2022 05:42:05 +0200
>
>
>
>
> Hello,
>
> emacs -Q:
>
> (progn (readablep (current-window-configuration))
>        (current-buffer))
> ==> #<buffer  prin1>
>
> After evaluating such a `readablep' call, weird things can happen
> because of this buffer being current.  I tried to actually display that
> buffer and the window I got looked quite funny, one second later Emacs
> had crashed.
>
> TIA,
>
> Michael.
>
>
> In GNU Emacs 29.0.50 (build 31, x86_64-pc-linux-gnu, GTK+ Version 3.24.24, 
> cairo version 1.16.0)
>  of 2022-07-26 built on drachen
> Repository revision: c455023f93f5073e7032a2097821e23eafa6f1aa
> Repository branch: master
> Windowing system distributor 'The X.Org Foundation', version 11.0.12011000
> System Description: Debian GNU/Linux 11 (bullseye)
>
>
>
>
> --- End Message ---
> --- Begin Message ---
>
>
>
> Subject: 
>
> Re: bug#56773: 29.0.50; (readablep UNREADABLE) causes strange things
>
>
>
>
> Date: 
>
> Thu, 28 Jul 2022 10:53:57 +0800
>
>
>
>
> User-agent: 
>
> Gnus/5.13 (Gnus v5.13) Emacs/28.0.91 (gnu/linux)
>
>
>
>
> Michael Heerdegen <michael_heerdegen@web.de> writes:
>
> > Po Lu <luangruo@yahoo.com> writes:
> >
> >> Right, thanks.  I fixed that as well.
> >
> > Thanks for the fix.  My use case seems to behave sane now.
> >
> > Michael.
>
> Closing, thanks for testing.
>
>
> --- End Message ---