From: Po Lu <luangruo@yahoo.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: martin rudalics <rudalics@gmx.at>,
gerd.moellmann@gmail.com, emacs-devel@gnu.org
Subject: Re: Question about üarent-frame changes
Date: Thu, 19 Sep 2024 16:41:24 +0800 [thread overview]
Message-ID: <874j6c2fyj.fsf@yahoo.com> (raw)
In-Reply-To: <86zfo4836w.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 19 Sep 2024 11:20:39 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> Date: Thu, 19 Sep 2024 10:10:11 +0200
>> Cc: gerd.moellmann@gmail.com, emacs-devel@gnu.org
>> From: martin rudalics <rudalics@gmx.at>
>>
>> > sounds not very useful to me on a TTY, because switching frames on a
>> > TTY will make the child frame invisible anyway. And why would I want
>> > to see a child of frame F1 when I display only frame F2?
>>
>> Because the calling code may reparent the child frame from F1 to F2
>> whenever the user switches from frame F1 to frame F2. At least Po Lu
>> said that applications do such reparenting.
>
> Isn't that the same as simply showing the child frame even though its
> parent frame is obscured?
>
> And I'd need to hear more details about what the application wants to
> achieve by such reparenting, to understand the issue.
They simply wish to retain created child frames for as long a period as
possible, because frame creation is expensive, and configuring a child
frame to behave as intended is hard work. See posframe.el (on ELPA) for
a typical instance, where three years ago I encountered the same dilemma
with the Haiku port.
next prev parent reply other threads:[~2024-09-19 8:41 UTC|newest]
Thread overview: 35+ 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-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
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 [this message]
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=874j6c2fyj.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 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.