From: Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: casouri@gmail.com, 59468@debbugs.gnu.org
Subject: bug#59468: 29.0.50; c-ts-mode cannot fontify after macros are encountered
Date: Thu, 24 Nov 2022 18:36:06 +0800 [thread overview]
Message-ID: <8735a81vxl.fsf@yahoo.com> (raw)
In-Reply-To: <8335a8yajq.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 24 Nov 2022 11:19:21 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
>> Cc: 59468@debbugs.gnu.org
>> Date: Thu, 24 Nov 2022 08:36:13 +0800
>> From: Po Lu via "Bug reports for GNU Emacs,
>> the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
>>
>> >> #ifdef FRAME_DEBUG
>> >> uint_fast64_t last_frame_ms = output->last_frame_time / 1000;
>> >> fprintf (stderr,
>> >> "Drawing the last frame took: %"PRIuFAST64" ms (%"PRIuFAST64")\n",
>> >> last_frame_ms, time);
>> >> #endif
>> >>
>> >> "PRIuFAST64" is fontified in the error face.
>>
>> > Is this valid C? If it it, we should report to tree-sitter-c. If not, we
>> > can add a heuristic.
>>
>> This is valid C. PRIuFAST64 is a standard macro containing the format
>> specifier for a uint_fast64_t.
>>
>> > It fontifies fine here. I guess it’s fixes by some changes I made,
>> > although I don’t recall making changes related to if statements.
>>
>> Maybe you scrolled up the file instead of down? That sometimes matters.
>
> I don't see an error, either. I did scroll from above.
Try going to the end and scrolling up using M-v. That makes the
error(s) show up for me.
next prev parent reply other threads:[~2022-11-24 10:36 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87k03n4v0r.fsf.ref@yahoo.com>
2022-11-22 1:50 ` bug#59468: 29.0.50; c-ts-mode cannot fontify after macros are encountered Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-11-22 20:11 ` Yuan Fu
2022-11-23 0:41 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-11-23 3:30 ` Eli Zaretskii
2022-11-23 4:13 ` Yuan Fu
2022-11-23 7:36 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-11-23 12:53 ` Eli Zaretskii
2022-11-23 12:43 ` Eli Zaretskii
2022-11-23 1:27 ` Yuan Fu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-11-24 0:03 ` Yuan Fu
2022-11-24 0:36 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-11-24 9:19 ` Eli Zaretskii
2022-11-24 10:36 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2022-11-24 10:55 ` Eli Zaretskii
2022-11-24 12:12 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-11-26 2:39 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8735a81vxl.fsf@yahoo.com \
--to=bug-gnu-emacs@gnu.org \
--cc=59468@debbugs.gnu.org \
--cc=casouri@gmail.com \
--cc=eliz@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.