From: Stefan Kangas <stefankangas@gmail.com>
To: Yuan Fu <casouri@gmail.com>, Po Lu <luangruo@yahoo.com>
Cc: 59435@debbugs.gnu.org
Subject: bug#59435: 29.0.50; tree-sitter fails to fontify or indent simple function
Date: Mon, 21 Nov 2022 05:52:55 -0800 [thread overview]
Message-ID: <CADwFkmk8K5mY5dHyxWH3NsgEYPgCmas_4svDa-dAUm9SHkgu7A@mail.gmail.com> (raw)
In-Reply-To: <3A4C0323-634D-437D-9510-50E59A254619@gmail.com>
Yuan Fu <casouri@gmail.com> writes:
> And there aren’t much we can do (except for maybe improve
> tree-sitter-c’s parser).
We should report these cases as bugs though, right?
IOW, I'm thinking that, going forward, perhaps in these cases it makes
sense for us to close bugs once there is a corresponding bug reported
against the relevant treesitter grammar.
next prev parent reply other threads:[~2022-11-21 13:52 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <871qpw7s9k.fsf.ref@yahoo.com>
2022-11-21 6:09 ` bug#59435: 29.0.50; tree-sitter fails to fontify or indent simple function Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-11-21 9:45 ` Yuan Fu
2022-11-21 11:57 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-11-21 13:53 ` Eli Zaretskii
2022-11-24 23:38 ` Richard Stallman
2022-11-25 5:12 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-11-28 21:37 ` Richard Stallman
2022-11-29 0:46 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-12-04 23:12 ` Richard Stallman
2022-12-05 1:15 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-11-25 6:38 ` Yuan Fu
2022-11-25 7:45 ` Eli Zaretskii
2022-11-28 21:37 ` Richard Stallman
2022-12-06 21:08 ` Florian Weimer
2022-12-07 1:02 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-12-07 10:50 ` Florian Weimer
2022-12-07 11:01 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-11-21 13:52 ` Stefan Kangas [this message]
2022-11-23 23:31 ` Yuan Fu
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=CADwFkmk8K5mY5dHyxWH3NsgEYPgCmas_4svDa-dAUm9SHkgu7A@mail.gmail.com \
--to=stefankangas@gmail.com \
--cc=59435@debbugs.gnu.org \
--cc=casouri@gmail.com \
--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).