16 commits

Author	SHA1	Message	Date
Jaehwang Jung	dccf31f9b1	feat(highlights)!: @keyword.storage → @keyword.modifier	2024-03-16 20:51:16 +08:00
Jaehwang Jung	998b230a77	feat(highlights)!: keyword @type.qualifier → @keyword.modifier	2024-03-16 20:51:16 +08:00
ObserverOfTime	fa38f4e6f9	fix(highlights): improve member/property distinction	2024-01-19 16:58:37 +01:00
ObserverOfTime	2f38c36294	fix(highlights): improve consistency	2024-01-19 16:58:37 +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
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	9f157094cd	feat(smali): update queries from upstream parser	2023-04-25 02:37:31 -04:00
Amaan Qureshi	85330918f0	perf: remove match where possible	2023-04-21 18:24:17 -04:00
Amaan Qureshi	c79c37927b	refactor(smali): refactor queries from upstream	2023-04-17 22:50:34 -04:00
Amaan Qureshi	5a87bc98da	feat: add @comment.documentation where applicable	2023-03-05 17:15:32 -05:00
Amaan Qureshi	8c4a22fd50	feat(smali): improve queries	2023-02-22 14:11:22 +01:00
Amaan Q	5b8b711926	refactor: move method and end_method to @keyword.function	2023-01-09 21:24:54 +01:00
Amaan Q	d13a0d563b	fix: character_literal is no longer unsupported :)	2023-01-09 21:24:54 +01:00
Amaan Qureshi	1735990aa9	feat: add character_literal query ... Co-authored-by: ObserverOfTime <chronobserver@disroot.org>	2023-01-09 21:24:54 +01:00
Amaan Q	e1f2bb2fcf	feat: add smali query	2023-01-09 21:24:54 +01:00