aboutsummaryrefslogtreecommitdiffstats
path: root/queries/rasi
Commit message (Collapse)AuthorAgeFilesLines
* feat!: drop modules, general refactor and cleanupChristian Clason2025-05-125-161/+0
|
* feat(rasi): Highlight captures similar to CSS (#6507)Omar Valdez2024-04-252-7/+8
|
* feat(highlights)!: keyword `@type.qualifier` → `@keyword.modifier`Jaehwang Jung2024-03-161-1/+1
|
* chore: query formattingPham Huy Hoang2024-01-194-42/+107
|
* feat!: align standard captures with upstreamChristian Clason2024-01-191-3/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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`
* feat(locals)!: switch to upstream capturesChristian Clason2024-01-191-3/+3
|
* refactor: Remove all `(ERROR) @error` capturesPham Huy Hoang2023-10-251-2/+0
| | | | | | | | | | | | 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.
* feat: @spell on commentsJaehwang Jung2023-09-121-1/+1
|
* use indent.X syntax for captures and properties of set directivesGeorge Harker2023-03-241-3/+3
| | | | | | | | update CONTRIBUTING.md adjust indents for bass fix doc capture comment
* highlights(rasi): fix capturesObserverOfTime2022-11-261-2/+2
|
* fix(locals): fix local selectors queryFymyte2022-01-061-1/+1
| | | | Signed-off-by: Fymyte <pierguill@gmail.com>
* add(indent): add ignore indent for commentsFymyte2022-01-061-0/+2
| | | | Signed-off-by: Fymyte <pierguill@gmail.com>
* fix(indent): fix indent queriesFymyte2022-01-061-1/+3
| | | | Signed-off-by: Fymyte <pierguill@gmail.com>
* add(query): fold, indent and locals queries for rasiFymyte2022-01-063-0/+11
| | | | Signed-off-by: Fymyte <pierguill@gmail.com>
* add(rasi): add rasi parserFymyte2022-01-051-0/+82
Signed-off-by: Fymyte <pierguill@gmail.com>