[no description] http://git.sudomsg.com/mirror/nvim-treesitter/atom/queries/gstlaunch/highlights.scm?h=test%2Finit 2025-05-12T16:43:40Z 2025-05-12T16:43:40Z Christian Clason c.clason@uni-graz.at 2023-06-12T15:54:30Z urn:sha1:692b051b09935653befdb8f7ba8afdb640adf17b 2024-01-19T15:58:37Z Pham Huy Hoang hoangtun0810@gmail.com 2024-01-06T06:05:50Z urn:sha1:57a8acf0c4ed5e7f6dda83c3f9b073f8a99a70f9 2024-01-19T15:58:37Z Christian Clason c.clason@uni-graz.at 2023-12-24T09:00:20Z urn: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` 2023-10-25T16:18:50Z Pham Huy Hoang hoangtun0810@gmail.com 2023-10-25T07:45:14Z urn: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. 2023-10-15T18:38:16Z Stephan Seitz stephan.seitz@fau.de 2023-10-15T18:38:16Z urn:sha1:159272a809c122a0b8ce815acea5265ebb66055b