From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Michael Welsh Duggan <mwd@md5i.com>
Cc: Alan Mackenzie <acm@muc.de>, emacs-devel@gnu.org
Subject: Re: What are invisible frames for?
Date: Thu, 22 Apr 2021 10:08:22 -0400 [thread overview]
Message-ID: <jwvh7jyifj3.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87v98eo264.fsf@md5i.com> (Michael Welsh Duggan's message of "Thu, 22 Apr 2021 09:54:11 -0400")
> I know that "emacs --daemon" creates a frame that isn't displayed. I
> don't know if that frame is an "invisible frame" by this definition, but
> I thought I'd mention it, just in case.
No, that frame is yet different: it's "visible" but it's in a "dummy
terminal" not connected to any GUI and not even a tty (it's initially
connected to the stdin/stdout, tho, so `message` gets output to stdout,
for example. It's the same dummy terminal that's used when Emacs runs
in batch mode).
BTW there are yet more forms of "invisible" frames: those frames that
are displayed on terminals that the user cannot currently see
(e.g. connected to a $DISPLAY that's in a different physical location).
This is relevant in the sense that when a minibuffer is on a frame
that's connected to display to which the user doesn't currently have
access, it can make Emacs unusable. For this reason, `server.el` calls
`top-level` sometimes.
Stefan
next prev parent reply other threads:[~2021-04-22 14:08 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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jwvh7jyifj3.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=acm@muc.de \
--cc=emacs-devel@gnu.org \
--cc=mwd@md5i.com \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.