From: Po Lu <luangruo@yahoo.com>
To: Gregory Heytings <gregory@heytings.org>
Cc: Eli Zaretskii <eliz@gnu.org>, acm@muc.de, emacs-devel@gnu.org
Subject: Re: CC Mode troubles and Emacs 29
Date: Wed, 11 Jan 2023 09:46:47 +0800 [thread overview]
Message-ID: <87v8ldg7w8.fsf@yahoo.com> (raw)
In-Reply-To: <87zgapg8di.fsf@yahoo.com> (Po Lu's message of "Wed, 11 Jan 2023 09:36:25 +0800")
[-- Attachment #1: Type: text/plain, Size: 507 bytes --]
Po Lu <luangruo@yahoo.com> writes:
> Gregory Heytings <gregory@heytings.org> writes:
>
>> It's indeed exaggerated, AFAIU. Basically, it's an effect of the
>> c-fontify-new-found-type function, which was added to CC Mode in Oct
>> 2021 because of this thread:
>
> It's not exaggerated at all. After 20 minutes to an hour of work, C
> Mode must be turned on and off again.
And just to demonstrate the severe nature of the problem, within _five_
minutes of working on a file, `fprintf' turns into a type:
[-- Attachment #2: Screenshot from 2023-01-11 09-45-24.png --]
[-- Type: image/png, Size: 34450 bytes --]
next prev parent reply other threads:[~2023-01-11 1:46 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 [this message]
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
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=87v8ldg7w8.fsf@yahoo.com \
--to=luangruo@yahoo.com \
--cc=acm@muc.de \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=gregory@heytings.org \
/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).