From: <tomas@tuxteam.de>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: Joost Kremers <joostkremers@fastmail.fm>,
"help-gnu-emacs@gnu.org" <help-gnu-emacs@gnu.org>
Subject: Re: Frame visibility
Date: Mon, 5 Dec 2016 16:26:57 +0100 [thread overview]
Message-ID: <20161205152657.GA25424@tuxteam.de> (raw)
In-Reply-To: <8760my1m0k.fsf@web.de>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Mon, Dec 05, 2016 at 03:35:55PM +0100, Michael Heerdegen wrote:
> Joost Kremers <joostkremers@fastmail.fm> writes:
>
> > The Elisp manual says that a frame can be visible, invisible or
> > iconified. Visible and iconified (a.k.a. minimized) are clear, but
> > when exactly is a frame invisible?
>
> AFAIU the manual, an invisible frame is just not displayed (...visible),
> so it's like "iconified" but without an icon, I guess. With other
> words: something like minimizing implemented in Emacs.
Exactly. This is window manager parlance. Those things correspond to
the ICCCM values "Normal", "Iconic" and "Withdrawn" values of the
(X) window's (which is an Emacs frame) WM_STATE property[1].
However the window manager decides to represent those things, they
are sometimes creative :-)
All Emacs does (all Emacs *can* do) is to request the style from
the WM, by setting some X properties on its windows (frames). The
window manager, as configured by the user then maps those abstract
requests to a concrete appearance.
I do like it that way. Imagine my browser could start deciding on
how its decoration looks, controlled by some random shi^H^H^H
obscure javascript off some obscure rag-du-jour page. No, thanks.
As Michael says... perhaps they hide your computer.
Regards
[1] https://tronche.com/gui/x/icccm/sec-4.html
- -- t
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
iEYEARECAAYFAlhFh0EACgkQBcgs9XrR2kZRSgCfcKVIdYKcVkLAe7JxzQTPhgnU
Jr8An1cVYadYKoTx4FpLvJzUQ9Q85YKy
=GgWE
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2016-12-05 15:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-29 12:37 Frame visibility Joost Kremers
2016-12-05 14:35 ` Michael Heerdegen
2016-12-05 14:50 ` Stefan Monnier
2016-12-05 15:26 ` tomas [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=20161205152657.GA25424@tuxteam.de \
--to=tomas@tuxteam.de \
--cc=help-gnu-emacs@gnu.org \
--cc=joostkremers@fastmail.fm \
--cc=michael_heerdegen@web.de \
/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.
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).