From: Ken Brown <kbrown@cornell.edu>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] emacs 27.1-1
Date: Sat, 15 Aug 2020 17:26:24 -0400 [thread overview]
Message-ID: <605209a3-eb9b-7972-7b57-a6793e065dba@cornell.edu> (raw)
In-Reply-To: <87pn7srlrf.fsf@Rainer.invalid>
On 8/15/2020 11:07 AM, Achim Gratz wrote:
> Ken Brown via Cygwin-announce writes:
>> The following packages have been uploaded to the Cygwin distribution:
>>
>> * emacs-27.1-1
>> * emacs-common-27.1-1
>> * emacs-X11-27.1-1
>> * emacs-w32-27.1-1
>> * emacs-lucid-27.1-1
>
> This release seems to have a serious performance regression when using
> diff-mode on large diffs with long lines (e.g. created by comparing the
> logs of two compilations), especially when combined with
> toggle-truncate-lines. Emacs becomes unresponsive with 100% CPU load
> when scrolling fast, sometimes for several seconds. The CPU time seems
> to be spent in redisplay().
emacs has long had problems with slow redisplay in files with long lines. See,
for example,
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=13675
and all the bugs that have been merged with it. One suggestion I've seen
recently is to try so-long-mode. Does that help?
Do you have reason to think this is Cygwin-specific? If so, it might be related
to the new pty code. Does it help to set CYGWIN=disable_pcon before starting
any Cygwin processes? (*)
Finally, does it matter which version of the emacs binary you use (emacs-w32,
emacs-X11,...)?
Ken
(*) Alternatively, if you don't mind building your own cygwin1.dll, you could
try Takashi's new version of the pty code:
https://cygwin.com/pipermail/cygwin-developers/2020-August/011941.html
I've seen dramatic speedups with this patch installed, though not specifically
with emacs.
next prev parent reply other threads:[~2020-08-15 21:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-11 16:48 Ken Brown via Cygwin-announce
2020-08-15 15:07 ` Achim Gratz
2020-08-15 21:26 ` Ken Brown [this message]
2020-08-16 6:14 ` ASSI
2020-08-16 12:38 ` Achim Gratz
2020-08-16 6:06 ` ASSI
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=605209a3-eb9b-7972-7b57-a6793e065dba@cornell.edu \
--to=kbrown@cornell.edu \
--cc=cygwin@cygwin.com \
/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.
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).