<feed xmlns='http://www.w3.org/2005/Atom'>
<title>nvim-treesitter/tests/query/highlights/fusion, branch main</title>
<subtitle>[no description]</subtitle>
<id>http://git.sudomsg.com/mirror/nvim-treesitter/atom/tests/query/highlights/fusion?h=main</id>
<link rel='self' href='http://git.sudomsg.com/mirror/nvim-treesitter/atom/tests/query/highlights/fusion?h=main'/>
<link rel='alternate' type='text/html' href='http://git.sudomsg.com/mirror/nvim-treesitter/'/>
<updated>2025-12-06T17:10:39Z</updated>
<entry>
<title>feat(parsers)!: remove gitlab-hosted blueprint, fusion, jsonc</title>
<updated>2025-12-06T17:10:39Z</updated>
<author>
<name>Christian Clason</name>
<email>c.clason@uni-graz.at</email>
</author>
<published>2025-12-05T08:59:04Z</published>
<link rel='alternate' type='text/html' href='http://git.sudomsg.com/mirror/nvim-treesitter/commit/?id=d2350758b39dce3593ffa8b058f863ea4cfa5b0e'/>
<id>urn:sha1:d2350758b39dce3593ffa8b058f863ea4cfa5b0e</id>
<content type='text'>
Problem: Gitlab has too frequent outages, which break automation.

