From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.bugs Subject: bug#24271: 25.1; font-lock problem of c++-mode Date: Sat, 20 Aug 2016 10:52:45 +0300 Message-ID: <83lgzrdghe.fsf@gnu.org> References: <7756A5F1-342F-4F55-8D6B-1A41B528DE5A@gmail.com> <83twegc4ie.fsf@gnu.org> <1645ABE9-D61A-4DDE-B4D6-94A29A2CC2AA@gmail.com> Reply-To: Eli Zaretskii NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Trace: blaine.gmane.org 1471679601 10842 195.159.176.226 (20 Aug 2016 07:53:21 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Sat, 20 Aug 2016 07:53:21 +0000 (UTC) Cc: 24271@debbugs.gnu.org To: Jiajian Huang Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Sat Aug 20 09:53:17 2016 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1bb15h-0002Xp-0I for geb-bug-gnu-emacs@m.gmane.org; Sat, 20 Aug 2016 09:53:17 +0200 Original-Received: from localhost ([::1]:60187 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bb15e-0004ws-50 for geb-bug-gnu-emacs@m.gmane.org; Sat, 20 Aug 2016 03:53:14 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:35797) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bb15W-0004vl-30 for bug-gnu-emacs@gnu.org; Sat, 20 Aug 2016 03:53:07 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bb15R-00063B-Vh for bug-gnu-emacs@gnu.org; Sat, 20 Aug 2016 03:53:05 -0400 Original-Received: from debbugs.gnu.org ([208.118.235.43]:36955) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bb15R-000637-S8 for bug-gnu-emacs@gnu.org; Sat, 20 Aug 2016 03:53:01 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1bb15R-0002gD-Mi for bug-gnu-emacs@gnu.org; Sat, 20 Aug 2016 03:53:01 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Eli Zaretskii Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Sat, 20 Aug 2016 07:53:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 24271 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: Original-Received: via spool by 24271-submit@debbugs.gnu.org id=B24271.147167956710282 (code B ref 24271); Sat, 20 Aug 2016 07:53:01 +0000 Original-Received: (at 24271) by debbugs.gnu.org; 20 Aug 2016 07:52:47 +0000 Original-Received: from localhost ([127.0.0.1]:34667 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1bb15D-0002fl-L5 for submit@debbugs.gnu.org; Sat, 20 Aug 2016 03:52:47 -0400 Original-Received: from eggs.gnu.org ([208.118.235.92]:44727) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1bb15C-0002fV-0O for 24271@debbugs.gnu.org; Sat, 20 Aug 2016 03:52:46 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bb153-00060Q-NK for 24271@debbugs.gnu.org; Sat, 20 Aug 2016 03:52:40 -0400 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:58859) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bb153-00060M-Jm; Sat, 20 Aug 2016 03:52:37 -0400 Original-Received: from 84.94.185.246.cable.012.net.il ([84.94.185.246]:1150 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_128_CBC_SHA1:128) (Exim 4.82) (envelope-from ) id 1bb152-0007BF-R7; Sat, 20 Aug 2016 03:52:37 -0400 In-reply-to: <1645ABE9-D61A-4DDE-B4D6-94A29A2CC2AA@gmail.com> (message from Jiajian Huang on Sat, 20 Aug 2016 15:39:58 +0800) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 208.118.235.43 X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.org gmane.emacs.bugs:122408 Archived-At: Please keep the bug address on the CC list. Forwarding to the bug tracker, since the response was sent only to me: > From: Jiajian Huang > Date: Sat, 20 Aug 2016 15:39:58 +0800 > > Hi, Thanks for your reply. > > I’m not meaning to write invalid C++ program intentionally, like making a “int test” into “in test”. > > When we’re typing “int test”, we type the “i” first then “n”, then “t”, then “ “(space), then “test”, namely, > > “i” -> “in” -> “int” -> “int “ -> … -> “int test”, > > even “normally” typing, the syntax keeping changing. Let’s keep tracking this procedure. > > > > As you can see, none of the above images shows a “valid” C++ program. But the color(or the font style) has at least > changed twice. Base on what you’ve point out, the color should change once the “i” is input and keep unbold till image 4 > since none of them is valid. > > This could happen in any other place when typing in c++-mode, like > > Example 1 > > > Why the “vector” in the first image and third is not turn into “bold red” ? > Why the “vec” in the second image is turn into “bold red” ? > > Example 2 > > > 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. > > Thanks. This misses the images you sent, so please re-send them to the bug address.