unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Alan Mackenzie <acm@muc.de>
To: emacs-devel@gnu.org
Subject: What are invisible frames for?
Date: Thu, 22 Apr 2021 10:09:10 +0000	[thread overview]
Message-ID: <YIFLRsawLKHiXqGg@ACM> (raw)

Hello, Emacs.

In src/frame.c, the notion of an @dfn{invisible frame} is implemented.
On a GUI, when a frame is in this invisible state, it appears to be
completely inaccessible to the user - it doesn't appear anywhere on the
GUI, there appear to be no commands to access it, and so on.  Only a
Lisp form can do anything with it, like making it visible again.

What is this facility used for?  There're uses in dframe.el, and there's
something in cl-extra.el saying it's "support for setf".  There aren't
really any uses in the C files - just one call in minibuf.c when
something else has set up an option for it.

So what is this thing for?

The reason I ask is that making frames invisible (or even iconified)
affects any minibuffers on those frames.  The current handling, which is
old, moves the minibuffers onto another frame.  This conflicts with the
meaning of the (newish) variable minibuffer-follows-selected-frame when
its value isn't t.  In particular, when m-f-s-f is nil, minibuffers are
defined to stay on the frame they were first created on.

So, to determine how these MBs should be handled, it would be very
useful to understand what invisible frames are used for.

This has relevance for bug #47766.

Thanks in advance!

-- 
Alan Mackenzie (Nuremberg, Germany).



             reply	other threads:[~2021-04-22 10:09 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-22 10:09 Alan Mackenzie [this message]
2021-04-22 12:15 ` What are invisible frames for? 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
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=YIFLRsawLKHiXqGg@ACM \
    --to=acm@muc.de \
    --cc=emacs-devel@gnu.org \
    /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).