[no description] http://git.sudomsg.com/mirror/nvim-treesitter/atom?h=feat%2Fstable 2025-05-29T18:08:10Z 2025-05-29T18:08:10Z Christian Clason c.clason@uni-graz.at 2025-05-29T10:25:13Z urn:sha1:ff770d718b34db10e33d18594153b4d1e0954882 Problem: People complain about noisy `install()`. Solution: Gate operation summary behind `summary` install option (default false, set to true for interactive `:TS*` commands). 2025-05-29T10:11:56Z Christian Clason c.clason@uni-graz.at 2025-05-29T10:04:37Z urn:sha1:ce903fde5d36d7955d34faaf0b812a186417e746 2025-05-29T09:52:58Z Christian Clason c.clason@uni-graz.at 2025-05-28T11:55:33Z urn:sha1:0860b9b1070c4e1bcce66416844b633acd8e0d2a Problem: Can't uninstall custom parsers without queries since `installed_parsers` only iterates over installed queries (to include query-only languages, and to avoid string manipulation). Solution: Iterate over both queries and parsers to collect list of installed languages (optionally only queries or only parsers). 2025-05-12T16:43:40Z Christian Clason c.clason@uni-graz.at 2024-04-14T14:25:28Z urn:sha1:c17de5689045f75c6244462182ae3b4b62df02d9 Problem: Tracking parser revision in lockfile and allowing override through the parsers module complicates the code. In addition, only revision changes are handled robustly, not changes to other installation info. Solution: Track parser revision in the parsers module directly. Reload parser table on every install or update call. Support modifying parser table in a `User TSUpdate` autocommand. 2025-05-12T16:43:40Z Christian Clason c.clason@uni-graz.at 2024-04-18T07:44:38Z urn:sha1:5a38df5627fd0658223bdf32c9d6a87e32eb9504 Problem: Many parsers require node/npm to evaluate the `grammar.js` before being able to generate a parser from it. Solution: Generate from `grammar.json` instead, which is fully resolved. Drops `node` and `npm` as (optional) requirements for nvim-treesitter. Note that this requires parsers to commit the generated json iff the grammar requires evaluation (which is currently the case for all tracked languages). 2025-05-12T16:43:40Z Lewis Russell lewis6991@gmail.com 2024-04-19T17:12:54Z urn:sha1:0bb981c87604200df6c8fb81e5a411101bdf93af 2025-05-12T16:43:40Z Christian Clason c.clason@uni-graz.at 2023-06-06T09:02:28Z urn:sha1:5a70048116f8fb7489aa68e347d9dfe57dc39498 also fixes the hole in install.compilers 2025-05-12T16:43:40Z Lewis Russell lewis6991@gmail.com 2023-05-22T13:35:25Z urn:sha1:cde679e435ade757733772236abf299fc06da231 Replace sync variants with callback support 2025-05-12T16:43:40Z Christian Clason c.clason@uni-graz.at 2023-06-12T15:54:30Z urn:sha1:692b051b09935653befdb8f7ba8afdb640adf17b 2022-10-16T13:50:55Z Christian Clason c.clason@uni-graz.at 2022-10-16T12:52:15Z urn:sha1:42ab95d5e11f247c6f0c8f5181b02e816caa4a4f 2022-07-30T18:13:24Z John Drouhard john@drouhard.dev 2022-07-29T14:24:41Z urn:sha1:635c450939e19c02538d6700e9b7f828db31e4eb If the plugin is loaded after a colorscheme is set that defines any of these highlight groups, the default won't be applied. Subsequent "highlight clear" commands (common when switching colorschemes) will then clear any of those highlights, but these defaults never have another opportunity to be initialized. Effectively, if you load neovim with a colorscheme that has definitions for some of these highlight groups, then load treesitter, then switch colorschemes, many of these default links will be absent resulting in colors that do not appear the same as if that colorscheme had been used at startup. Hooking the ColorScheme event with an autocmd that just reapplies these defaults gives every colorscheme switch the opportunity to get the defaults for non-explicitly-defined groups. 2022-04-30T14:08:01Z Christian Clason c.clason@uni-graz.at 2022-04-16T15:49:17Z urn:sha1:07eb437bb1c4c0a0298553dd509294f82362d6bc * set highlight groups via nvim_set_hl * define autocommands via nvim_create_autocmd * port plugin/nvim-treesitter.vim to Lua * port healthcheck to Lua