]f, mif and the other textobject keys use helix's own queries

helix's textobjects.scm for pardes's grammars are vendored in vendor/queries
under MPL-2.0, each with a header naming its source and what it inherits,
inlined; a README says what is there and what is not. syntax.objectAt and
objectNext run them over the file's kept parse, with their #eq? and #match?
predicates, for ]f [f ]t [t ]a [a ]c [c ]T [T ]e [e ]x [x and mi/ma with
f t a c T e x. erlang's and zig's queries do not compile against the grammar
versions pardes builds and are left out; fortran, markdown and powershell
have none in helix. A test replays sixteen Python and JSON cases whose
results were taken from the installed hx, and another holds that every
vendored query compiles.

Co-Authored-By: Claude Opus 5.5 <[email protected]>

1 files changed, 15 insertions, 0 deletions

diff --git a/vendor/queries/README.md b/vendor/queries/README.md
new file mode 100644
index 00000000..abd37d00
--- /dev/null
+++ b/vendor/queries/README.md
@@ -0,0 +1,15 @@
+# Textobject queries
+
+`<grammar>/textobjects.scm` is helix's own query for that grammar, vendored
+from helix (https://github.com/helix-editor/helix) at 278b24389, the
+reference build docs/helix-keys.md names. Each file says where it came from
+and what it inherits, inlined. They are Mozilla Public License 2.0, whose text
+is `helix.LICENSE` here. They give `]f`, `[f`, `mif` and the other
+tree-sitter textobject keys what a function, class, argument, comment, test,
+entry or element is.
+
+Not vendored: fortran, markdown and powershell (helix has no query for
+them), and erlang and zig, whose helix queries do not compile against the
+grammar versions pardes builds (a node name either side has renamed). Those
+grammars have no textobjects, and the keys do nothing there, as in helix
+without a query.