From: Michael Welsh Duggan <mwd@cert.org>
To: "7930\@debbugs.gnu.org" <7930@debbugs.gnu.org>
Subject: bug#7930: (24.0.50; Indentation problem in C-mode)
Date: Thu, 27 Jan 2011 15:22:11 -0500 [thread overview]
Message-ID: <tnty6669jws.fsf_-_@waterbuck.yellow.cert.org> (raw)
In-Reply-To: <handler.7930.B.129615449115675.ack@debbugs.gnu.org> (GNU bug Tracking System's message of "Thu, 27 Jan 2011 13:55:02 -0500")
I now can recreate this problem, although not minimally.
Using the included file pdusource.c:
emacs -Q pdusource.c
M-g g 549 RET
TAB
This will cause the wrong-type-argument error. A bisection shows that
this error was introduced in commit 191882,
acm@muc.de-20101009195828-ajo6zapkxu8oluwz:
Enhance fontification of declarators to take account of the
presence/absence of "typedef".
cc-engine.el (c-forward-type): New &optional param "brace-block-too".
(c-forward-decl-or-cast-1): cdr of return value now indicates the
presence of either or both of a "struct"-like keyword and "typedef".
cc-fonts.el (c-complex-decl-matchers): Remove the heuristic fontification
of declarators which follow a "}".
(c-font-lock-declarations): Fontify declarators according to the
presence/absence of "typedef".
cc-langs.el (c-typedef-kwds c-typedef-key): New lang variable for
"typedef".
(c-typedef-decl-key): New lang variable built from c-typedef-decl-kwds.
--
Michael Welsh Duggan
(mwd@cert.org)
next prev parent reply other threads:[~2011-01-27 20:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-27 19:01 bug#7930: 24.0.50; Indentation problem in C-mode Michael Welsh Duggan
[not found] ` <handler.7930.B.129615449115675.ack@debbugs.gnu.org>
2011-01-27 20:22 ` Michael Welsh Duggan [this message]
2011-01-27 20:26 ` bug#7930: Forgot to include the file Michael Welsh Duggan
2011-02-20 15:26 ` Alan Mackenzie
2011-02-20 19:19 ` Michael Welsh Duggan
2011-02-21 21:36 ` bug#7930: Bug #7930 fixed 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=tnty6669jws.fsf_-_@waterbuck.yellow.cert.org \
--to=mwd@cert.org \
--cc=7930@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).