From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Alan Mackenzie Newsgroups: gmane.emacs.bugs Subject: bug#56818: 28.1; c-mode font-lock issues in Emacs 28 Date: Sat, 30 Jul 2022 13:18:54 +0000 Message-ID: References: <83edy48nsq.fsf@gnu.org> <343d4736-8c6e-eacb-5d7f-3ae10ef486e6@ucar.edu> <00abbbce-f72d-dd4a-7430-f85722c9d9b0@ucar.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="14461"; mail-complaints-to="usenet@ciao.gmane.io" Cc: 56818-done@debbugs.gnu.org, Eli Zaretskii To: Bill Sacks Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Sat Jul 30 15:20:19 2022 Return-path: Envelope-to: geb-bug-gnu-emacs@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 1oHmOB-0003aZ-M8 for geb-bug-gnu-emacs@m.gmane-mx.org; Sat, 30 Jul 2022 15:20:19 +0200 Original-Received: from localhost ([::1]:43804 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1oHmOA-000535-LJ for geb-bug-gnu-emacs@m.gmane-mx.org; Sat, 30 Jul 2022 09:20:18 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:36596) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oHmNx-00052o-BP for bug-gnu-emacs@gnu.org; Sat, 30 Jul 2022 09:20:05 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:44576) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1oHmNu-0002Je-Nk for bug-gnu-emacs@gnu.org; Sat, 30 Jul 2022 09:20:04 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1oHmNu-0001PN-Jv for bug-gnu-emacs@gnu.org; Sat, 30 Jul 2022 09:20:02 -0400 Resent-From: Alan Mackenzie Original-Sender: "Debbugs-submit" Resent-To: bug-gnu-emacs@gnu.org Resent-Date: Sat, 30 Jul 2022 13:20:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: cc-closed 56818 X-GNU-PR-Package: emacs Mail-Followup-To: 56818@debbugs.gnu.org, acm@muc.de, sacks@ucar.edu Original-Received: via spool by 56818-done@debbugs.gnu.org id=D56818.16591871435321 (code D ref 56818); Sat, 30 Jul 2022 13:20:02 +0000 Original-Received: (at 56818-done) by debbugs.gnu.org; 30 Jul 2022 13:19:03 +0000 Original-Received: from localhost ([127.0.0.1]:34323 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1oHmMx-0001Nj-8T for submit@debbugs.gnu.org; Sat, 30 Jul 2022 09:19:03 -0400 Original-Received: from colin.muc.de ([193.149.48.1]:64344 helo=mail.muc.de) by debbugs.gnu.org with smtp (Exim 4.84_2) (envelope-from ) id 1oHmMv-0001N0-8D for 56818-done@debbugs.gnu.org; Sat, 30 Jul 2022 09:19:01 -0400 Original-Received: (qmail 25768 invoked by uid 3782); 30 Jul 2022 13:18:55 -0000 Original-Received: from acm.muc.de (p2e5d52c1.dip0.t-ipconnect.de [46.93.82.193]) (using STARTTLS) by colin.muc.de (tmda-ofmipd) with ESMTP; Sat, 30 Jul 2022 15:18:55 +0200 Original-Received: (qmail 5185 invoked by uid 1000); 30 Jul 2022 13:18:54 -0000 Content-Disposition: inline In-Reply-To: <00abbbce-f72d-dd4a-7430-f85722c9d9b0@ucar.edu> X-Submission-Agent: TMDA/1.3.x (Ph3nix) X-Primary-Address: acm@muc.de X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list 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-mx.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.io gmane.emacs.bugs:238276 Archived-At: Hello, Bill. On Fri, Jul 29, 2022 at 14:38:53 -0600, Bill Sacks wrote: > Unfortunately, I still see an issue in a slightly different context. The > issue appears when function arguments appear on a line following the > function name. This one is harder to provide screen shots for, because > it is a bit more dynamic, but I'll try to walk through how to reproduce > it, referencing two attachments: The starting point is testing_start.c > and the end point is testing.c. If you start with testing_start.c and > then take some steps to get to testing.c, you will notice a few issues > with fontification of "somevar": > (1) Position the cursor at the start of line 2 and hit Tab to put the > cursor on line 2, column 12. Type "int somevar" and notice that > "somevar" remains in the default face rather than being given > font-lock-variable-name-face. > (2) Run M-x font-lock-fontify-buffer to make "somevar" correctly take on > font-lock-variable-name-face. (Interestingly, it seems fixed as soon as > I type "M-x" and get into the minibuffer.) > (3) Delete then retype the "r" in "somevar", noticing that it again > reverts to default face > (4) Repeat step (2) to temporarily fix the fontification > (5) Type " // comment", noticing that "somevar" again loses its > fontification > (6) Repeat step (2) to temporarily fix the fontification > (7) Delete and retype the "t" in "comment", noticing that "somevar" > again loses its fontification. > If my instructions are unclear or you cannot reproduce this, I can > provide a screencast where I illustrate this behavior. Those directions are admirably clear, thanks! > I tested briefly with Emacs 27, and it appears that the problems in (1) > and (3) are new issues in Emacs 28, but (5) and (7) appear in Emacs 27 > as well. What is happening here is a different bug, distinct from bug #56818, with different causes. I've opened a fresh bug for this, bug #56841, putting you on the Cc:. So I'm closing bug #56818 with this post, as it appears to be fixed. [ .... ] > Bill -- Alan Mackenzie (Nuremberg, Germany).