nvim-treesitter/queries/v, branch master[no description]http://git.sudomsg.com/mirror/nvim-treesitter/atom/queries/v?h=master2024-06-28T03:33:06Zfix(v): anchor comment highlight query2024-06-28T03:33:06ZTuriiya34311583+ttytm@users.noreply.github.com2024-06-28T03:33:06Zurn:sha1:cf7baac35aa5c103b960bcb3f15c690a4aa5c6f1
* fix(v): use `source_file` as parent node for comment highlight query
* fix: correctly recognize doc commentfeat(v): add shebang query2024-06-26T08:54:01ZTuriiya34311583+ttytm@users.noreply.github.com2024-06-26T07:52:56Zurn:sha1:53b32a6aa3e1de224e82f88cbdc08584c753adb7feat: more `@keyword.type` captures2024-05-01T07:59:50ZRiley Bruinsribru17@hotmail.com2024-04-23T19:23:15Zurn:sha1:f58cae6c228e26681039253cb172de16cd764408bot(lockfile): update beancount, liquid, ocaml, ocaml_interface, v, vento, wing2024-03-30T11:16:35Znvim-treesitter-bot[bot]157957100+nvim-treesitter-bot[bot]@users.noreply.github.com2024-03-30T06:35:04Zurn:sha1:5127a844073d56df9ee4e64ccfc17ecc294e38b5refactor(format): drop extra indentation for field2024-03-21T14:51:26ZPhạm Huy Hoànghoangtun0810@gmail.com2024-03-21T11:44:35Zurn:sha1:722617e6726c1508adadf83d531f54987c703be0feat(highlights)!: `@keyword.storage` → `@keyword.modifier`2024-03-16T12:51:16ZJaehwang Jungtomtomjhj@gmail.com2024-03-16T05:23:57Zurn:sha1:dccf31f9b1fbbbd09e6720c7d8f5f1a2433fd32dfeat(highlights)!: keyword `@type.qualifier` → `@keyword.modifier`2024-03-16T12:51:16ZJaehwang Jungtomtomjhj@gmail.com2024-03-08T10:09:51Zurn:sha1:998b230a77b544761bae8aa7518d40b91a5c9559feat(format-scripts): linewrap predicates2024-02-23T08:42:01Z再生花hoangtun0810@gmail.com2024-02-23T08:42:01Zurn:sha1:31641d72a4c33536e9d5fc8f829d2ba84211af8a
"format-ignore".kick()chore: format queries2024-01-21T14:55:02ZPhạm Huy Hoànghoangtun0810@gmail.com2024-01-21T13:05:44Zurn:sha1:77e298e4de607d69aa7f37dc6dcba6aee131ac7fFixup format (#5934)2024-01-20T09:47:56ZPhạm Huy Hoànghoangtun0810@gmail.com2024-01-20T09:47:56Zurn:sha1:d198a75e2c2e24885b05650515538d055d0c64e4
* fix(format): newline between top-level field defs
* fixup: newline between node and comment
* fixup: optimize patternchore: query formatting2024-01-19T15:58:37ZPham Huy Hoanghoangtun0810@gmail.com2024-01-06T06:05:50Zurn:sha1:57a8acf0c4ed5e7f6dda83c3f9b073f8a99a70f9feat!: align standard captures with upstream2024-01-19T15:58:37ZChristian Clasonc.clason@uni-graz.at2023-12-24T09:00:20Zurn:sha1:1ae9b0e4558fe7868f8cda2db65239cfb14836d0
Problem: Sharing highlight queries with upstream tree-sitter and
Helix is difficult.
Solution: Where reasonable, use capture names in tree-sitter's standard
list or Helix's Atom-style hierarchy.
Specifically:
* tree-sitter "standard capture names"
(https://github.com/tree-sitter/tree-sitter/blob/3f44b896852eb7daaa6df4fb778c9bb52c70c815/highlight/src/lib.rs#L20-L72):
- `@parameter` -> `@variable.parameter`
- `@field` -> `@variable.member`
- `@namespace` -> `@module`
- `@float` -> `@number.float`
- `@symbol` -> `@string.special.symbol`
- `@string.regex` -> `@string.regexp`
- `@text.*` -> `@markup.*` (`strong`, `italic`, `link`, `strikethrough`; with exceptions; see below)
- `@text.title` -> `@markup.heading`
- `@text.literal` -> `@markup.raw`
- `@text.reference` -> `@markup.link`
- `@text.uri` -> `@markup.link.url` (in markup links)
- `@string.special` -> `@markup.link.label` (non-url links)
- `@punctuation.special` -> `@markup.list` (markdown lists only; move subitems from `@text.todo`)
* Helix captures
(https://docs.helix-editor.com/master/themes.html#syntax-highlighting):
- `@method` -> `@function.method`
- `@method.call` -> `@function.method.call`
- `@text.{todo,warning,note,danger}` -> `@comment.{error,warning,hint,info,todo}`
- `@text.diff.{add,delete,}` -> `@diff.{plus,minus,delta}`
- `@text.uri` -> `@string.special.url` (outside markup)
- `@preproc` -> `@keyword.directive`
- `@define` -> `@keyword.directive`(`.define`?)
- `@storageclass` -> `@keyword.storage`
- `@conditional` -> `@keyword.conditional`
- `@debug` -> `@keyword.debug`
- `@exception` -> `@keyword.exception`
- `@include` -> `@keyword.import`
- `@repeat` -> `@keyword.repeat`
* cleanup
- remove some redundant `@conceal` (but still allow it for conceal-only patterns)
- remove obsolete `@error` (syntax linting is out of scope for this repo)
- sort, cleanup capture list in `CONTRIBUTING.md`
feat(locals)!: switch to upstream captures2024-01-19T15:58:37ZChristian Clasonc.clason@uni-graz.at2023-07-22T13:29:32Zurn:sha1:5b90ea2abaa4303b9205b5c9002a8cdd0acd11a5fix(v): adapt to removed scanner.c2023-12-15T09:24:32ZChristian Clasonc.clason@uni-graz.at2023-12-15T09:00:18Zurn:sha1:9bc1f1e6406933e9263456e5761e47b9cb1da71drefactor: Remove all `(ERROR) @error` captures2023-10-25T16:18:50ZPham Huy Hoanghoangtun0810@gmail.com2023-10-25T07:45:14Zurn:sha1:107e61afb7129d637ea6c3c68b97a22194b0bf16
As discussed in PR#5421, capturing `@error` is inconsistent, requiring
deep nesting (or priority) in order to correctly have red backgrounds to
it.
Some queries has this capture, some don't. For consistency purposes,
removing all of them is more preferable.
For re-enabling error, either add `(ERROR) @error` or `(ERROR _ @error)`
to your custom queries.
chore(injections)!: update injection syntax to 0.92023-08-12T15:34:15ZPham Huy Hoanghoangtun0810@gmail.com2023-05-03T10:07:59Zurn:sha1:78b54eb7f6a9956d25a3911fa0dfd0cabfe2a4c5
Since 0.9, @lang syntax is still available as fallback but will soon be deprecated.
Because of that, new syntax should be adopted once 0.9 becomes the
baseline requirements for nvim-treesitter
- update health check
- update doc
refactor(v)!: update upstream repository2023-07-04T09:08:07ZAmaan Qureshiamaanq12@gmail.com2023-07-04T08:12:21Zurn:sha1:46b1ad3de2942dcf05f18d124b25fb6ee691c5bfperf: remove match where possible2023-04-21T22:24:17ZAmaan Qureshiamaanq12@gmail.com2023-04-21T08:06:20Zurn:sha1:85330918f05b3a4bd342a69063e7ef5fcdfadd2euse indent.X syntax for captures and properties of set directives2023-03-24T17:07:53ZGeorge Harkergeorge@george-graphics.co.uk2023-03-20T21:44:39Zurn:sha1:cb568af5393241e5dbc9c19157c5df5e9ca9af2d
update CONTRIBUTING.md
adjust indents for bass
fix doc capture comment
feat: add `@comment.documentation` where applicable2023-03-05T22:15:32ZAmaan Qureshiamaanq12@gmail.com2023-03-02T13:06:35Zurn:sha1:5a87bc98dabd0d38152a6fa774005f7ecbd40f1bv(injections): inject regex for some methods in `re` module2023-03-03T20:14:58ZYochem van Rosmalenyochem+git@icloud.com2023-03-03T17:55:49Zurn:sha1:190561df8995ff9526c06d33cf17416b9e0791e3docs: fix typos2023-02-23T19:39:43Zdundargocgocdundar@gmail.com2023-02-23T19:30:36Zurn:sha1:4612212c72a3fe683cbca2f99977ad63b942f70eSplit func/method definition from calls in several programming language queries2022-08-03T19:05:30Zlfenzolfenzo@protonmail.com2022-07-30T00:09:58Zurn:sha1:c784720917bacb6716ce35ef07d464f5da738dd7highlights(vlang): add `attribute_declaration` and specialize some keywords2022-05-21T11:48:58ZStephan Seitzstephan.seitz@fau.de2022-02-26T12:54:19Zurn:sha1:4da1d0702aa33ff5a8da6590bbb362e645c76a5ffeat: highlight string_interpolation identifiers2022-05-21T11:48:58Ztami5kkharji@protonmail.com2022-02-23T13:53:43Zurn:sha1:ad77a80813fcdbfd880df3a363c2f5ab41d76146
functions call work without issues
chore: add more builtin variables2022-05-21T11:48:58Ztami5kkharji@protonmail.com2022-02-23T13:02:50Zurn:sha1:d039b4d0a4459245d78356c9739814fda9826427chore: add $else keyword2022-05-21T11:48:58Ztami5kkharji@protonmail.com2022-02-23T12:58:01Zurn:sha1:b34aadbcb3036502f3aafdb590f0199acad3d301chore(vlang): rename set! > #set!2022-05-21T11:48:58Ztami5kkharji@protonmail.com2022-02-23T02:54:34Zurn:sha1:08092ecc06bc5d4e127285451c1ced5825ea18bcparser(vlang): fix location of remote repo2022-05-21T11:48:58ZStephan Seitzstephan.seitz@fau.de2022-02-22T17:48:05Zurn:sha1:c19d14f39593ff9bc028db6db35f9fc60966543bfeat(vlang): initial support2022-05-21T11:48:58Ztami5kkharji@protonmail.com2022-02-22T14:36:44Zurn:sha1:010f3642956099806f25793f92ba58f1a3114c17
Add support for vlang filetypes.
- [ ] Highlight `C` as builtin variable. This is FFI in vlang land,
where C act like extern and access c functions. The vlang parser does
some extension between C function calls and arguments but I believe
highlighting C as builtin variable is sufficient indicator for now. I
tried to use offset! but failed. Any suggestions?
- [ ] Set up parser url. the vlang parser is located within [vls] repo. Is
installing from nested repo supported? `tree_sitter_v/src/parser.c`?
[vls]: https://github.com/vlang/vls/tree/master/tree_sitter_v
cc @elianiva @theHamsta