From: Feng Shu <tumashu@163.com>
To: martin rudalics <rudalics@gmx.at>
Cc: "Gerd Möllmann" <gerd.moellmann@gmail.com>,
"Emacs Devel" <emacs-devel@gnu.org>
Subject: Re: Question about minibuffer and child frames (Posframe)
Date: Mon, 07 Oct 2024 17:35:45 +0800 [thread overview]
Message-ID: <871q0sl0ge.fsf@163.com> (raw)
In-Reply-To: <37473fc5-0899-4957-a0ad-6cdff854ff58@gmx.at> (martin rudalics's message of "Mon, 7 Oct 2024 10:34:13 +0200")
martin rudalics <rudalics@gmx.at> writes:
>> posframe do not handle focus in most situation, for it is too complicate
>> to let focus work. posframe just *show* the content of a buffer.
>
> What if the user clicks into a child frame with the mouse? Do you have
> the frame's 'no-accept-focus' parameter set? Does it work everywhere?
> I never got any feedback on this.
by default, posframe use 'no-accept-focus', but it seem to not work
everywhere, it seem to depend on window manager used. if user clicks
poframe, sometimes it will get focus and insert user input, sometimes
not.
by default, posframe do not support user clicks :-)
>
>> When enable vertico-posframe, we just let the content of minibuffer is
>> showed in a posframe, but input handle is in parent frame, we lock the
>> height of parent minibuffer window and vscroll minibuffer window to hide
>> minibuffer content in below function.
>
> This sounds awfully tricky. Did you never try to do that in a "cleaner"
> way? Here I _always_ have one single minibuffer window in a child
> frame
Haha, My Emacs level is unable to handle focus bugs, and posframe do not
consider focus at the begin of design :-)
> and with the exception of some minor modifications that were necessary
> when redirecting frame focus got broken I have no problems. The child
> frame pops up when and where needed and is not visible otherwise.
>
> martin
>
--
prev parent reply other threads:[~2024-10-07 9:35 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-02 12:50 Question about minibuffer and child frames (Posframe) Gerd Möllmann
2024-10-02 13:39 ` Po Lu
2024-10-02 13:52 ` Gerd Möllmann
2024-10-02 14:56 ` martin rudalics
2024-10-02 15:47 ` Gerd Möllmann
2024-10-02 16:08 ` martin rudalics
2024-10-02 17:17 ` Gerd Möllmann
2024-10-02 17:34 ` martin rudalics
2024-10-02 18:48 ` Gerd Möllmann
2024-10-03 7:35 ` Gerd Möllmann
2024-10-03 8:26 ` martin rudalics
2024-10-03 9:07 ` Gerd Möllmann
2024-10-03 9:33 ` martin rudalics
2024-10-03 9:50 ` Gerd Möllmann
2024-10-03 13:12 ` martin rudalics
2024-10-03 14:03 ` Gerd Möllmann
2024-10-04 7:24 ` Gerd Möllmann
2024-10-04 8:10 ` martin rudalics
2024-10-04 9:16 ` Gerd Möllmann
2024-10-04 9:31 ` martin rudalics
2024-10-04 9:55 ` Gerd Möllmann
2024-10-05 8:31 ` Gerd Möllmann
2024-10-02 18:43 ` Eli Zaretskii
2024-10-02 18:56 ` Gerd Möllmann
2024-10-07 1:08 ` Feng Shu
2024-10-07 4:28 ` Gerd Möllmann
2024-10-07 6:43 ` Feng Shu
2024-10-07 8:00 ` Gerd Möllmann
2024-10-07 8:17 ` Feng Shu
2024-10-07 8:32 ` Gerd Möllmann
2024-10-07 10:03 ` Feng Shu
2024-10-07 10:46 ` Gerd Möllmann
2024-10-07 13:44 ` martin rudalics
2024-10-07 14:29 ` Gerd Möllmann
2024-10-07 21:45 ` Feng Shu
2024-10-08 4:19 ` Gerd Möllmann
2024-10-08 5:01 ` Gerd Möllmann
2024-10-08 5:42 ` Feng Shu
2024-10-08 6:31 ` Gerd Möllmann
2024-10-08 13:06 ` Gerd Möllmann
2024-10-07 8:35 ` martin rudalics
2024-10-07 8:46 ` Gerd Möllmann
2024-10-07 8:52 ` martin rudalics
2024-10-07 9:12 ` Gerd Möllmann
2024-10-07 10:11 ` Feng Shu
2024-10-07 10:36 ` Gerd Möllmann
2024-10-07 12:12 ` Feng Shu
2024-10-07 12:24 ` Gerd Möllmann
2024-10-07 13:44 ` martin rudalics
2024-10-07 14:24 ` Gerd Möllmann
2024-10-07 8:35 ` martin rudalics
2024-10-07 9:46 ` Feng Shu
2024-10-07 7:20 ` Feng Shu
2024-10-07 8:12 ` Gerd Möllmann
2024-10-11 8:03 ` Gerd Möllmann
2024-10-07 8:34 ` martin rudalics
2024-10-07 9:35 ` Feng Shu [this message]
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=871q0sl0ge.fsf@163.com \
--to=tumashu@163.com \
--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).