unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Alan Mackenzie <acm@muc.de>
To: Chong Yidong <cyd@stupidchicken.com>
Cc: martin rudalics <rudalics@gmx.at>,
	Nick Roberts <nickrob@snap.net.nz>,
	emacs-devel@gnu.org
Subject: Re: narrow-to-defun and mark-defun now work properly for CC Mode.
Date: 11 Apr 2007 22:22:20 +0200	[thread overview]
Message-ID: <20070411214155.GB1818@muc.de> (raw)
In-Reply-To: <20070411210916.GA1818@muc.de>

Hallo, again!

On Wed, Apr 11, 2007 at 10:09:16PM +0100, Alan Mackenzie wrote:
> 'Evening, Chong!

> On Wed, Apr 11, 2007 at 01:53:30PM -0400, Chong Yidong wrote:
> > Chong Yidong <cyd@stupidchicken.com> writes:

> > One way to see this [ speed problems caused by the latest CC Mode
> > patch] is to open xdisp.c, and do C-s method.  The incremental search
> > takes several seconds.  Previously, it was instantaneous.

> > Another data point: 

> > - Open xdisp.c
> > - M->

> > On my Pentium IV, M-> takes 30 seconds to complete.

> I have a 1.2 GHz Athlon, and for me these operations are instantaneous
> enough.  I start Emacs with -Q.  With C-s method, I don't see any delay
> at all, and M-> takes well under half a second.  I have checked (by
> doing C-x n d) that I have my own latest changes in my Emacs.

[ .... ]

> I last updated my Emacs a week ago.  I'm going to update it again in the
> next few minutes, to see if some other change in the last few days is
> interacting badly with my changes.

I've just updated and rebuild my Emacs 22.  I still don't see any of the
speed problems others have.

> -- 
> Alan.

  reply	other threads:[~2007-04-11 20:22 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-09 11:18 narrow-to-defun and mark-defun now work properly for CC Mode Alan Mackenzie
2007-04-09 17:00 ` Eric Hanchrow
2007-04-11  0:29 ` Nick Roberts
2007-04-11  5:27   ` martin rudalics
2007-04-11 17:26     ` Chong Yidong
2007-04-11 17:53       ` Chong Yidong
2007-04-11 18:53         ` Eli Zaretskii
2007-04-11 19:49         ` Alan Mackenzie
2007-04-11 20:22           ` Alan Mackenzie [this message]
2007-04-11 21:53             ` Robert J. Chassell
2007-04-11 20:51           ` Chong Yidong
2007-04-11 21:02             ` Alan Mackenzie
2007-04-11 22:19               ` Nick Roberts
2007-04-12 18:45                 ` Alan Mackenzie
2007-04-12 22:04                   ` Nick Roberts
2007-04-12 17:43               ` Richard Matthew Stallman
2007-04-12 19:08               ` Stefan Monnier
2007-04-11 21:21             ` Kim F. Storm
2007-04-12  3:18             ` Eli Zaretskii
2007-04-12  3:51               ` Nick Roberts
2007-04-12 19:08                 ` Eli Zaretskii
2007-04-11 19:51         ` Kim F. Storm
2007-04-11 21:27         ` Edward O'Connor
2007-04-11 19:46   ` Richard Matthew Stallman
2007-04-11 18:04 ` Chong Yidong
2007-04-11 23:04   ` Richard Matthew Stallman

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=20070411214155.GB1818@muc.de \
    --to=acm@muc.de \
    --cc=cyd@stupidchicken.com \
    --cc=emacs-devel@gnu.org \
    --cc=nickrob@snap.net.nz \
    --cc=rudalics@gmx.at \
    /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).