From: Aaron Jensen <aaronjensen@gmail.com>
To: Alan Third <alan@idiocy.org>,
Aaron Jensen <aaronjensen@gmail.com>,
52085@debbugs.gnu.org
Subject: bug#52085: 29.0.50; Frame occasionally fails to paint while screen sharing on macOS
Date: Fri, 3 Dec 2021 00:14:10 -0500 [thread overview]
Message-ID: <CAHyO48x8MrdqqutAHutJEDicnSb--dddrVFTc=jZPmVjNNbqGQ@mail.gmail.com> (raw)
In-Reply-To: <YalHCvAdtN4Acg6i@idiocy.org>
On Thu, Dec 2, 2021 at 5:22 PM Alan Third <alan@idiocy.org> wrote:
>
> On Wed, Nov 24, 2021 at 08:12:53PM -0500, Aaron Jensen wrote:
> > I still need to try this with emacs -Q, but I have seen this for some
> > time now (possibly since Alan's recent batch of changes to macOS
> > rendering)
> >
> > If I am screen sharing on zoom, I will often issue a command that I
> > expect to repaint the frame and it will not. If I issue another then it
> > repaints immediately with both commands having been realized. This
> > *only* happens when screen sharing with Zoom. I will try other screen
> > sharing software to see if it is a Zoom specific thing. I am typically
> > sharing just the Emacs window (and maybe an iTerm and a browser), but
> > never full screen sharing.
> >
> > Alan, is there anything that you could think of that could cause
> > something like this to happen? Is there logging I could add to help get
> > to the bottom of it?
>
> Probably the first thing you could do is check that [EmacsLayer
> display] is being called at the right time.
>
> But I can't really think of any particular reason for this to happen.
How do I enable and observe NSTRACE?
next prev parent reply other threads:[~2021-12-03 5:14 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-25 1:12 bug#52085: 29.0.50; Frame occasionally fails to paint while screen sharing on macOS Aaron Jensen
2021-11-30 15:49 ` Rudolf Adamkovič via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-30 18:18 ` Aaron Jensen
2021-12-02 12:45 ` Rudolf Adamkovič via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-12-07 20:30 ` Rudolf Adamkovič via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-12-02 22:22 ` Alan Third
2021-12-02 22:22 ` Alan Third
2021-12-03 5:14 ` Aaron Jensen [this message]
2021-12-04 10:48 ` Alan Third
2021-12-08 3:14 ` Aaron Jensen
2021-12-08 10:21 ` Rudolf Adamkovič via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-12-08 21:23 ` Alan Third
2021-12-08 21:33 ` Aaron Jensen
2021-12-09 7:26 ` Eli Zaretskii
2021-12-09 7:38 ` Aaron Jensen
2021-12-12 12:08 ` Alan Third
2021-12-19 21:57 ` Aaron Jensen
2022-07-23 14:37 ` Aaron Jensen
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='CAHyO48x8MrdqqutAHutJEDicnSb--dddrVFTc=jZPmVjNNbqGQ@mail.gmail.com' \
--to=aaronjensen@gmail.com \
--cc=52085@debbugs.gnu.org \
--cc=alan@idiocy.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).