From: "Gerd Möllmann" <gerd.moellmann@gmail.com>
To: Robert Pluim <rpluim@gmail.com>
Cc: martin rudalics <rudalics@gmx.at>, Eli Zaretskii <eliz@gnu.org>,
emacs-devel@gnu.org
Subject: Re: Q: child frames on ttys
Date: Fri, 30 Aug 2024 14:37:59 +0200 [thread overview]
Message-ID: <m2jzfy5gpk.fsf@pro2.fritz.box> (raw)
In-Reply-To: <87bk1auso3.fsf@gmail.com> (Robert Pluim's message of "Fri, 30 Aug 2024 14:00:28 +0200")
Robert Pluim <rpluim@gmail.com> writes:
>>>>>> On Fri, 30 Aug 2024 13:19:44 +0200, Gerd Möllmann <gerd.moellmann@gmail.com> said:
> >> but I have a use case in mind where I have two non-overlapping frames
> >> in the same tty. Is that the kind of thing youʼre talking about?
>
> Gerd> Would these be "normal" Emacs frames like one gets with C-x 5 2? Or are
> Gerd> these frames special in some sense, like a Corfu child frame displaying
> Gerd> completions (possibly with second child frame displaying additional info
> Gerd> for completion candidates), or a Posframe chlid frame displaying a
> Gerd> Transient menu, or somehting like that?
>
> Theyʼd be completely normal independent frames. Think two half screen
> gui frames aligned next to each other, but then on a tty.
>
> If there was a way in Emacs to tell window generating commands to
> pretend that only the left half of the current tty frame should be
> considered, then I could use that, but I donʼt know of one. (hmm,
> could I spike `frame-width' somehow?)
>
> (itʼs an obscure use case, so itʼs really not a big deal if itʼs not
> supported. posframe or similar on tty would already be fantastic)
Thanks, I guess that speaks for having a more or less complete child
frame feature.
next prev parent reply other threads:[~2024-08-30 12:37 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
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 [this message]
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=m2jzfy5gpk.fsf@pro2.fritz.box \
--to=gerd.moellmann@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=rpluim@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).