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 troubles and Emacs 29 Date: Tue, 10 Jan 2023 14:57:04 +0200 Message-ID: <83k01uo8db.fsf@gnu.org> References: <874jt0hw7p.fsf.ref@yahoo.com> <874jt0hw7p.fsf@yahoo.com> <838ribq48f.fsf@gnu.org> <87zgarhl7j.fsf@yahoo.com> <83zgarodeh.fsf@gnu.org> <87v8lfgpwf.fsf@yahoo.com> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="25766"; mail-complaints-to="usenet@ciao.gmane.io" Cc: acm@muc.de, emacs-devel@gnu.org To: Po Lu Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Tue Jan 10 14:27:19 2023 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 1pFEet-0006Nv-G6 for ged-emacs-devel@m.gmane-mx.org; Tue, 10 Jan 2023 14:27:19 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1pFEBH-0005yO-Pd; Tue, 10 Jan 2023 07:56:43 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1pFEBC-0005wv-CV for emacs-devel@gnu.org; Tue, 10 Jan 2023 07:56:39 -0500 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1pFEBB-0003jJ-DC; Tue, 10 Jan 2023 07:56:37 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=56rhWBRMrDGMfVUrvEn5ayyY8Ax+KZetlnES0ytj1b8=; b=fuuCzsqmdn4r UoPo++uvd33VzhdBFBw7Ik/Zmtx2jx7qVngD0Orf3J60G+RQs8G0hbL8tgScj0GX2D6X0LEYhN053 4VPxO6y8/3oqpZm2BMpZ6IKSfi1uXW6de4dXYZ4/ANi39++5gY2RwFfRpAtkKCIj+zPUxrXLIm7iz PB78g2oxPZXPZxkrUAYeFUqkHyWY8JrpNGk7jvnHnyZA+F9q7s63IUP9AYElxnAPQ2vbHNRLITVQP TB+ZThKtU1AiatmG+7S4L7ASR+lc28mFfsztrq7WhZXGVWefob53xocxj/NGqbMYQnL9AvENQfywX a6xmvT2qpYI5UNvm22rvfA==; Original-Received: from [87.69.77.57] (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 1pFEB9-00066d-M9; Tue, 10 Jan 2023 07:56:37 -0500 In-Reply-To: <87v8lfgpwf.fsf@yahoo.com> (message from Po Lu on Tue, 10 Jan 2023 09:05:36 +0800) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 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-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:302313 Archived-At: > From: Po Lu > Cc: Alan Mackenzie , emacs-devel@gnu.org > Date: Tue, 10 Jan 2023 09:05:36 +0800 > > Eli Zaretskii writes: > > >> Date: Mon, 9 Jan 2023 15:48:12 +0000 > >> Cc: Eli Zaretskii , emacs-devel@gnu.org > >> From: Alan Mackenzie > >> > >> On Mon, Jan 09, 2023 at 21:49:20 +0800, Po Lu wrote: > >> > Eli Zaretskii writes: > >> > >> > > Is there a bug number for this issue? if so, could you please tell > >> > > what it is? > >> > >> One of the bugs is bug #59671. > > > > I see no user-facing problems with the recipe there. It sounds like > > you are discussing some internal feature of CC mode that potentially > > misbehaves in that case. Why should I, as a user, care? More > > importantly, why should I, as an Emacs maintainer, be worried due to > > this problem, which Po Lu described as a "major regression"? I don't > > even see a regression, let alone a major one. What did I miss? > > That's just one bug of many. If you look at the CC Mode bug tracker for > November, you'll see a lot of bugs that boil down to this: after 25 to > 60 minutes of editing in a buffer, the entire buffer is filled with > green splotches (making fontification useless) and C Mode has to be > re-enabled, because CC Mode keeps misrecognizing and fontifying > identifiers as types. If this is so, I find it strange that we don't have heaps of bug reports about this in our bug tracker. I doubt that anyone could ignore the terrible misbehavior you describe, if indeed the description is accurate and not exaggerated. I guess we will have to wait till the pretest to see how bad that is in practice.