13 commits

Author	SHA1	Message	Date
Omar Valdez	51bba660a8	refactor(queries): Remove quotes from properties in set! directive	2024-07-28 11:43:41 +02:00
Riley Bruins	9d68e876cc	feat: more comment injections	2024-06-15 10:40:34 +02:00
Phạm Huy Hoàng	722617e672	refactor(format): drop extra indentation for field	2024-03-21 15:51:26 +01:00
Christian Clason	99ddf57353	feat(highlights)!: enforce documented captures (#6232) ... Problem: Allowing undocumented "secret" (sub)captures makes it harder to write comprehensive colorschemes and catch inconsistent captures. Solution: Only allow captures listed in CONTRIBUTING.md. Add useful (cross-language) subcaptures and drop language-specific or too niche ones. Follow-up: Adding further `*.builtin` captures and changing queries to use them. Language-specific subcaptures should instead be added in user config or a custom language plugin.	2024-03-03 11:00:11 +01: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
Christian Clason	5b90ea2aba	feat(locals)!: switch to upstream captures	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
Jaehwang Jung	9567185621	feat: @spell on comments	2023-09-12 17:34:58 +02:00
Jeroen Op 't Eynde	4d41d9bfb0	feat(jsonnet): update parser and queries	2023-08-25 13:55:22 -04:00
Cezary Drożak	4ffdc4c985	feat: update jsonnet queries	2023-08-17 21:46:33 -04:00
Hoang Nguyen	71bb1da621	feat(jsonnet): add "for" & "function", update operator highlights ... `expr` -> `operator` doesn't exist in the node tree anymore after 505f5bd900	2023-06-08 10:13:26 -04:00
Cezary Drożak	f2d3d509d9	feat: add jsonnet	2022-09-10 11:09:10 -07:00