unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Aaron Jensen <aaronjensen@gmail.com>
Cc: alan@idiocy.org, 52085@debbugs.gnu.org
Subject: bug#52085: 29.0.50; Frame occasionally fails to paint while screen sharing on macOS
Date: Thu, 09 Dec 2021 09:26:38 +0200	[thread overview]
Message-ID: <83tufiutld.fsf@gnu.org> (raw)
In-Reply-To: <CAHyO48weimKajvTGcGYTtOYV=x0x0Q2gKxuM00h6LcmTyFNLCQ@mail.gmail.com> (message from Aaron Jensen on Wed, 8 Dec 2021 16:33:06 -0500)

> From: Aaron Jensen <aaronjensen@gmail.com>
> Date: Wed, 8 Dec 2021 16:33:06 -0500
> 
> > To be honest, if I just want to see when one function is called I
> > stick in 'NSLog (@"Moo")' or whatever. There's too much output in
> > NSTRACE and I'm sure that sometimes it doesn't print out results from
> > things that are called deep in the toolkit code.
> 
> Well, I can say with some certainty that those messages are the only
> ones appearing under typical operations like key presses. I can insert
> newlines into the terminal and observe that only those are emitted
> when I press keys or even scroll. So the display function is not being
> called unless there is some other wildness going on with the tracing.
> Do you expect it to be called every render? (It is also not called
> when I run M-: (redisplay))

I'm not tracking this discussion, so apologies if what I say below
makes no sense.  However, the Emacs display engine avoids redrawing
anything if it concludes that what's on the glass is correct.  So just
calling 'redisplay', or making some simple changes that don't require
significant redrawing, don't necessarily result in calls to low-level
drawing functions, you need to do something drastic to force those
with 100% certainty.

HTH





  reply	other threads:[~2021-12-09  7:26 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
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 [this message]
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=83tufiutld.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=52085@debbugs.gnu.org \
    --cc=aaronjensen@gmail.com \
    --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).