From: Alan Mackenzie <acm@muc.de>
To: Po Lu <luangruo@yahoo.com>
Cc: emacs-devel@gnu.org
Subject: Re: CC Mode troubles and Emacs 29
Date: Mon, 9 Jan 2023 15:52:32 +0000 [thread overview]
Message-ID: <Y7w4QKsgDjo4t+kv@ACM> (raw)
In-Reply-To: <874jt0hw7p.fsf@yahoo.com>
Hello, Po.
On Mon, Jan 09, 2023 at 17:51:38 +0800, Po Lu wrote:
> Alan, all,
> Emacs 29 is supposed to have pretests released in around a month.
> However, CC Mode is still prone to misidentifying typos as types.
Yes. I can see my way to having this fixed in a small number of weeks,
or a large number of days. The bug is understood.
> That is a major regression from the standpoint of users.
Yes, I agree with that.
> So, perhaps it would be prudent to disable automatic type finding on
> the emacs-29 branch, and to keep working on it in the CC Mode
> repository?
No, this wouldn't be a good idea. It would be an appreciable amount of
work, and would leave around 50% of types unfontified. This would very
quickly cause bug reports.
> Thanks.
--
Alan Mackenzie (Nuremberg, Germany).
prev parent reply other threads:[~2023-01-09 15:52 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
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 [this message]
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=Y7w4QKsgDjo4t+kv@ACM \
--to=acm@muc.de \
--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).