nvim-treesitter/queries/hack, branch fix/lua[no description]http://git.sudomsg.com/mirror/nvim-treesitter/atom/queries/hack?h=fix%2Flua2025-05-12T16:43:40Zfeat!: drop modules, general refactor and cleanup2025-05-12T16:43:40ZChristian Clasonc.clason@uni-graz.at2023-06-12T15:54:30Zurn:sha1:692b051b09935653befdb8f7ba8afdb640adf17bfeat: more comment injections2024-06-15T08:40:34ZRiley Bruinsribru17@hotmail.com2024-06-08T04:33:49Zurn:sha1:9d68e876cce94fc9f8f8819da0c956a4429a3766feat: more `@keyword.type` captures2024-05-01T07:59:50ZRiley Bruinsribru17@hotmail.com2024-04-23T19:23:15Zurn:sha1:f58cae6c228e26681039253cb172de16cd764408refactor(format): drop extra indentation for field2024-03-21T14:51:26ZPhạm Huy Hoànghoangtun0810@gmail.com2024-03-21T11:44:35Zurn:sha1:722617e6726c1508adadf83d531f54987c703be0feat(highlights)!: keyword `@type.qualifier` → `@keyword.modifier`2024-03-16T12:51:16ZJaehwang Jungtomtomjhj@gmail.com2024-03-08T10:09:51Zurn:sha1:998b230a77b544761bae8aa7518d40b91a5c9559chore: 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`
refactor: 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.
feat: add `@comment.documentation` where applicable2023-03-05T22:15:32ZAmaan Qureshiamaanq12@gmail.com2023-03-02T13:06:35Zurn:sha1:5a87bc98dabd0d38152a6fa774005f7ecbd40f1bfeat!: add `@keyword.coroutine` capture2023-03-03T15:07:52ZAmaan Qureshiamaanq12@gmail.com2023-02-24T11:37:45Zurn:sha1:33ba346e60c3151fcdafc55d0e547556dc803c03highlights: create subscoping for ternary operator2022-12-02T20:42:11ZStephan Seitzstephan.seitz@fau.de2022-12-02T19:22:58Zurn:sha1:d6a2ecb8b7093d6f6673cb6748bce9214a5099d3
After https://github.com/nvim-treesitter/nvim-treesitter/issues/470,
we decided to use `@conditional` for ternary operator instead of
operator despite `@conditional` is documented for keywords only.
A sub-scoping can make it easier for people to highlight this operator
group differently.
Also unify the usage of `@conditional...` across languages.
highlights(hack): fix captures2022-11-26T11:17:51ZObserverOfTimechronobserver@disroot.org2022-11-20T13:14:25Zurn:sha1:6725bef5ce43d62852d43e7eb01082f7721cd728highlights(hack): use `@function.call`/`@method.call`2022-09-11T11:16:06ZStephan Seitzstephan.seitz@fau.de2022-08-29T21:46:40Zurn:sha1:d11d35fb614cb58033b29de7b33832ae48d3e666highlights(hack): fix typo in "tuple" keyword2022-04-06T20:30:44ZStephan Seitzstephan.seitz@fau.de2022-04-06T20:15:12Zurn:sha1:1031bb47694f41f50fb4f06dce1820e75147c725
https://github.com/slackhq/tree-sitter-hack/pull/34
highlights(hack): add keywords implements2022-01-17T09:53:35ZStephan Seitzstephan.seitz@fau.de2021-11-28T14:12:08Zurn:sha1:6a61461d18039de7ebc8fd51f2b6ec0d4e562431highlights(hack): extend queries add tests2022-01-17T09:53:35ZStephan Seitzstephan.seitz@fau.de2021-11-23T17:23:57Zurn:sha1:cc0bdabe5f9a9705bf2992831dd45e95d116fe0chighlights(hack): add some basic highlights2022-01-17T09:53:35ZStephan Seitzstephan.seitz@fau.de2021-11-23T00:20:25Zurn:sha1:d53de75cfd40e12af8ec14e3d1c05dfa8daf8721
Fixes #2041