From: David Reitter <david.reitter@gmail.com>
To: Alan Third <alan@idiocy.org>
Cc: Anders Lindgren <andlind@gmail.com>,
Emacs-Devel devel <emacs-devel@gnu.org>
Subject: Re: Redisplay: NS port, high CPU load
Date: Thu, 9 Jun 2016 18:22:46 +1000 [thread overview]
Message-ID: <F787BFD7-53AA-442E-A3EF-F03C6AE9F98F@gmail.com> (raw)
In-Reply-To: <FA3E0A3D-8E33-46AA-9F79-3BAB479C766B@gmail.com>
On Jun 9, 2016, at 11:03 AM, David Reitter <david.reitter@gmail.com> wrote:
> I can manually cause a call to update_frame_tool_bar by evaluating this expression. I don’t have time to look further right now, but the call to Ffind_file_name_handler is a suspect. See also below.
So far, I have traced it to the use of ENCODE_FILE (encode_file_name) in verify-visited-file-modtime:
filename = ENCODE_FILE (BVAR (b, filename));
Now, file-name-coding-system is utf-8-hfs, and that setting is associated with the error. Setting it to ‘utf-8 makes the bug go away.
What can trigger a redisplay or menu/toolbar update in encode_file_name() for utf-8-hfs?
next prev parent reply other threads:[~2016-06-09 8:22 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 [this message]
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
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
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=F787BFD7-53AA-442E-A3EF-F03C6AE9F98F@gmail.com \
--to=david.reitter@gmail.com \
--cc=alan@idiocy.org \
--cc=andlind@gmail.com \
--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 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).