From: Yuan Fu <casouri@gmail.com>
To: "Mattias Engdegård" <mattiase@acm.org>
Cc: Po Lu <luangruo@yahoo.com>,
59426@debbugs.gnu.org, Eli Zaretskii <eliz@gnu.org>,
Stefan Kangas <stefankangas@gmail.com>
Subject: bug#59426: 29.0.50; [tree-sitter] Some functions exceed maximum recursion limit
Date: Mon, 21 Nov 2022 09:01:45 -0800 [thread overview]
Message-ID: <E4A36FB0-989F-47DB-9433-5A7940258DEC@gmail.com> (raw)
In-Reply-To: <3A46E3F3-08BD-40C2-9B68-0EAF03295E1C@acm.org>
> On Nov 21, 2022, at 8:54 AM, Eli Zaretskii <eliz@gnu.org> wrote:
>
>> From: Yuan Fu <casouri@gmail.com>
>> Date: Mon, 21 Nov 2022 08:43:45 -0800
>> Cc: Eli Zaretskii <eliz@gnu.org>,
>> Stefan Kangas <stefankangas@gmail.com>,
>> Po Lu <luangruo@yahoo.com>,
>> 59426@debbugs.gnu.org
>>
>>> There are still scores of Elisp byte-compilation warnings but I leave fixing those to the tree-sitter developers.
>>
>> Could you paste the warnings? Because I don’t see any warnings on my machine.
>
> I' see them and am working on fixing them. (You won't see them unless you
> configure --without-tree-sitter.)
Thanks!
> On Nov 21, 2022, at 8:56 AM, Mattias Engdegård <mattiase@acm.org> wrote:
>
> 21 nov. 2022 kl. 17.43 skrev Yuan Fu <casouri@gmail.com>:
>
>>> There are still scores of Elisp byte-compilation warnings but I leave fixing those to the tree-sitter developers.
>>
>> Could you paste the warnings? Because I don’t see any warnings on my machine.
>
> Build without tree-sitter and you should see them for several .el files, as well as when byte-compiling treesit-tests.el .
> (I could paste the warnings but you need to reproduce them yourself in order to fix them anyway.)
>
Ah, I see. I’ll let Eli do the hard work for me :-)
Yuan
next prev parent reply other threads:[~2022-11-21 17:01 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-21 0:53 bug#59426: 29.0.50; [tree-sitter] Some functions exceed maximum recursion limit Yuan Fu
2022-11-21 6:40 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-11-21 7:38 ` Stefan Kangas
2022-11-21 12:00 ` Mattias Engdegård
2022-11-21 13:55 ` Eli Zaretskii
2022-11-21 14:46 ` Mattias Engdegård
2022-11-21 16:43 ` Yuan Fu
2022-11-21 16:54 ` Eli Zaretskii
2022-11-21 17:10 ` Eli Zaretskii
2022-11-21 17:45 ` Eli Zaretskii
2022-11-21 18:20 ` Mattias Engdegård
2022-11-21 18:26 ` Eli Zaretskii
2022-11-21 18:59 ` Mattias Engdegård
2022-11-21 19:00 ` Yuan Fu
2022-11-22 9:08 ` Mattias Engdegård
2022-11-22 23:19 ` Yuan Fu
2022-11-23 10:40 ` Mattias Engdegård
2022-11-23 18:46 ` Yuan Fu
2022-11-23 20:01 ` Mattias Engdegård
2022-11-24 9:17 ` Yuan Fu
2022-11-24 10:24 ` Mattias Engdegård
2022-11-24 19:25 ` Yuan Fu
2022-11-24 19:28 ` Eli Zaretskii
2022-11-27 2:36 ` Yuan Fu
2022-11-24 10:24 ` Eli Zaretskii
2022-11-21 16:56 ` Mattias Engdegård
2022-11-21 17:01 ` Yuan Fu [this message]
2022-11-21 17:44 ` Eli Zaretskii
2022-11-22 1:46 ` Stefan Kangas
2022-11-22 0:27 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-11-22 8:59 ` Mattias Engdegård
2022-11-21 13:19 ` Eli Zaretskii
2022-11-21 16:52 ` Yuan Fu
2022-11-21 17:16 ` Eli Zaretskii
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=E4A36FB0-989F-47DB-9433-5A7940258DEC@gmail.com \
--to=casouri@gmail.com \
--cc=59426@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=luangruo@yahoo.com \
--cc=mattiase@acm.org \
--cc=stefankangas@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).