From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: cc-mode fontification feels random Date: Sun, 06 Jun 2021 20:06:23 +0300 Message-ID: <83tumahqi8.fsf@gnu.org> References: <86a85d26-75c0-e4a3-e8d3-244c5346dd3a@dancol.org> <83bl8ji4sw.fsf@gnu.org> <837dj7i2mh.fsf@gnu.org> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="38067"; mail-complaints-to="usenet@ciao.gmane.io" Cc: dancol@dancol.org, emacs-devel@gnu.org To: Alan Mackenzie Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sun Jun 06 19:07:41 2021 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1lpwFP-0009ei-6Y for ged-emacs-devel@m.gmane-mx.org; Sun, 06 Jun 2021 19:07:39 +0200 Original-Received: from localhost ([::1]:60700 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1lpwFN-0003L4-PU for ged-emacs-devel@m.gmane-mx.org; Sun, 06 Jun 2021 13:07:37 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:37492) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1lpwEC-0002TZ-HL for emacs-devel@gnu.org; Sun, 06 Jun 2021 13:06:24 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:54466) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1lpwEC-0001S6-8a; Sun, 06 Jun 2021 13:06:24 -0400 Original-Received: from 84.94.185.95.cable.012.net.il ([84.94.185.95]:1859 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1lpwEB-0002DG-Qk; Sun, 06 Jun 2021 13:06:24 -0400 In-Reply-To: (message from Alan Mackenzie on Sun, 6 Jun 2021 14:19:00 +0000) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:270484 Archived-At: > Date: Sun, 6 Jun 2021 14:19:00 +0000 > From: Alan Mackenzie > Cc: dancol@dancol.org, emacs-devel@gnu.org > > By "background fontification" I meant stealth fontification (and should > have said so). This is, sadly, disabled by default. If it were to be > enabled again, I was envisaging some sort of signal from jit-lock stealth > fontification when the stealth had determined a buffer was completely > fontified. When a buffer has been completely fontified by jit-lock stealth fontification, that buffer no longer appears in jit-lock-stealth-buffers. Is that good enough? But yes, since stealth fontifications are disabled by default, this isn't the way to make CC mode fontifications more accurate. > Yes. By CC Mode's fontification detecting a symbol, foo, must be a type, > and entering it into its internal table. I am thinking that immediately > following, CC Mode could scan the entire buffer and refontify occurrences > of foo which hadn't yet got font-lock-type-face. You could still do that, but it could be costly, and slow down redisplay, no?