From: Alan Mackenzie <acm@muc.de>
To: Jeff Norden <norden.jeff@gmail.com>
Cc: acm@muc.de, Eli Zaretskii <eliz@gnu.org>, 64133@debbugs.gnu.org
Subject: bug#64133: CC Mode 5.35.2 (C/*l); incorrect indentation for an arrays of structs.
Date: Mon, 19 Jun 2023 11:46:32 +0000 [thread overview]
Message-ID: <ZJBAGKznW-MPHVKZ@ACM> (raw)
In-Reply-To: <CAPbFCn=p0q5NbPO0XQjtmZJTbYiJY03R=Xajb62bjQb_nYHBpQ@mail.gmail.com>
Hello, Jeff.
On Sun, Jun 18, 2023 at 12:23:58 -0500, Jeff Norden wrote:
> The only reason the minibuffer-read affects things is timing. This
> seems obvious now, but somehow it didn't occur to me until after I
> sent the previous message. If I do
> <tab><backspace><backspace> ..wait a few seconds.. <tab>
> then the syntax does *not* change to brace-list. I tried changing
> c-progress-interval, but that didn't seem to affect things. Maybe
> there is another timer, or maybe a race condition involved somehow.
No, I think it really is the cache bug I mentioned in my last post.
Caches are wonderful things when they work properly, but the utter devil
to debug when they don't.
I've currently got a CC Mode version with this cache corrected, such
that it parses your test file correctly, but I want to make sure the
correction is correct before I send you a patch and release the fix.
I'll be back again soon.
> Hope this helps,
> -Jeff
--
Alan Mackenzie (Nuremberg, Germany).
next prev parent reply other threads:[~2023-06-19 11:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-17 15:03 bug#64133: CC Mode 5.35.2 (C/*l); incorrect indentation for an arrays of structs Jeff Norden
2023-06-17 15:14 ` Eli Zaretskii
[not found] ` <CAPbFCnniiTyPQBmayZpRwS46--JW6ipmmLAzMterB5cK9NEXCA@mail.gmail.com>
2023-06-17 16:27 ` Eli Zaretskii
2023-06-17 17:36 ` Jeff Norden
2023-06-18 13:13 ` Alan Mackenzie
2023-06-18 16:10 ` Jeff Norden
2023-06-18 17:23 ` Jeff Norden
2023-06-19 11:46 ` Alan Mackenzie [this message]
2023-06-19 14:30 ` Jeff Norden
2023-06-21 10:39 ` Alan Mackenzie
2023-06-21 18:43 ` Jeff Norden
2023-06-27 20:19 ` 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=ZJBAGKznW-MPHVKZ@ACM \
--to=acm@muc.de \
--cc=64133@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=norden.jeff@gmail.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).