Language c no longer working

[reet-]

Hi,

I updated my configuration to revision 9cd4e3b and now get the following exception when opening a (simple) c file:

Error detected while processing CursorMoved Autocommands for "*"..function 3[3]..4[71]..matchup#delim#get_current[1]..<SNR>55_get_delim_multi[3]..matchup#ts_engine#get_delim[3]..<SNR>51_forward:
line    1:                                                                        
E5108: Error executing lua ...tRbn/usr/share/nvim/runtime/lua/vim/treesitter/query.lua:259: query: invalid node type at position 589 for language c
stack traceback:                                                                 
        [C]: in function '_ts_parse_query'                                       
        ...tRbn/usr/share/nvim/runtime/lua/vim/treesitter/query.lua:259: in function 'get_query'
        ...vim-matchup/lua/treesitter-matchup/third-party/query.lua:55: in function 'get_query'
        ...vim-matchup/lua/treesitter-matchup/third-party/query.lua:142: in function 'prepare_query'
        ...vim-matchup/lua/treesitter-matchup/third-party/query.lua:339: in function 'iter_group_results'
        ...vim-matchup/lua/treesitter-matchup/third-party/query.lua:351: in function 'collect_group_results'
        ...vim/lazy/vim-matchup/lua/treesitter-matchup/internal.lua:46: in function 'fn'
        ...r/share/nvim/runtime/lua/vim/treesitter/languagetree.lua:385: in function 'for_each_tree'
        ...vim/lazy/vim-matchup/lua/treesitter-matchup/internal.lua:40: in function 'fn'
        ...im/lazy/nvim-treesitter/lua/nvim-treesitter/ts_utils.lua:380: in function 'get_matches'
        ...vim/lazy/vim-matchup/lua/treesitter-matchup/internal.lua:102: in function 'fn'
        ...im/lazy/nvim-treesitter/lua/nvim-treesitter/ts_utils.lua:380: in function 'get_active_nodes'
        ...vim/lazy/vim-matchup/lua/treesitter-matchup/internal.lua:221: in function 'get_delim'
        [string "luaeval()"]:1: in main chunk

Other languages seem to work fine.

Thanks!

• reto

[reet-]

The problem is gone with latest nightly v0.10.0-dev-766+gef44e5972, closing this issue.