From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Po Lu <luangruo@yahoo.com>
Cc: emacs-devel@gnu.org
Subject: Re: master cc29fab3a6: Redisplay "invisible" frames that are actually visible on modern X
Date: Mon, 26 Dec 2022 09:04:26 -0500 [thread overview]
Message-ID: <jwvy1qucll0.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <20221226075759.AAF44C00613@vcs2.savannah.gnu.org> (Po Lu via Mailing list for Emacs changes's message of "Mon, 26 Dec 2022 02:57:59 -0500 (EST)")
> +** Emacs will now redisplay frames that are made visible by a compositor.
> +This means even if `frame-visible-p' returns nil or `icon', the frame
> +will be redisplayed if it is being displayed to the user by the
> +compositing manager, which can happenas part of a preview for
> +iconified windows.
FWIW, while this sounds about right for `icon`ified frames, for those
frames that are marked as actually invisible, I think we should try and
keep them as invisible as possible. IOW if they appear as
preview/thumbnails somewhere it should itself be considered as a bug
(either in our code or in the compositing manager or ...).
Keeping the preview's appearance up-to-date is wasted efforts in
this respect.
Stefan
PS: In case you need to see concrete uses of invisible frames, you can
find one in `server.el` and another in GNU ELPA's `xclip.el`.
There are probably others, but these are the one I know of because
I coded them :-)
next parent reply other threads:[~2022-12-26 14:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <167204147913.11300.799159655252309055@vcs2.savannah.gnu.org>
[not found] ` <20221226075759.AAF44C00613@vcs2.savannah.gnu.org>
2022-12-26 14:04 ` Stefan Monnier [this message]
2022-12-26 16:45 ` [External] : Re: master cc29fab3a6: Redisplay "invisible" frames that are actually visible on modern X Drew Adams
2022-12-27 13:44 ` Eli Zaretskii
2022-12-27 15:29 ` Stefan Monnier
2022-12-27 16:48 ` Eli Zaretskii
2022-12-27 17:14 ` Stefan Monnier
2022-12-27 17:42 ` [External] : " Drew Adams
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=jwvy1qucll0.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=emacs-devel@gnu.org \
--cc=luangruo@yahoo.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.