unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Alan Mackenzie <acm@muc.de>
To: martin rudalics <rudalics@gmx.at>
Cc: emacs-devel@gnu.org
Subject: Re: What are invisible frames for?
Date: Thu, 22 Apr 2021 14:13:14 +0000	[thread overview]
Message-ID: <YIGEeiOOh9Qk2TWq@ACM> (raw)
In-Reply-To: <bcb67596-a061-663d-e029-46686136fa24@gmx.at>

Hello, Martin.

On Thu, Apr 22, 2021 at 14:15:03 +0200, martin rudalics wrote:
>  > So, to determine how these MBs should be handled, it would be very
>  > useful to understand what invisible frames are used for.

> I'm using a minibuffer child frame which is invisible most of the time.
> It becomes visible and reparented to the selected frame whenever I want
> to talk to it.  Also, I have `tooltip-reuse-hidden-frame' non-nil which
> means that my tooltip frame is invisible whenever it's not used.

OK.  Presumably you set this up by setting the 'visibility frame
parameter.  I don't think setting that frame parameter causes
Fmake_frame_invisible to get called.  At least, I can't find the call
anywhere.

I don't think I was clear enough in my OP, but it's calls to
Fmake_frame_invisible which are bothering me.  That function moves any
minibuffer on the frame to some other frame.  I don't think it should.
That's what I'm trying to sort out.

[ .... ]

> martin

-- 
Alan Mackenzie (Nuremberg, Germany).



  parent reply	other threads:[~2021-04-22 14:13 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-22 10:09 What are invisible frames for? Alan Mackenzie
2021-04-22 12:15 ` martin rudalics
2021-04-22 13:18   ` Stefan Monnier
2021-04-22 21:23     ` Clément Pit-Claudel
2021-04-22 14:13   ` Alan Mackenzie [this message]
2021-04-22 16:09     ` [External] : " Drew Adams
2021-04-22 12:31 ` Stefan Monnier
2021-04-22 13:54   ` Michael Welsh Duggan
2021-04-22 14:08     ` Stefan Monnier
2021-04-22 14:13     ` Eli Zaretskii
2021-04-22 14:14 ` tumashu

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=YIGEeiOOh9Qk2TWq@ACM \
    --to=acm@muc.de \
    --cc=emacs-devel@gnu.org \
    --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).