From: Eli Zaretskii <eliz@gnu.org>
To: martin rudalics <rudalics@gmx.at>
Cc: gerd.moellmann@gmail.com, emacs-devel@gnu.org
Subject: Re: Q: child frames on ttys
Date: Fri, 30 Aug 2024 14:03:40 +0300 [thread overview]
Message-ID: <86jzfye0hf.fsf@gnu.org> (raw)
In-Reply-To: <cefc2d05-67d8-4f49-9be9-89092ca1a650@gmx.at> (message from martin rudalics on Fri, 30 Aug 2024 11:17:12 +0200)
> Date: Fri, 30 Aug 2024 11:17:12 +0200
> Cc: Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org
> From: martin rudalics <rudalics@gmx.at>
>
> > (Background is of course that I'm trying to assess how much work is
> > ahead, and if I want to do it :-).
>
> I suppose that visibility and restacking of child frames and size
> changes of child frames and their ancestors are the corner issues. Once
> these have been resolved, the code should be pushed and you should wait
> for user feedback.
>
> Many thanks for lifting the "Note that child frames are meaningful on
> graphical terminals only." restriction, martin
Another feature to test with child frames on TTY displays is menus,
both from the menu bar and popup menus.
From where I stand, features that are perhaps hard to implement for
child frames on TTY displays could be documented as unsupported, and
could either do nothing or signal an error. IOW, we don't have to
support everything on TTY frames in this regard, if doing so is
currently hard or impossible. The feature, even if limited, is still
useful enough, from my POV.
Thanks.
next prev parent reply other threads:[~2024-08-30 11:03 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-17 7:24 Q: child frames on ttys Gerd Möllmann
2024-08-17 10:39 ` Eli Zaretskii
2024-08-17 11:02 ` Gerd Möllmann
2024-08-17 17:18 ` martin rudalics
2024-08-17 18:41 ` Gerd Möllmann
2024-08-21 7:10 ` Gerd Möllmann
2024-08-21 7:55 ` martin rudalics
2024-08-21 8:03 ` Gerd Möllmann
2024-08-21 8:11 ` Robert Pluim
2024-08-21 8:38 ` Gerd Möllmann
2024-08-21 12:00 ` Gerd Möllmann
2024-08-30 6:42 ` Gerd Möllmann
2024-08-30 9:17 ` martin rudalics
2024-08-30 11:03 ` Eli Zaretskii [this message]
2024-08-30 11:23 ` Gerd Möllmann
2024-08-30 14:53 ` Eli Zaretskii
2024-08-31 8:26 ` Gerd Möllmann
2024-08-31 11:54 ` Eli Zaretskii
2024-08-31 14:00 ` Gerd Möllmann
2024-08-31 14:40 ` Eli Zaretskii
2024-09-02 8:37 ` Gerd Möllmann
2024-09-02 11:38 ` Eli Zaretskii
2024-09-02 12:46 ` Gerd Möllmann
2024-09-02 13:13 ` Eli Zaretskii
2024-09-02 13:54 ` Gerd Möllmann
2024-08-30 11:09 ` Gerd Möllmann
2024-08-30 9:29 ` Robert Pluim
2024-08-30 11:19 ` Gerd Möllmann
2024-08-30 12:00 ` Robert Pluim
2024-08-30 12:37 ` Gerd Möllmann
2024-08-30 21:11 ` Dmitry Gutov
2024-08-31 6:45 ` Eli Zaretskii
2024-08-31 8:46 ` Po Lu
2024-09-01 0:27 ` Dmitry Gutov
2024-09-16 1:35 ` Dmitry Gutov
2024-09-01 0:27 ` Dmitry Gutov
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=86jzfye0hf.fsf@gnu.org \
--to=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).