You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 17, 2024. It is now read-only.
After attempting to write my own custom parser i was hit with a rather interesting problem - whenever viewing my syntax tree in TSPlayground, no matter how hard I tried, the tree would not update. The only way to reparse the buffer is to either re-enter neovim or execute :e to force reparsing. After asking around on the Zulip server the source of the problem seems to be highlights - my treesitter parser (can be found here just for reference) does not yet support highlights, and after adding some using :TSEditQuery highlights the automatic reparsing kicked in and started working. Is it possible to reparse on buffer change, rather than on a physical parser update? I believe this would avoid confusion for any new peeps developing parsers for treesitter and Neovim :)
The text was updated successfully, but these errors were encountered:
Hi!
After attempting to write my own custom parser i was hit with a rather interesting problem - whenever viewing my syntax tree in TSPlayground, no matter how hard I tried, the tree would not update. The only way to reparse the buffer is to either re-enter neovim or execute
:e
to force reparsing. After asking around on the Zulip server the source of the problem seems to be highlights - my treesitter parser (can be found here just for reference) does not yet support highlights, and after adding some using:TSEditQuery highlights
the automatic reparsing kicked in and started working. Is it possible to reparse on buffer change, rather than on a physical parser update? I believe this would avoid confusion for any new peeps developing parsers for treesitter and Neovim :)The text was updated successfully, but these errors were encountered: