14 commits

Author	SHA1	Message	Date
Omar Valdez	df111f886c	feat(rasi): Highlight captures similar to CSS (#6507)	2024-04-25 12:05:06 +02: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
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
George Harker	cb568af539	use indent.X syntax for captures and properties of set directives ... update CONTRIBUTING.md adjust indents for bass fix doc capture comment	2023-03-24 13:07:53 -04:00
ObserverOfTime	7294e534d2	highlights(rasi): fix captures	2022-11-26 13:17:51 +02:00
Fymyte	69aeed8495	fix(locals): fix local selectors query ... Signed-off-by: Fymyte <pierguill@gmail.com>	2022-01-06 22:02:02 +01:00
Fymyte	234ec41653	add(indent): add ignore indent for comments ... Signed-off-by: Fymyte <pierguill@gmail.com>	2022-01-06 22:02:02 +01:00
Fymyte	4ebaa35c0b	fix(indent): fix indent queries ... Signed-off-by: Fymyte <pierguill@gmail.com>	2022-01-06 22:02:02 +01:00
Fymyte	171adc391b	add(query): fold, indent and locals queries for rasi ... Signed-off-by: Fymyte <pierguill@gmail.com>	2022-01-06 22:02:02 +01:00
Fymyte	d13c045223	add(rasi): add rasi parser ... Signed-off-by: Fymyte <pierguill@gmail.com>	2022-01-05 01:01:12 +01:00