Open rbjorklin opened 11 months ago
I can't seem to reproduce this, bash tree-sitter works fine for me using latest plugin and parser
One time, after I updated nvim
, nvim always prompt out the same errors as yours. I spent some time to fix it and found out that I have to remove the whole plugin
directory and make treesitter
re-run the whole install process, which finally makes the problem gone.
It seems like there are some dependency problem among nvim
, treesitter
or vim-matchup
. However, I'm not sure which one makes the root cause. The only thing I know is that vim-matchup
is the only one plugin in my list that would prompt out these messages after I did some changes on nvim
or treesitter
(yes, I met these errors several times)
So, assume you didn't meet this problem before and you did some update recently. Maybe you could try to clean the whole nvim
configuration including the download repositories inside the treesitter
@andymass Today I started getting a similar issue with typescript:
I got the same issue for javascript/typescript since today.
I could pinpoint the issue to this treesitter commit: https://github.com/nvim-treesitter/nvim-treesitter/commit/6da205148fb43eb4fa70888fd6ac46a32f1fc3f2
The commit before works fine, while 6da2051 introduces the error
Hi @chrisgrieser, there is a patch here (#338). You can apply it locally before the PR is merged.
Explain the issue
This seems very similar to #334.
EDIT: Setting
disable = { "bash" }
makes the error go away. EDIT2: Nvm, looks like disablingbash
only reduced the frequency. RunningTSUninstall bash
actually makes the problem go away but also disables TreeSitter forbash
. EDIT3: That also didn't help. Reverted to the last known good commit:6c8909b682803d8c3a054259079f158a73a0e30f