From: Alan Mackenzie <acm@muc.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Po Lu <luangruo@yahoo.com>, emacs-devel@gnu.org
Subject: Re: CC Mode troubles and Emacs 29
Date: Tue, 10 Jan 2023 17:37:18 +0000 [thread overview]
Message-ID: <Y72iTtonXCBHEUrm@ACM> (raw)
In-Reply-To: <83k01uo8db.fsf@gnu.org>
Hello, Eli.
On Tue, Jan 10, 2023 at 14:57:04 +0200, Eli Zaretskii wrote:
> > From: Po Lu <luangruo@yahoo.com>
> > Cc: Alan Mackenzie <acm@muc.de>, emacs-devel@gnu.org
> > Date: Tue, 10 Jan 2023 09:05:36 +0800
> > Eli Zaretskii <eliz@gnu.org> writes:
> > >> Date: Mon, 9 Jan 2023 15:48:12 +0000
> > >> Cc: Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org
> > >> From: Alan Mackenzie <acm@muc.de>
[ .... ]
> > >> One of the bugs is bug #59671.
[ .... ]
> > 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.
We do have such heaps, where "this" is understood to be about the
fontification bugs, one of which Gregory accurately summarised.
Some of these bugs are 58534, 58537, 58795, 58796, 58772, 58883, 59032,
59070, 59233, 59267, 59051, 59427, which have all been fixed.
Additionally there are 59234, 59671 (the bug mentioned earlier) for which
patches are available but not yet committed, and 59216, for which there
is, as yet, no patch.
> I doubt that anyone could ignore the terrible misbehavior you describe,
> if indeed the description is accurate and not exaggerated.
I don't think there was exaggeration, here.
> I guess we will have to wait till the pretest to see how bad that is
> in practice.
Why shouldn't I fix it before the pretest? As mentioned above, the patch
is available.
--
Alan Mackenzie (Nuremberg, Germany).
next prev parent reply other threads:[~2023-01-10 17:37 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <874jt0hw7p.fsf.ref@yahoo.com>
2023-01-09 9:51 ` CC Mode troubles and Emacs 29 Po Lu
2023-01-09 12:31 ` Eli Zaretskii
2023-01-09 13:49 ` Po Lu
2023-01-09 15:48 ` Alan Mackenzie
2023-01-09 16:56 ` Eli Zaretskii
2023-01-10 1:05 ` Po Lu
2023-01-10 12:57 ` Eli Zaretskii
2023-01-10 14:13 ` Gregory Heytings
2023-01-11 1:36 ` Po Lu
2023-01-11 1:46 ` Po Lu
2023-01-11 9:27 ` Gregory Heytings
2023-01-11 10:12 ` Po Lu
2023-01-11 13:27 ` Eli Zaretskii
2023-01-11 14:17 ` Po Lu
2023-01-11 14:27 ` Gregory Heytings
2023-01-10 17:37 ` Alan Mackenzie [this message]
2023-01-10 17:50 ` Eli Zaretskii
2023-01-09 16:36 ` Eli Zaretskii
2023-01-10 9:26 ` Gregory Heytings
2023-01-10 9:49 ` Po Lu
2023-01-10 10:06 ` Gregory Heytings
2023-01-10 17:05 ` Alan Mackenzie
2023-01-09 15:52 ` Alan Mackenzie
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=Y72iTtonXCBHEUrm@ACM \
--to=acm@muc.de \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=luangruo@yahoo.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).