From: Chong Yidong <cyd@stupidchicken.com>
To: martin rudalics <rudalics@gmx.at>
Cc: Alan Mackenzie <acm@muc.de>, 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: Wed, 11 Apr 2007 13:26:44 -0400 [thread overview]
Message-ID: <871wiqkejv.fsf@stupidchicken.com> (raw)
In-Reply-To: <461C71A8.7060401@gmx.at> (martin rudalics's message of "Wed\, 11 Apr 2007 07\:27\:04 +0200")
martin rudalics <rudalics@gmx.at> writes:
>> > Please complain to me about any problems.
>>
>> Well, with that invitation!
>>
>> Fontifying C files takes too long now, so my old machine starts to hang if I
>> step through a buffer or search for a string. xbacktrace seems to consistently
>> include:
>>
>> ...
>
> ... probably due to disabling stealth fontification a couple of weeks ago.
No, it has nothing to do with stealth fontification. The problem is
due to the recent change:
2007-04-09 Alan Mackenzie <acm@muc.de>
Changes to make `narrow-to-defun' and `mark-defun' work properly
in CC Mode:
* progmodes/cc-defs.el (c-beginning-of-defun-1):
* progmodes/cc-cmds.el (c-beginning-of-defun, c-end-of-defun):
Bind beginning/end-of-defun-function to nil around calls to
beginning/end-of-defun.
* progmodes/cc-langs.el (beginning-of-defun-function)
(end-of-defun-function): New c-lang-setvar's.
* progmodes/cc-awk.el (c-awk-beginning-of-defun): Add "(or arg
(setq arg 1))" to enable non-interactive call.
One way to see this is to open xdisp.c, and do C-s method. The
incremental search takes several seconds. Previously, it was
instantaneous.
I think it may be too late for this change. If the problem it is
meant to fix is not serious, maybe this patch should be reverted.
next prev parent reply other threads:[~2007-04-11 17:26 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=871wiqkejv.fsf@stupidchicken.com \
--to=cyd@stupidchicken.com \
--cc=acm@muc.de \
--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 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.