From: Rolf Ade <rolf@pointsman.de>
To: 23818@debbugs.gnu.org
Subject: bug#23818: 25.0.95.3: c-beginning-of-defun misbehaviour
Date: Wed, 22 Jun 2016 02:19:21 +0200 [thread overview]
Message-ID: <87ziqeaxdi.fsf@linux-qg7d.fritz.box> (raw)
The same in 24.5 and 25.0.95.3:
emacs -Q
Open some random emtpy buffer foo.c, put it in c-mode (M-x c-mode) and
insert the following C code:
#define DBG(x) x
DBG(
static void __dbgAttr () {
/* something */
}
)
int main (void)
{
int i;
i++;
i++;
return i;
}
int foo ()
{
int i;
i++;
i++;
return 1;
}
Put the point inside function main and C-M-home (or M-x
c-beginning-of-defun). Instead of the beginning of main() the point is
here:
_P_DBG(
...
Far away from
_P_int main(void)
...
This isn't "unbalanced braces in preprocessor statements are
horrendously difficult to parse" as in bug #23775, there are no
unbalanced braces everywhere. It's that some code above the code of a
syntactical correct function disturbs c-beginning-of-defun in finding
the beginning of the function.
Put the point into or at the end of function foo, do C-M-home and you
are at the beginning of function foo. Do C-M-home again, and you are not
at the beginning of main, but of the beginning of DBG.
Remove the DBG(). Now C-M-home works, even if the point is inside or the
end of main().
next reply other threads:[~2016-06-22 0:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-22 0:19 Rolf Ade [this message]
[not found] ` <mailman.2009.1466608581.1216.bug-gnu-emacs@gnu.org>
2016-06-24 14:43 ` bug#23818: 25.0.95.3: c-beginning-of-defun misbehaviour Alan Mackenzie
[not found] ` <mailman.1962.1466554808.1216.bug-gnu-emacs@gnu.org>
2016-06-22 8:54 ` Alan Mackenzie
2016-06-22 15:14 ` Eli Zaretskii
2016-06-24 15:02 ` Alan Mackenzie
2016-06-28 23:22 ` bug#23775: " Rolf Ade
2016-06-29 20:26 ` Alan Mackenzie
2016-06-29 20:27 ` Alan Mackenzie
2016-06-29 0:57 ` Rolf Ade
2017-08-08 21:42 ` Rolf Ade
2017-08-13 13:17 ` 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=87ziqeaxdi.fsf@linux-qg7d.fritz.box \
--to=rolf@pointsman.de \
--cc=23818@debbugs.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 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).