unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: martin rudalics <rudalics@gmx.at>
To: "Gerd Möllmann" <gerd.moellmann@gmail.com>
Cc: Emacs Devel <emacs-devel@gnu.org>
Subject: Re: Question about üarent-frame changes
Date: Wed, 18 Sep 2024 16:15:56 +0200	[thread overview]
Message-ID: <9bc2af0a-d3c1-4ba6-a350-af6e2b85695d@gmx.at> (raw)
In-Reply-To: <m2cyl19qkk.fsf@MacBookPro.fritz.box>

 > AFAICT from the Elisp Info docs, one is currently free to change the
 > parent-frame as one sees fit. That is, one can make a child a root
 > frame, a root frame a child, or change the parent of a child to another
 > root.
 >
 > I'm currently inclined to disallow parent-frame changes on ttys
 > entirely, unless it is used for something. Couldn't find something
 > today, but maybe something is a package outside Emacs' repo, or I'm just
 > ont looking for the right thing.

I'm not aware of people using multiple frames on TTYs and I have no idea
whether child frames out there are even intended to be reparented.

Reparenting is useful because you can set up one child frame for some
special purpose, make it invisible when you don't need it, and move it
to another frame and make it visible there whenever you want to.  On
GUIs, this approach has the advantage that you can avoid the (at least
here) costly process of setting up frame faces every time anew.  Emacs
tooltips do that by default and I recall that showing a tooltip every
time incurred two entire GC cycles here.

martin



  reply	other threads:[~2024-09-18 14:15 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 [this message]
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
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=9bc2af0a-d3c1-4ba6-a350-af6e2b85695d@gmx.at \
    --to=rudalics@gmx.at \
    --cc=emacs-devel@gnu.org \
    --cc=gerd.moellmann@gmail.com \
    /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).