dotemacs/docs/python-treesit-predicate-mismatch.txt, branch load-graph-classify-startMy Emacs configuration
https://git.cjennings.net/dotemacs/atom?h=load-graph-classify-start2026-05-14T12:33:17+00:00chore(todo): close Python tree-sitter predicate bug as upstream-resolved2026-05-14T12:33:17+00:00Craig Jenningsc@cjennings.net2026-05-14T12:33:17+00:00urn:sha1:dd907fde706f5a9dec0473ff465dff2ee9d9ff6a
The treesit-query-error redisplay flood diagnosed 2026-04-26 no
longer reproduces. Versions: emacs 30.2-3 (was 30.2-2 at the time
of the investigation, upgraded 2026-05-03), tree-sitter 0.26.8
(unchanged). The upstream Emacs version string is unchanged, but
the Arch package revision bump most likely carries a downstream
patch to treesit.c's predicate translation.
Verified by re-running the documented repro: the exact failing query
from python.el captures cleanly via `treesit-query-capture', and
`font-lock-ensure' on a real .py file under `python-ts-mode' returns
with no `treesit-query-error'. No local override needed.
Mark the todo.org entry DONE, fix the stale `inbox/' path on the
investigation-doc link (file now lives under `docs/'), update the
cross-reference from the grammar-bootstrap task to note this no
longer blocks it, and append a RESOLVED 2026-05-14 footer to the
investigation doc so future-me can see why it got closed.
docs: add Python tree-sitter font-lock predicate-mismatch diagnostic2026-05-11T10:17:44+00:00Craig Jenningsc@cjennings.net2026-05-11T10:17:44+00:00urn:sha1:54a2567c58dd3a456219c17c44e89233f7176b0d
Pins down why every Python buffer fires `treesit-query-error` on redisplay: Emacs 30.2 emits `#match` predicates, but tree-sitter 0.26 only accepts `#match?`. The doc has the reproduction, the six fix options with their trade-offs, and the verification path. The next pass picks up at decision-time instead of re-deriving the cause.