all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Gerd Möllmann" <gerd.moellmann@gmail.com>
To: martin rudalics <rudalics@gmx.at>
Cc: Eli Zaretskii <eliz@gnu.org>,  emacs-devel@gnu.org
Subject: Re: Question about üarent-frame changes
Date: Thu, 19 Sep 2024 06:29:12 +0200	[thread overview]
Message-ID: <m2r09g8dwn.fsf@MacBookPro.fritz.box> (raw)
In-Reply-To: <b98abbf3-b7fc-43c9-b545-c570464d3483@gmx.at> (martin rudalics's message of "Wed, 18 Sep 2024 20:52:00 +0200")

martin rudalics <rudalics@gmx.at> writes:

>> What you describe makes sens for GUI frames, but seems to make little
>> sense for TTY frames, because frame visibility situation there is much
>> simpler.
>
> You mean because only one normal frame can be visible at any time.
> However, child frames complicate the situation considerably because
> Emacs itself has to take care of their visibility instead of the WM.

Yes, that's true but I think I have that, at least in principle.

The biggest problem for me in this area today is that "visibility" on
GUIs and ttys apparently is not the same thing. For example,
make-frame-visible seems to do nothing for tty frames. So I guess all
tty frames are always visible in the sense that frame::visible is
non-zero.

But that would be too easy of course, which is why frame::visible has 2
bits, and if the second bit is set the frame is "obscured" (happens with
C-x 5 2), which I'd call sort of invisible because it can't be seen but
that's of course naive.

Grumpy.



  parent reply	other threads:[~2024-09-19  4:29 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-18 10:58 Question about üarent-frame changes Gerd Möllmann
2024-09-18 14:15 ` martin rudalics
2024-09-18 14:24   ` Ship Mints
2024-09-18 18:51     ` martin rudalics
2024-09-19  5:01       ` Eli Zaretskii
2024-09-19  8:10         ` martin rudalics
2024-09-18 14:26   ` Robert Pluim
2024-09-18 14:30     ` Ship Mints
2024-09-18 15:26       ` Gerd Möllmann
2024-09-18 15:32         ` Ship Mints
2024-09-18 15:22     ` Gerd Möllmann
2024-09-25 10:17       ` Gerd Möllmann
2024-09-25 11:13         ` Gerd Möllmann
2024-09-25 14:04           ` martin rudalics
2024-09-25 14:38             ` Gerd Möllmann
2024-09-25 15:29           ` Eli Zaretskii
2024-09-25 18:10             ` Gerd Möllmann
2024-09-26  4:54               ` Gerd Möllmann
2024-09-26  5:01                 ` Gerd Möllmann
2024-09-26  6:40                   ` Eli Zaretskii
2024-09-26  6:39                 ` Eli Zaretskii
2024-09-28  9:10           ` Gerd Möllmann
2024-09-18 18:51     ` martin rudalics
2024-09-18 15:03   ` Gerd Möllmann
2024-09-18 16:14     ` Eli Zaretskii
2024-09-18 16:42       ` Gerd Möllmann
2024-09-18 16:15   ` Eli Zaretskii
2024-09-18 18:52     ` martin rudalics
2024-09-19  0:33       ` Po Lu
2024-09-19  8:08         ` martin rudalics
2024-09-19  4:29       ` Gerd Möllmann [this message]
2024-09-19  8:09         ` martin rudalics
2024-09-19  9:15           ` Gerd Möllmann
2024-09-19  9:40             ` martin rudalics
2024-09-19 10:10               ` Gerd Möllmann
2024-09-19 11:13                 ` martin rudalics
2024-09-19 12:49                   ` Gerd Möllmann
2024-09-19  4:58       ` Eli Zaretskii
2024-09-19  8:10         ` martin rudalics
2024-09-19  8:20           ` Eli Zaretskii
2024-09-19  8:41             ` Po Lu
2024-09-19 10:30               ` Eli Zaretskii
2024-09-19 11:13                 ` martin rudalics
2024-09-19 11:33                   ` Eli Zaretskii
2024-09-19  9:26           ` Gerd Möllmann
2024-09-19 13:46             ` Po Lu

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m2r09g8dwn.fsf@MacBookPro.fritz.box \
    --to=gerd.moellmann@gmail.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=rudalics@gmx.at \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.