all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Anders Lindgren <andlind@gmail.com>
Cc: david.reitter@gmail.com, alan@idiocy.org, emacs-devel@gnu.org
Subject: Re: Redisplay: NS port, high CPU load
Date: Mon, 13 Jun 2016 22:16:16 +0300	[thread overview]
Message-ID: <837fdsgarj.fsf@gnu.org> (raw)
In-Reply-To: <CABr8ebYiF7Ac+w_26+6Nc9M5+6t62Yw8tpWv5gUhB6MamzYr0A@mail.gmail.com> (message from Anders Lindgren on Mon, 13 Jun 2016 20:44:15 +0200)

> From: Anders Lindgren <andlind@gmail.com>
> Date: Mon, 13 Jun 2016 20:44:15 +0200
> Cc: Eli Zaretskii <eliz@gnu.org>, Alan Third <alan@idiocy.org>, emacs-devel <emacs-devel@gnu.org>
> 
> Unfortunately, I can't reproduce this either, but I have a theory on what is going on.

David said that it didn't happen in "emacs -Q", but did happen in his
normal setup, and AFAIU intended to come up with a recipe.

> When it comes to the HFS coding rewrite, I still think it is valid. The documentation of `define-coding-system'
> indicated that it expects the pre-write function to convert the current buffer and that the two parameters are
> only there for backward compatibility. The function, before the rewrite, was clearly written for an older version
> of `define-coding-system'.

That's not the issue.  The issue is what change(s) to install on the
release branch.  We've lived with the current form of the utf-8-hfs's
pre-write conversion for a long time, so if it is not the root cause
behind the CPU load, I'd like to leave it alone on the release branch,
and fix the real problem instead.



  reply	other threads:[~2016-06-13 19:16 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
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 [this message]
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=837fdsgarj.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=alan@idiocy.org \
    --cc=andlind@gmail.com \
    --cc=david.reitter@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 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.