From: David Reitter <david.reitter@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: alan@idiocy.org, andlind@gmail.com, emacs-devel@gnu.org
Subject: Re: Redisplay: NS port, high CPU load
Date: Fri, 10 Jun 2016 19:46:01 +1000 [thread overview]
Message-ID: <B3350AE7-AD07-4F69-ACBD-33BF31785CA2@gmail.com> (raw)
In-Reply-To: <83lh2dpetr.fsf@gnu.org>
On Jun 10, 2016, at 7:34 PM, Eli Zaretskii <eliz@gnu.org> wrote:
> If you want it on the release branch, why did you push it to master?
> This just makes things more complicated than they should be.
I guess because I’m stupid. I would have cherry-picked it in the release branch then.
>
>> Also, I would suggest to check whether code like this should indeed trigger an update_frame_tool_bar.
>>
>> (with-temp-buffer
>> (insert "XXX"))
>
> I don't think so. It doesn't here. How did you check that it does on
> your system?
Enable NSTRACE in nsterm.h, specifically for updates.
Run an observe output. Observe that the above causes an update to the toolbar, unlike evaluating other expressions.
next prev parent reply other threads:[~2016-06-10 9:46 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-08 6:04 Redisplay: NS port, high CPU load David Reitter
2016-06-08 7:50 ` Anders Lindgren
2016-06-08 10:44 ` David Reitter
2016-06-08 19:55 ` Alan Third
2016-06-08 20:12 ` David Reitter
2016-06-09 1:03 ` David Reitter
2016-06-09 8:22 ` David Reitter
2016-06-09 9:25 ` Anders Lindgren
2016-06-09 13:04 ` David Reitter
2016-06-09 14:11 ` Anders Lindgren
2016-06-09 18:03 ` David Reitter
2016-06-09 18:52 ` Anders Lindgren
2016-06-09 23:03 ` David Reitter
2016-06-10 6:02 ` Anders Lindgren
2016-06-10 8:16 ` David Reitter
2016-06-10 9:34 ` Eli Zaretskii
2016-06-10 9:46 ` David Reitter [this message]
2016-06-10 10:22 ` Eli Zaretskii
2016-06-10 10:36 ` David Reitter
2016-06-13 18:44 ` Anders Lindgren
2016-06-13 19:16 ` Eli Zaretskii
2016-06-14 12:07 ` David Reitter
2016-06-14 17:02 ` Eli Zaretskii
2016-06-15 3:55 ` Stefan Monnier
2016-06-14 11:50 ` David Reitter
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=B3350AE7-AD07-4F69-ACBD-33BF31785CA2@gmail.com \
--to=david.reitter@gmail.com \
--cc=alan@idiocy.org \
--cc=andlind@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.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 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.