From: Alan Mackenzie <acm@muc.de>
Cc: bug-cc-mode@gnu.org, herberteuler@hotmail.com, rms@gnu.org,
emacs-devel@gnu.org
Subject: Re: On the behavior of `c-beginning-of-defun'
Date: 20 Jan 2007 20:37:53 +0100 [thread overview]
Message-ID: <20070120205053.GA2078@muc.de> (raw)
In-Reply-To: <200612301209.55371.xugp@alibaba-inc.com>
Hi, Guanpeng!
On Sat, Dec 30, 2006 at 12:09:55PM +0800, Herbert Euler wrote:
[ .... ]
> I planned to use `c-beginning-of-defun' and `c-end-of-defun'. But I
> found a strange behavior of `c-beginning-of-defun'. In the attatched
> `x.c' file, `c-beginning-of-defun' moves point differently for the
> function `main' and others. For the `main' function, it moves point to
> the open of the function body, i.e. before the { at line 6; for other
> functions, it moves point to the beginning of the definition of the
> function, i.e. before the type specification of the return value of the
> function.
[ .... ]
I've fixed this bug, basically by analysing K&R regions much more
rigorously. I've just committed cc-defs.el and cc-engine.el to
savannah.gnu.org.
Please try out the amended version and let me know if anything's not
right.
> Thanks in advance.
Thank you for the bug report!
> int
> main (argc, argv)
> int argc;
> char *argv[];
> {
> if ()
> ;
> }
--
Alan Mackenzie (Ittersbach, Germany).
next prev parent reply other threads:[~2007-01-20 19:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200612301209.55371.xugp@alibaba-inc.com>
2006-12-30 20:15 ` On the behavior of `c-beginning-of-defun' Alan Mackenzie
2006-12-31 9:40 ` Herbert Euler
2006-12-31 22:13 ` Richard Stallman
2007-01-01 22:30 ` Alan Mackenzie
2007-01-02 1:19 ` Herbert Euler
2007-01-20 19:37 ` Alan Mackenzie [this message]
2007-01-21 1:19 Herbert Euler
2007-01-21 1:22 ` Herbert Euler
2007-01-21 19:33 ` Alan Mackenzie
2007-01-22 2:06 ` Herbert Euler
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=20070120205053.GA2078@muc.de \
--to=acm@muc.de \
--cc=bug-cc-mode@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=herberteuler@hotmail.com \
--cc=rms@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.