From: Oleh Krehel <ohwoeowho@gmail.com>
To: Alan Mackenzie <acm@muc.de>
Cc: 20245@debbugs.gnu.org
Subject: bug#20245: 24.5; c++-mode font-lock broken by the last commit to emacs24 branch
Date: Thu, 2 Apr 2015 15:10:57 +0200 [thread overview]
Message-ID: <CAA01p3qu1xk_sP_F9atwTtYh=2OzZ0jDCyodLDEWiTFr5gE=jA@mail.gmail.com> (raw)
In-Reply-To: <20150402124846.96754.qmail@mail.muc.de>
Hi Alan,
On Thu, Apr 2, 2015 at 2:48 PM, Alan Mackenzie <acm@muc.de> wrote:
>> I just tried "23bb07e", the latest commit on master, but this issue isn't fixed.
>> The include statements look the same as in the screenshot.
>
> That's a pity. It looks like there's a separate problem with the "fix"
> from February.
>
> Is there any chance you could send me a copy of the file which triggers
> the bug, a description of exactly what you do to see it, and (unless you
> start from emacs -Q) a copy of your CC Mode configuration (generated by
> C-c C-b)?
The bug is reproducible with emacs -Q. You can get an example file at:
https://github.com/dune-project/dune-pdelab-howto/blob/master/src/navier-stokes/cgstokes_instat.cc
To trigger the bug, just M->, and then scroll up with the mouse to the
start of the file where the headers are. Random headers will be
partially highlighted with 'default instead of 'font-lock-string-face.
Oleh
next prev parent reply other threads:[~2015-04-02 13:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-02 6:55 bug#20245: 24.5; c++-mode font-lock broken by the last commit to emacs24 branch Oleh Krehel
[not found] ` <mailman.3171.1427958137.31049.bug-gnu-emacs@gnu.org>
2015-04-02 9:51 ` Alan Mackenzie
2015-04-02 10:19 ` Oleh Krehel
2015-04-03 12:46 ` Alan Mackenzie
2015-04-06 22:40 ` Alan Mackenzie
2015-04-07 12:17 ` Oleh Krehel
[not found] ` <mailman.3178.1427970015.31049.bug-gnu-emacs@gnu.org>
2015-04-02 12:48 ` Alan Mackenzie
2015-04-02 13:10 ` Oleh Krehel [this message]
2015-04-02 13:32 ` 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='CAA01p3qu1xk_sP_F9atwTtYh=2OzZ0jDCyodLDEWiTFr5gE=jA@mail.gmail.com' \
--to=ohwoeowho@gmail.com \
--cc=20245@debbugs.gnu.org \
--cc=acm@muc.de \
/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).