14 commits

Author	SHA1	Message	Date
Phạm Huy Hoàng	722617e672	refactor(format): drop extra indentation for field	2024-03-21 15:51:26 +01:00
Jaehwang Jung	998b230a77	feat(highlights)!: keyword @type.qualifier → @keyword.modifier	2024-03-16 20:51:16 +08:00
Pham Huy Hoang	57a8acf0c4	chore: query formatting	2024-01-19 16:58:37 +01:00
Christian Clason	1ae9b0e455	feat!: align standard captures with upstream ... 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" (3f44b89685/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`	2024-01-19 16:58:37 +01:00
Pham Huy Hoang	107e61afb7	refactor: Remove all (ERROR) @error captures ... 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-25 18:18:50 +02:00
Amaan Qureshi	5a87bc98da	feat: add @comment.documentation where applicable	2023-03-05 17:15:32 -05:00
Amaan Qureshi	33ba346e60	feat!: add @keyword.coroutine capture	2023-03-03 07:07:52 -08:00
Stephan Seitz	d6a2ecb8b7	highlights: create subscoping for ternary operator ... 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.	2022-12-02 21:42:11 +01:00
ObserverOfTime	6725bef5ce	highlights(hack): fix captures	2022-11-26 13:17:51 +02:00
Stephan Seitz	d11d35fb61	highlights(hack): use @function.call/@method.call	2022-09-11 04:16:06 -07:00
Stephan Seitz	1031bb4769	highlights(hack): fix typo in "tuple" keyword ... https://github.com/slackhq/tree-sitter-hack/pull/34	2022-04-06 22:30:44 +02:00
Stephan Seitz	6a61461d18	highlights(hack): add keywords implements	2022-01-17 10:53:35 +01:00
Stephan Seitz	cc0bdabe5f	highlights(hack): extend queries add tests	2022-01-17 10:53:35 +01:00
Stephan Seitz	d53de75cfd	highlights(hack): add some basic highlights ... Fixes #2041	2022-01-17 10:53:35 +01:00