From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Eli Zaretskii <eliz@gnu.org>
Cc: luangruo@yahoo.com, emacs-devel@gnu.org
Subject: Re: master cc29fab3a6: Redisplay "invisible" frames that are actually visible on modern X
Date: Tue, 27 Dec 2022 10:29:19 -0500 [thread overview]
Message-ID: <jwvpmc47u66.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <83o7rp0xn1.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 27 Dec 2022 15:44:18 +0200")
>> 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.
>
> I'm not sure I agree. I believe this could belong to some new GUI
> ideas (all of which are invariably copy-cat'ed from MS-Windows ;-),
> whereby you have a means of showing a small-but-still-readable image
> of an otherwise invisible frame, e.g., by hovering the mouse above
> some desktop icon or widget.
If there's some representation of that frame somewhere on the screen,
then I think it belongs in the `icon`ified state, not the
`invisible` state.
> If that is the intent,
In my experience the intent of `invisible` frames is for them to be
literally invisible as if the frame did not exist at all.
Quoting from the docstring of `make-frame-invisible`:
On graphical displays, invisible frames are not updated and are
usually not displayed at all, even in a window system’s "taskbar".
> But I do think this should be an optional feature (we could argue
> later about the defaults). In an Emacs session with a dozen
> invisible/iconified frames, updating those frames without the user's
> say-so could be a misfeature and a performance hit.
Hmm... didn't think of that aspect, but indeed, my Emacs sessions usually
grow to around a hundred frames, the vast majority of which are `icon`ified.
The usual redisplay optimizations should hopefully keep the performance
impact in check, tho (except for those iconified frames that display
a buffer that's changed in the background, I guess).
Rather than rely on "optional feature", would it be possible to rely on
"expose events" to detect when an iconified frame needs to be updated?
Stefan
next prev parent reply other threads:[~2022-12-27 15:29 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 ` master cc29fab3a6: Redisplay "invisible" frames that are actually visible on modern X Stefan Monnier
2022-12-26 16:45 ` [External] : " Drew Adams
2022-12-27 13:44 ` Eli Zaretskii
2022-12-27 15:29 ` Stefan Monnier [this message]
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=jwvpmc47u66.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=eliz@gnu.org \
--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.