Subject: bug#75056: 31.0.50; tty-child-frames with server / multiple clients possible hangs

From: Eli Zaretskii <[email-masked]>
Date: Sun, 26 Jan 2025 21:05:49 +0200

> Date: Sun, 26 Jan 2025 17:44:39 +0100
> Cc: [email-masked], [email-masked], [email-masked]
> From: martin rudalics <[email-masked]>
> 
>  > I just described what factually happens:
>  >
>  >    emacs -Q -nw
>  >    C-x 5 b RET
>  >    M-: (frame-visible-p (next-frame)) RET
>  >     => t
> 
> That's what 'frame-visible-p' does.  I wondered what happened to
> FRAME_OBSCURED_P in w32_read_socket.  Has that become obsolete?

Gerd decided to remove that as part of the TTY child frames changeset.
He said it was an optimization that is not worth keeping.

Why are you asking? did you see any problems caused by that?