unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Jiajian Huang <wherejoystarts@gmail.com>
Cc: 24271@debbugs.gnu.org
Subject: bug#24271: 25.1; font-lock problem of c++-mode
Date: Sun, 17 Nov 2019 08:08:29 +0100	[thread overview]
Message-ID: <874kz3dloy.fsf@gnus.org> (raw)
In-Reply-To: <02148DC1-20D2-41B8-BA43-CFBE6A07C3F6@gmail.com> (Jiajian Huang's message of "Sat, 20 Aug 2016 15:57:02 +0800")

Jiajian Huang <wherejoystarts@gmail.com> writes:

> This is a more serious example. As you can see, I normally input such
> a short line “using std::string”, the color have change 6 times !  I
> don’s think any of them is a “valid” C++ program except the last one.
>
> I’ve not seen any other major mode has such a “feature”. This is my
> first time get into c++-mode. Because of this mechanism, the current
> input area keep “flashing” too much when keep typing fast within a
> buffer full of words even under such a light color theme.  I feel that
> it’s so different from other major mode(python-mode etc.) soon as I
> switch to c++-mode. Maybe it’s not a bug, but I don’t think it’s a
> good feature.

I tried the recipe in Emacs 27, and it seems like c++ mode is much
calmer these days.  There are one three changes I see to the
fontification while typing that line, and none of them are very
attention-grabbing (i.e., none of them flash red bold at me), so I'm
going to go ahead and guess that this has been tweaked in the years
since this was reported, and I'm closing this bug report.

Please reopen if it's still an issue.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





      parent reply	other threads:[~2019-11-17  7:08 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
     [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 [this message]

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=874kz3dloy.fsf@gnus.org \
    --to=larsi@gnus.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).