nvim-treesitter/runtime/queries/nickel/highlights.scm

130 lines
1.6 KiB
Scheme
Raw Normal View History

(comment) @comment @spell
(annot_atom
doc: (static_string) @spell)
[
"forall"
"in"
"let"
"default"
"doc"
"rec"
"optional"
"priority"
"force"
"not_exported"
] @keyword
"fun" @keyword.function
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" (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`
2023-12-24 10:00:20 +01:00
"import" @keyword.import
2024-01-06 15:05:50 +09:00
[
"if"
"then"
"else"
] @keyword.conditional
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" (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`
2023-12-24 10:00:20 +01:00
"match" @keyword.conditional
(types) @type
2024-01-06 15:05:50 +09:00
"Array" @type.builtin
; BUILTIN Constants
2022-10-20 20:01:08 +02:00
(bool) @boolean
2024-01-06 15:05:50 +09:00
"null" @constant.builtin
(enum_tag) @constant
(num_literal) @number
[
(infix_op)
"|>"
"="
"&"
"=="
"/"
"!="
"<"
">"
"@"
".."
] @operator
(type_atom) @type
2024-01-06 15:05:50 +09:00
(static_string) @string
(chunk_literal_single) @string
2024-01-06 15:05:50 +09:00
(chunk_literal_multi) @string
(str_esc_char) @string.escape
[
2024-01-06 15:05:50 +09:00
"{"
"}"
"("
")"
"[|"
"|]"
"["
"]"
] @punctuation.bracket
[
","
"."
":"
"|"
"->"
"+"
"-"
"*"
] @punctuation.delimiter
(multstr_start) @string
2024-01-06 15:05:50 +09:00
(multstr_end) @string
2024-01-06 15:05:50 +09:00
(interpolation_start) @punctuation.bracket
2024-01-06 15:05:50 +09:00
(interpolation_end) @punctuation.bracket
(builtin) @function.builtin
2024-01-06 15:05:50 +09:00
(fun_expr
pats: (pattern_fun
(ident) @variable.parameter))
; application where the head terms is an identifier: function arg1 arg2 arg3
2024-01-06 15:05:50 +09:00
(applicative
t1: (applicative
.
(record_operand
(atom
(ident))) @function))
; application where the head terms is a record field path: foo.bar.function arg1 arg2 arg3
(applicative
t1: (applicative
.
(record_operand
(record_operation_chain)) @function))
(str_chunks) @string
(field_path_elem) @property
(infix_expr
op: (infix_b_op_6)
t2: (infix_expr
(applicative
.
(record_operand
(record_operation_chain) @function))))