unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: 张海君 <netjune@icloud.com>
To: Alan Mackenzie <acm@muc.de>
Cc: 20266@debbugs.gnu.org
Subject: bug#20266: Emacs doesn't respond when editing the attached c header	file.
Date: Sun, 12 Apr 2015 10:15:15 +0800	[thread overview]
Message-ID: <40D04DD6-2D4F-47AD-BEFA-19AEA5AC0938@icloud.com> (raw)
In-Reply-To: <20150407151616.87042.qmail@mail.muc.de>


> 在 2015年4月7日,23:16,Alan Mackenzie <acm@muc.de> 写道:
> 
> Hello, Netjune.
> 
> In article <mailman.71.1428315070.904.bug-gnu-emacs@gnu.org> you wrote:
>> [-- text/plain, encoding 7bit, charset: us-ascii, 13 lines --]
> 
>> Emacs doesn't respond when editing the attached c header file.
>> Emacs version: 24.4.
> 
>> ------------------------------------
>> Run emacs with "emacs -Q test.h".
>> M-x mark-whole-buffer
>> M-x kill-ring-save
>> M-x end-of-buffer
>> M-x yank
>> Then emacs doesn't respond for about 5 seconds.
>> M-x scroll-down-command. 
>> Then emacs doesn't respond for about 5 seconds too.
> 
> Yes.  This isn't good at all.
> 
>> M-x scroll-down-command.
>> Then emacs doesn't respond for about 5 seconds too.
> 
> I can't actually reproduce this delay.

Try do it more than 4 times, like: M-> M-v M-v M-v M-v M-v.
The delay often happens at the first M-v, but not always.
The delay is about 5 seconds on mac OSX (cpu: 1.4GHz), and is about 2 seconds on linux (cpu: 2.53Ghz).

Or try to input some text (like newline chars) at the end of buffer.
I input a newline at the end of buffer, and emacs didn't respond about 2 seconds on linux.

After apply the patch, there is no delay after yank.







  reply	other threads:[~2015-04-12  2:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-06 10:09 bug#20266: Emacs doesn't respond when editing the attached c header file 张海君
     [not found] ` <mailman.71.1428315070.904.bug-gnu-emacs@gnu.org>
2015-04-07 15:16   ` Alan Mackenzie
2015-04-12  2:15     ` 张海君 [this message]
2015-04-21 16:14       ` Alan Mackenzie
2015-04-25 21:11         ` Alan Mackenzie

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=40D04DD6-2D4F-47AD-BEFA-19AEA5AC0938@icloud.com \
    --to=netjune@icloud.com \
    --cc=20266@debbugs.gnu.org \
    --cc=acm@muc.de \
    /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).