Closed cowboyd closed 7 months ago
I also ran into this today, and can confirm pinning to v0.20.3
fixed it
I don't think this belongs here, there's no parse errors and we're not going to debug an issue inside emacs. File this with the appropriate emacs repository responsible for tree-sitter integration.
@cowboyd and anyone else finding this later - this is confirmed to be an Emacs bug, and it was fixed in Emacs 29.2, which is already out. I just updated to 29.2 and confirmed the fix worked :)
https://lists.gnu.org/archive/html/bug-gnu-emacs/2023-10/msg01335.html
@ajyoon I am still experiencing this in emacs 29.2
Apart from re-compiling tree-sitter-typescript and upgrading to emacs 29.2, was there anything else you had to do?
I also removed the tree-sitter-typescript version pin from my .emacs, maybe double check that? But otherwise no, that's all I did and it works for me now.
Did you check existing issues?
Tree-Sitter CLI Version, if relevant (output of
tree-sitter --version
)No response
Describe the bug
After upgrading from version
0.20.3
, my typescript buffers in emacs started continually raising the following error:Steps To Reproduce/Bad Parse Tree
v0.20.4
(v0.20.5
andmaster
will also reproduce the bug)hello.ts
file with the following content:(font-lock-fontify-region 1 23)
which is called by the language server mode.Expected Behavior/Parse Tree
for
v0.20.3
and before, this succeeds. Past that point it fails. If this is a bug in eglot or emacs-lsp mode, then happy to report those there.Repro
Apologies for requiring an external tool/IDE. I've spent about 90 minutes trying to track this down to be as reproducible as possible so that I could put it on somebody's radar, but without really understanding it, I'm not sure how to reproduce it without Emacs. It might be problem with emacs, it might be a problem with eglot (the emacs LSP client), or it might be a problem with tree sitter-typescript. The only thing I know that is that it has worked flawlessly up until this point, and that the tree-sitter-typescript version is the only variable I can manipulate to cause it to break.
My current workaround is to pin tree-sitter-typescript to
v0.20.3