nvim-treesitter/queries/comment/highlights.scm

(_) @spell

((tag
  (name) @text.todo @nospell
  ("(" @punctuation.bracket (user) @constant ")" @punctuation.bracket)?
  ":" @punctuation.delimiter)
  (#eq? @text.todo "TODO"))

("text" @text.todo @nospell
 (#eq? @text.todo "TODO"))

((tag
  (name) @text.note @nospell
  ("(" @punctuation.bracket (user) @constant ")" @punctuation.bracket)?
  ":" @punctuation.delimiter)
  (#any-of? @text.note "NOTE" "XXX"))

("text" @text.note @nospell
 (#any-of? @text.note "NOTE" "XXX"))

((tag
  (name) @text.warning @nospell
  ("(" @punctuation.bracket (user) @constant ")" @punctuation.bracket)?
  ":" @punctuation.delimiter)
  (#any-of? @text.warning "HACK" "WARNING"))

("text" @text.warning @nospell
 (#any-of? @text.warning "HACK" "WARNING"))

((tag
  (name) @text.danger @nospell
  ("(" @punctuation.bracket (user) @constant ")" @punctuation.bracket)?
  ":" @punctuation.delimiter)
  (#any-of? @text.danger "FIXME" "BUG"))

("text" @text.danger @nospell
 (#any-of? @text.danger "FIXME" "BUG"))

; Issue number (#123)
("text" @number
 (#lua-match? @number "^#[0-9]+$"))
feat(spell): support more languages 2022-09-26 10:19:02 +01:00			`(_) @spell`

comment(highlights): reduce false positives (#4298) There are a couple cases where the comment highlights will match things that aren't necessary a tag. For example in Rust, when commenting a block that deals with generics (generics are declared as `T: Type`), this may be distracting. So, instead of highlighting all tags, we can restrict to highlighting the explicit keywords. Ref https://github.com/stsewd/tree-sitter-comment/issues/14 2023-02-13 03:43:26 -05:00			`((tag`
comment(highlights): add `@nospell` to tags and user mentions 2023-03-01 14:26:52 +01:00			`(name) @text.todo @nospell`
comment(highlights): reduce false positives (#4298) There are a couple cases where the comment highlights will match things that aren't necessary a tag. For example in Rust, when commenting a block that deals with generics (generics are declared as `T: Type`), this may be distracting. So, instead of highlighting all tags, we can restrict to highlighting the explicit keywords. Ref https://github.com/stsewd/tree-sitter-comment/issues/14 2023-02-13 03:43:26 -05:00			`("(" @punctuation.bracket (user) @constant ")" @punctuation.bracket)?`
			`":" @punctuation.delimiter)`
			`(#eq? @text.todo "TODO"))`
highlights(comment): improve note tags 2022-10-17 20:09:56 +03:00
comment(highlights): add `@nospell` to tags and user mentions 2023-03-01 14:26:52 +01:00			`("text" @text.todo @nospell`
highlights(comment): improve note tags 2022-10-17 20:09:56 +03:00			`(#eq? @text.todo "TODO"))`
Add comment parser to highlight comment tags (#893) Closes #236 2021-03-12 11:21:46 -05:00
comment(highlights): reduce false positives (#4298) There are a couple cases where the comment highlights will match things that aren't necessary a tag. For example in Rust, when commenting a block that deals with generics (generics are declared as `T: Type`), this may be distracting. So, instead of highlighting all tags, we can restrict to highlighting the explicit keywords. Ref https://github.com/stsewd/tree-sitter-comment/issues/14 2023-02-13 03:43:26 -05:00			`((tag`
comment(highlights): add `@nospell` to tags and user mentions 2023-03-01 14:26:52 +01:00			`(name) @text.note @nospell`
comment(highlights): reduce false positives (#4298) There are a couple cases where the comment highlights will match things that aren't necessary a tag. For example in Rust, when commenting a block that deals with generics (generics are declared as `T: Type`), this may be distracting. So, instead of highlighting all tags, we can restrict to highlighting the explicit keywords. Ref https://github.com/stsewd/tree-sitter-comment/issues/14 2023-02-13 03:43:26 -05:00			`("(" @punctuation.bracket (user) @constant ")" @punctuation.bracket)?`
			`":" @punctuation.delimiter)`
			`(#any-of? @text.note "NOTE" "XXX"))`
feat(comment): highlight `NOTE` as `@text.note` (#3537) 2022-09-23 19:52:00 +02:00
comment(highlights): add `@nospell` to tags and user mentions 2023-03-01 14:26:52 +01:00			`("text" @text.note @nospell`
highlights(comment): improve note tags 2022-10-17 20:09:56 +03:00			`(#any-of? @text.note "NOTE" "XXX"))`
feat(comment): highlight `NOTE` as `@text.note` (#3537) 2022-09-23 19:52:00 +02:00
comment(highlights): reduce false positives (#4298) There are a couple cases where the comment highlights will match things that aren't necessary a tag. For example in Rust, when commenting a block that deals with generics (generics are declared as `T: Type`), this may be distracting. So, instead of highlighting all tags, we can restrict to highlighting the explicit keywords. Ref https://github.com/stsewd/tree-sitter-comment/issues/14 2023-02-13 03:43:26 -05:00			`((tag`
comment(highlights): add `@nospell` to tags and user mentions 2023-03-01 14:26:52 +01:00			`(name) @text.warning @nospell`
comment(highlights): reduce false positives (#4298) There are a couple cases where the comment highlights will match things that aren't necessary a tag. For example in Rust, when commenting a block that deals with generics (generics are declared as `T: Type`), this may be distracting. So, instead of highlighting all tags, we can restrict to highlighting the explicit keywords. Ref https://github.com/stsewd/tree-sitter-comment/issues/14 2023-02-13 03:43:26 -05:00			`("(" @punctuation.bracket (user) @constant ")" @punctuation.bracket)?`
			`":" @punctuation.delimiter)`
			`(#any-of? @text.warning "HACK" "WARNING"))`
Add comment parser to highlight comment tags (#893) Closes #236 2021-03-12 11:21:46 -05:00
comment(highlights): add `@nospell` to tags and user mentions 2023-03-01 14:26:52 +01:00			`("text" @text.warning @nospell`
highlights(comment): improve note tags 2022-10-17 20:09:56 +03:00			`(#any-of? @text.warning "HACK" "WARNING"))`
Comment: highlight text nodes As requested in https://github.com/nvim-treesitter/nvim-treesitter/issues/236#issuecomment-797878646 2021-04-02 11:58:45 -05:00
comment(highlights): reduce false positives (#4298) There are a couple cases where the comment highlights will match things that aren't necessary a tag. For example in Rust, when commenting a block that deals with generics (generics are declared as `T: Type`), this may be distracting. So, instead of highlighting all tags, we can restrict to highlighting the explicit keywords. Ref https://github.com/stsewd/tree-sitter-comment/issues/14 2023-02-13 03:43:26 -05:00			`((tag`
comment(highlights): add `@nospell` to tags and user mentions 2023-03-01 14:26:52 +01:00			`(name) @text.danger @nospell`
comment(highlights): reduce false positives (#4298) There are a couple cases where the comment highlights will match things that aren't necessary a tag. For example in Rust, when commenting a block that deals with generics (generics are declared as `T: Type`), this may be distracting. So, instead of highlighting all tags, we can restrict to highlighting the explicit keywords. Ref https://github.com/stsewd/tree-sitter-comment/issues/14 2023-02-13 03:43:26 -05:00			`("(" @punctuation.bracket (user) @constant ")" @punctuation.bracket)?`
			`":" @punctuation.delimiter)`
			`(#any-of? @text.danger "FIXME" "BUG"))`
Add comment parser to highlight comment tags (#893) Closes #236 2021-03-12 11:21:46 -05:00
comment(highlights): add `@nospell` to tags and user mentions 2023-03-01 14:26:52 +01:00			`("text" @text.danger @nospell`
highlights(comment): improve note tags 2022-10-17 20:09:56 +03:00			`(#any-of? @text.danger "FIXME" "BUG"))`
Comment: highlight text nodes As requested in https://github.com/nvim-treesitter/nvim-treesitter/issues/236#issuecomment-797878646 2021-04-02 11:58:45 -05:00
Add comment parser to highlight comment tags (#893) Closes #236 2021-03-12 11:21:46 -05:00			`; Issue number (#123)`
highlights(comment): improve note tags 2022-10-17 20:09:56 +03:00			`("text" @number`
			`(#lua-match? @number "^#[0-9]+$"))`