From: vinurs <hi@vinurs.me>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 73310@debbugs.gnu.org, casouri@gmail.com
Subject: bug#73310: tree-sitter makes cpu 100%
Date: Sun, 10 Nov 2024 19:35:53 +0800 [thread overview]
Message-ID: <etPan.67309a9e.50881797.3d1c@vinurs.me> (raw)
In-Reply-To: <86bjynl43x.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 724 bytes --]
Because I saw Yuan’s response in the tree-sitter issue thread stating that this bug had already been fixed, so I'm not sure if it’s the same issue anymore.https://github.com/tree-sitter/tree-sitter/issues/3620 ------------Sincerely,Haiyuan Zhang, VinursBinaryBrain LLC 开 2024年11月10日 在 19:28:55, Eli Zaretskii (eliz@gnu.org) 写到: > Date: Sun, 10 Nov 2024 19:22:24 +0800
> From: vinurs <hi@vinurs.me>
> Cc: 73310@debbugs.gnu.org, Eli Zaretskii <eliz@gnu.org>
>
> The release of tree-sitter version 0.24.4 is out, and I tested it; this issue still persists.
If you are saying that the fix they installed in tree-sitter didn't
solve the problem, why not take this up with the tree-sitter
developers?
[-- Attachment #2: Type: text/html, Size: 1674 bytes --]
next prev parent reply other threads:[~2024-11-10 11:35 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-17 1:27 bug#73310: tree-sitter makes cpu 100% vinurs
2024-09-17 12:29 ` Eli Zaretskii
2024-09-19 12:53 ` vinurs
2024-09-20 6:50 ` Yuan Fu
2024-11-10 11:22 ` vinurs
2024-11-10 11:28 ` Eli Zaretskii
2024-11-10 11:35 ` vinurs [this message]
2024-11-25 1:48 ` Yuan Fu
2024-11-25 11:21 ` vinurs
2024-12-07 12:22 ` Eli Zaretskii
2024-12-11 7:04 ` Yuan Fu
2024-12-11 7:44 ` vinurs
2024-12-11 8:10 ` vinurs
2024-12-12 4:52 ` Yuan Fu
2024-12-18 15:22 ` vinurs
2024-12-19 18:33 ` Yuan Fu
2024-12-19 21:34 ` vinurs
2024-12-20 8:25 ` Yuan Fu
2024-12-20 8:37 ` Eli Zaretskii
2024-12-20 9:14 ` Yuan Fu
2024-12-20 12:15 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=etPan.67309a9e.50881797.3d1c@vinurs.me \
--to=hi@vinurs.me \
--cc=73310@debbugs.gnu.org \
--cc=casouri@gmail.com \
--cc=eliz@gnu.org \
/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.