unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Jiajian Huang <wherejoystarts@gmail.com>
Cc: 24271@debbugs.gnu.org
Subject: bug#24271: 25.1; font-lock problem of c++-mode
Date: Sat, 20 Aug 2016 09:56:41 +0300	[thread overview]
Message-ID: <83twegc4ie.fsf@gnu.org> (raw)
In-Reply-To: <7756A5F1-342F-4F55-8D6B-1A41B528DE5A@gmail.com> (message from Jiajian Huang on Sat, 20 Aug 2016 08:42:43 +0800)

> From: Jiajian Huang <wherejoystarts@gmail.com>
> Date: Sat, 20 Aug 2016 08:42:43 +0800
> 
> I recently notice that there's some strange behaviours of the font-lock of the c++-mode.

I don't see it as strange.

> Let's start emacs by `emacs -Q` in the terminal, edit a new file `test.cpp` and save the following contents
> 
> Then put the cursor two lines above the `int main` line, type `int test`, you will find that the color of word `main` changes from *blue* to *black*
> 
> Backspace the current line to `in` or `i`, you will see that the color of `main` change back to *blue*

When you insert "int test", without the semi-colon, your buffer now
has an invalid C++ program, so it's a small wonder the colors change.
When you replace "int test" with "in test", the "in" part is no longer
a C++ type, so it's again small wonder that colors change.

> Is this a emacs bug ?

I don't think it's a bug.

Thanks.





  reply	other threads:[~2016-08-20  6:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-20  0:42 bug#24271: 25.1; font-lock problem of c++-mode Jiajian Huang
2016-08-20  6:56 ` Eli Zaretskii [this message]
     [not found]   ` <1645ABE9-D61A-4DDE-B4D6-94A29A2CC2AA@gmail.com>
2016-08-20  7:52     ` Eli Zaretskii
2016-08-20  7:57     ` Jiajian Huang
2016-08-20  8:15       ` Eli Zaretskii
2016-08-20  8:27         ` Jiajian Huang
2016-08-20  8:36           ` Eli Zaretskii
2019-11-17  7:08       ` Lars Ingebrigtsen

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=83twegc4ie.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=24271@debbugs.gnu.org \
    --cc=wherejoystarts@gmail.com \
    /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).