<feed xmlns='http://www.w3.org/2005/Atom'>
<title>nvim-treesitter/scripts/convert-lockfile.lua, branch test/plenary</title>
<subtitle>[no description]</subtitle>
<id>http://git.sudomsg.com/mirror/nvim-treesitter/atom/scripts/convert-lockfile.lua?h=test%2Fplenary</id>
<link rel='self' href='http://git.sudomsg.com/mirror/nvim-treesitter/atom/scripts/convert-lockfile.lua?h=test%2Fplenary'/>
<link rel='alternate' type='text/html' href='http://git.sudomsg.com/mirror/nvim-treesitter/'/>
<updated>2025-05-12T16:43:40Z</updated>
<entry>
<title>chore: remove lockfile and update script</title>
<updated>2025-05-12T16:43:40Z</updated>
<author>
<name>Christian Clason</name>
<email>c.clason@uni-graz.at</email>
</author>
<published>2025-04-30T16:11:16Z</published>
<link rel='alternate' type='text/html' href='http://git.sudomsg.com/mirror/nvim-treesitter/commit/?id=44bb06bc123f2c90acbe79035cb19a8e89674d7d'/>
<id>urn:sha1:44bb06bc123f2c90acbe79035cb19a8e89674d7d</id>
<content type='text'>
`main` branch and `parsers.lua` is the record of truth now
</content>
</entry>
<entry>
<title>feat!: use tree-sitter build</title>
<updated>2025-05-12T16:43:40Z</updated>
<author>
<name>Christian Clason</name>
<email>c.clason@uni-graz.at</email>
</author>
<published>2024-04-22T17:56:30Z</published>
<link rel='alternate' type='text/html' href='http://git.sudomsg.com/mirror/nvim-treesitter/commit/?id=214cfcf851d95a4c4f2dc7526b95ce9d31c88a76'/>
<id>urn:sha1:214cfcf851d95a4c4f2dc7526b95ce9d31c88a76</id>
<content type='text'>
</content>
</entry>
<entry>
<title>feat!: track parser revision in Lua</title>
<updated>2025-05-12T16:43:40Z</updated>
<author>
<name>Christian Clason</name>
<email>c.clason@uni-graz.at</email>
</author>
<published>2024-04-14T14:25:28Z</published>
<link rel='alternate' type='text/html' href='http://git.sudomsg.com/mirror/nvim-treesitter/commit/?id=c17de5689045f75c6244462182ae3b4b62df02d9'/>
<id>urn:sha1:c17de5689045f75c6244462182ae3b4b62df02d9</id>
<content type='text'>
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.
</content>
</entry>
</feed>
