From: Po Lu <luangruo@yahoo.com>
To: martin rudalics <rudalics@gmx.at>
Cc: Eli Zaretskii <eliz@gnu.org>,
gerd.moellmann@gmail.com, emacs-devel@gnu.org
Subject: Re: Question about üarent-frame changes
Date: Thu, 19 Sep 2024 08:33:52 +0800 [thread overview]
Message-ID: <87jzf832j3.fsf@yahoo.com> (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.
>
> For example, I can type into a GUI window text beneath a (small) child
> frame as long as that child frame doesn't have focus. Emulating such
> behavior with text emanating at the right of the child frame on a TTY
> seems tricky at least.
>
> martin
Most of the extant popup packages that exercise child frames also retain
and reparent them across different parents, and as such, Gerd will need
to implement reparenting.
next prev parent reply other threads:[~2024-09-19 0:33 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 [this message]
2024-09-19 8:08 ` martin rudalics
2024-09-19 4:29 ` Gerd Möllmann
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87jzf832j3.fsf@yahoo.com \
--to=luangruo@yahoo.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=gerd.moellmann@gmail.com \
--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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).