From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: luangruo@yahoo.com, 63840@debbugs.gnu.org, casouri@gmail.com,
theo@thornhill.no
Subject: bug#63840: 29.0.91; c-ts-mode fails to fontify common C extension
Date: Mon, 02 Oct 2023 08:55:01 +0300 [thread overview]
Message-ID: <835y3p8t6y.fsf@gnu.org> (raw)
In-Reply-To: <CADwFkmnnSmVnNZ_YK6KY3f_V2bzWAPr6Gc4+5ytcajC4Qch1hQ@mail.gmail.com> (message from Stefan Kangas on Sun, 1 Oct 2023 14:10:15 -0700)
> From: Stefan Kangas <stefankangas@gmail.com>
> Date: Sun, 1 Oct 2023 14:10:15 -0700
> Cc: luangruo@yahoo.com, 63840@debbugs.gnu.org, theo@thornhill.no
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> >> From: Yuan Fu <casouri@gmail.com>
> >> Date: Tue, 27 Jun 2023 18:46:24 -0700
> >> Cc: Theodor Thornhill <theo@thornhill.no>,
> >> Po Lu <luangruo@yahoo.com>,
> >> 63840@debbugs.gnu.org
> >>
> >> > Would it be possible for you or someone else of the interested Emacs
> >> > users to submit a patch for the grammar library to support $, either
> >> > as an option or as an extension? IOW, is it hard to modify the
> >> > TS grammar definitions for such relatively simple and straightforward
> >> > extensions?
> >>
> >> There is a PR for it on GitHub (under which I left a comment). Judging from the PR, it’s simple to add support for $.
> >
> > If so, perhaps just pinging about it from time to time is all that
> > should be done.
>
> Does it make sense to keep this bug open on our side if we only intend
> to wait for upstream support? Or should we close it as wontfix?
We could indeed close it.
next prev parent reply other threads:[~2023-10-02 5:55 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87fs7anjwq.fsf.ref@yahoo.com>
2023-06-02 12:11 ` bug#63840: 29.0.91; c-ts-mode fails to fontify common C extension Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-02 12:51 ` Eli Zaretskii
2023-06-08 7:18 ` Yuan Fu
2023-06-08 8:50 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-15 5:56 ` Eli Zaretskii
2023-06-16 5:05 ` Yuan Fu
2023-06-16 6:31 ` Eli Zaretskii
2023-06-19 6:43 ` Yuan Fu
2023-06-19 16:23 ` Eli Zaretskii
2023-06-27 5:54 ` Yuan Fu
2023-06-27 11:05 ` Eli Zaretskii
2023-06-28 1:46 ` Yuan Fu
2023-06-28 2:33 ` Eli Zaretskii
2023-10-01 21:10 ` Stefan Kangas
2023-10-02 5:55 ` Eli Zaretskii [this message]
2023-10-02 6:44 ` Stefan Kangas
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=835y3p8t6y.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=63840@debbugs.gnu.org \
--cc=casouri@gmail.com \
--cc=luangruo@yahoo.com \
--cc=stefankangas@gmail.com \
--cc=theo@thornhill.no \
/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).