Solution: Drop all Gitlab-hosted parsers (two of which have been
unmaintained for years).
</content>
</entry>
<entry>
<title>feat: more `@keyword.type` captures</title>
<updated>2024-05-01T07:59:50Z</updated>
<author>
<name>Riley Bruins</name>
<email>ribru17@hotmail.com</email>
</author>
<published>2024-04-23T19:23:15Z</published>
<link rel='alternate' type='text/html' href='http://git.sudomsg.com/mirror/nvim-treesitter/commit/?id=f58cae6c228e26681039253cb172de16cd764408'/>
<id>urn:sha1:f58cae6c228e26681039253cb172de16cd764408</id>
<content type='text'>
</content>
</entry>
<entry>
<title>feat!: align standard captures with upstream</title>
<updated>2024-01-19T15:58:37Z</updated>
<author>
<name>Christian Clason</name>
<email>c.clason@uni-graz.at</email>
</author>
<published>2023-12-24T09:00:20Z</published>
<link rel='alternate' type='text/html' href='http://git.sudomsg.com/mirror/nvim-treesitter/commit/?id=1ae9b0e4558fe7868f8cda2db65239cfb14836d0'/>
<id>urn:sha1:1ae9b0e4558fe7868f8cda2db65239cfb14836d0</id>
<content type='text'>
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` -&gt; `@variable.parameter`
  - `@field` -&gt; `@variable.member`
  - `@namespace` -&gt; `@module`
  - `@float` -&gt; `@number.float`
  - `@symbol` -&gt; `@string.special.symbol`
  - `@string.regex` -&gt; `@string.regexp`
  - `@text.*` -&gt; `@markup.*` (`strong`, `italic`, `link`, `strikethrough`; with exceptions; see below)
  - `@text.title` -&gt; `@markup.heading`
  - `@text.literal` -&gt; `@markup.raw`
  - `@text.reference` -&gt; `@markup.link`
  - `@text.uri` -&gt; `@markup.link.url` (in markup links)
  - `@string.special` -&gt; `@markup.link.label` (non-url links)
  - `@punctuation.special` -&gt; `@markup.list` (markdown lists only; move subitems from `@text.todo`)

* Helix captures
  (https://docs.helix-editor.com/master/themes.html#syntax-highlighting):

  - `@method` -&gt; `@function.method`
  - `@method.call` -&gt; `@function.method.call`
  - `@text.{todo,warning,note,danger}` -&gt; `@comment.{error,warning,hint,info,todo}`
  - `@text.diff.{add,delete,}` -&gt; `@diff.{plus,minus,delta}`
  - `@text.uri` -&gt; `@string.special.url` (outside markup)
  - `@preproc` -&gt; `@keyword.directive`
  - `@define` -&gt; `@keyword.directive`(`.define`?)
  - `@storageclass` -&gt; `@keyword.storage`
  - `@conditional` -&gt; `@keyword.conditional`
  - `@debug` -&gt; `@keyword.debug`
  - `@exception` -&gt; `@keyword.exception`
  - `@include` -&gt; `@keyword.import`
  - `@repeat` -&gt; `@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`
</content>
</entry>
<entry>
<title>chore(tests): consistent captures</title>
<updated>2024-01-19T15:58:37Z</updated>
<author>
<name>Christian Clason</name>
<email>c.clason@uni-graz.at</email>
</author>
<published>2023-12-24T11:52:21Z</published>
<link rel='alternate' type='text/html' href='http://git.sudomsg.com/mirror/nvim-treesitter/commit/?id=10dd49958c96f86c8247c715bd20a6681afc1d8b'/>
<id>urn:sha1:10dd49958c96f86c8247c715bd20a6681afc1d8b</id>
<content type='text'>
</content>
</entry>
<entry>
<title>highlights: create subscoping for ternary operator</title>
<updated>2022-12-02T20:42:11Z</updated>
<author>
<name>Stephan Seitz</name>
<email>stephan.seitz@fau.de</email>
</author>
<published>2022-12-02T19:22:58Z</published>
<link rel='alternate' type='text/html' href='http://git.sudomsg.com/mirror/nvim-treesitter/commit/?id=d6a2ecb8b7093d6f6673cb6748bce9214a5099d3'/>
<id>urn:sha1:d6a2ecb8b7093d6f6673cb6748bce9214a5099d3</id>
<content type='text'>
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.
</content>
</entry>
<entry>
<title>update fusion to version 1.1.1 (#2148)</title>
<updated>2021-12-23T16:18:15Z</updated>
<author>
<name>jirgn</name>
<email>jirgnmssnr@googlemail.com</email>
</author>
<published>2021-12-23T16:18:15Z</published>
<link rel='alternate' type='text/html' href='http://git.sudomsg.com/mirror/nvim-treesitter/commit/?id=6b5b37cc3ee2468beef1289980102fc3c4e06e2c'/>
<id>urn:sha1:6b5b37cc3ee2468beef1289980102fc3c4e06e2c</id>
<content type='text'>
* feat(fusion): update tests

* fix(fusion): update lockfile

* fix(fusion): update to (highlight breaking) version 1.1.0

* update grammer to introduce afx support
* update tests and queries

* fix: revert lockfile update of unrelated grammars

* fix: update to 1.1.1 and fix hightlights

* fix: use @tag.attribute capture to match specs

Co-authored-by: Jirgn &lt;jirgn76@googlemail.com&gt;</content>
</entry>
<entry>
<title>feat(fusion): update tests</title>
<updated>2021-12-06T20:51:53Z</updated>
<author>
<name>Jirgn</name>
<email>jirgn76@googlemail.com</email>
</author>
<published>2021-12-05T22:26:59Z</published>
<link rel='alternate' type='text/html' href='http://git.sudomsg.com/mirror/nvim-treesitter/commit/?id=f51aa0b75ebc09e811fb775932635e80bfc8d343'/>
<id>urn:sha1:f51aa0b75ebc09e811fb775932635e80bfc8d343</id>
<content type='text'>
</content>
</entry>
<entry>
<title>fix: incorrect hightlight groups</title>
<updated>2021-11-26T21:04:59Z</updated>
<author>
<name>Jirgn</name>
<email>jirgn76@googlemail.com</email>
</author>
<published>2021-11-26T20:22:28Z</published>
<link rel='alternate' type='text/html' href='http://git.sudomsg.com/mirror/nvim-treesitter/commit/?id=096f0e91be337252bf3d1e9569528e3c844a6220'/>
<id>urn:sha1:096f0e91be337252bf3d1e9569528e3c844a6220</id>
<content type='text'>
</content>
</entry>
<entry>
<title>fix: typo in highlight group punct(u)ation</title>
<updated>2021-11-26T21:04:59Z</updated>
<author>
<name>Jirgn</name>
<email>jirgn76@googlemail.com</email>
</author>
<published>2021-11-26T19:08:16Z</published>
<link rel='alternate' type='text/html' href='http://git.sudomsg.com/mirror/nvim-treesitter/commit/?id=a0ad73493ea557089d8bb05a73349d760e5f3911'/>
<id>urn:sha1:a0ad73493ea557089d8bb05a73349d760e5f3911</id>
<content type='text'>
</content>
</entry>
<entry>
<title>feat: add fusion grammar and highlights</title>
<updated>2021-11-26T21:04:59Z</updated>
<author>
<name>Jirgn</name>
<email>jirgn76@googlemail.com</email>
</author>
<published>2021-11-26T15:37:51Z</published>
<link rel='alternate' type='text/html' href='http://git.sudomsg.com/mirror/nvim-treesitter/commit/?id=979c32493d1edabb949badf00da9d130d966aaae'/>
<id>urn:sha1:979c32493d1edabb949badf00da9d130d966aaae</id>
<content type='text'>
</content>
</entry>
</feed>
