Riley Bruins bd4ca22d03 feat(treesitter)!: don't parse tree in get_parser() or start() ...

**Problem:** `vim.treesitter.get_parser()` and `vim.treesitter.start()`
both parse the tree before returning it. This is problematic because if
this is a sync parse, it will stall the editor on large files. If it is
an async parse, the functions return stale trees.

**Solution:** Remove this parsing side effect and leave it to the user
to parse the returned trees, either synchronously or asynchronously.

2025-01-12 08:10:49 -08:00

..

_meta

feat(treesitter): introduce child_with_descendant()

2024-10-11 17:29:45 +02:00

_fold.lua

refactor(treesitter.foldexpr): remove unused parse_injections parameter

2025-01-10 22:06:35 +00:00

_query_linter.lua

fix(treesitter): remove duplicate symbol names in language.inspect()

2024-10-11 18:15:07 +02:00

_range.lua

docs(treesitter): generate inline docs for Ranges

2024-08-06 18:18:34 +02:00

dev.lua

fix(treesitter): keep treeview open if source window is still open #31198

2024-11-14 19:00:18 -08:00

health.lua

fix(health): better layout of vim.treesitter health check

2024-11-02 23:51:00 +01:00

highlighter.lua

feat(treesitter)!: don't parse tree in get_parser() or start()

2025-01-12 08:10:49 -08:00

language.lua

fix(treesitter): don't return error message on success #31955

2025-01-10 14:46:19 -08:00

languagetree.lua

feat(treesitter): async parsing

2025-01-12 08:10:47 -08:00

query.lua

feat(treesitter): async parsing

2025-01-12 08:10:47 -08:00