[no description] http://git.sudomsg.com/mirror/nvim-treesitter/atom/queries/comment?h=main 2025-05-12T16:43:40Z 2025-05-12T16:43:40Z Christian Clason c.clason@uni-graz.at 2023-06-12T15:54:30Z urn:sha1:692b051b09935653befdb8f7ba8afdb640adf17b 2024-03-03T15:03:26Z Christian Clason c.clason@uni-graz.at 2024-03-03T14:50:48Z urn:sha1:3d08cdd741ea02ab820406582f8ea0b1198e368d 2024-01-21T14:55:02Z Phạm Huy Hoàng hoangtun0810@gmail.com 2024-01-21T13:05:44Z urn:sha1:77e298e4de607d69aa7f37dc6dcba6aee131ac7f 2024-01-20T16:52:50Z Christian Clason c.clason@uni-graz.at 2024-01-20T16:41:40Z urn:sha1:5cc562748729b6dc9563ea5a3d676ff102ab38b1 Distinguishing `hint` and `info` is too confusing; it's enough to have `error`, `warning`, `todo`, and `note`. 2024-01-19T15:58:37Z Pham Huy Hoang hoangtun0810@gmail.com 2024-01-06T06:05:50Z urn:sha1:57a8acf0c4ed5e7f6dda83c3f9b073f8a99a70f9 2024-01-19T15:58:37Z Christian Clason c.clason@uni-graz.at 2023-12-24T09:00:20Z urn:sha1:1ae9b0e4558fe7868f8cda2db65239cfb14836d0 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-09-12T15:34:58Z Jaehwang Jung tomtomjhj@gmail.com 2023-09-12T14:46:39Z urn:sha1:905e782e803e200ec43b0b31fee37164cb2249a0 Problem: Comment highlight query produces too many @spell captures. Solution: Remove the query. This is fine because comment parser is only used in injection and the parent language has @spell for comment. 2023-07-25T13:03:54Z pseudometa 73286100+chrisgrieser@users.noreply.github.com 2023-07-25T13:03:54Z urn:sha1:74a7da4e4be5ee71e9efb6d7bdffa16ad620cc57 2023-06-16T19:21:40Z Santos Gallegos stsewd@proton.me 2023-06-16T19:11:10Z urn:sha1:1b9f704eb8664508749a1164d4086e47f9afa77f 2023-06-09T08:14:08Z pseudometa 73286100+chrisgrieser@users.noreply.github.com 2023-06-09T08:14:08Z urn:sha1:e040eda9976533fa5dfa5e473079dcc7b0d95bbf see also: https://github.com/stsewd/tree-sitter-comment/issues/22 2023-06-04T04:03:09Z Santos Gallegos stsewd@proton.me 2023-06-04T04:03:09Z urn:sha1:48f4f3ead16e59d886f2109dd796773c37dd713e https and https links are recognized now ref https://github.com/stsewd/tree-sitter-comment/pull/21 2023-05-10T15:53:57Z ObserverOfTime chronobserver@disroot.org 2023-05-10T15:46:07Z urn:sha1:f9cfd40c08e1a505e728271a57960c387a9bf8f5 2023-03-20T08:47:56Z ObserverOfTime chronobserver@disroot.org 2023-03-20T08:40:10Z urn:sha1:25b656a4b771ee7d440e506280b9ae546d6f7233 2023-03-01T20:22:10Z Yochem van Rosmalen yochem+git@icloud.com 2023-03-01T13:26:52Z urn:sha1:252c1011c4bae91d25a8c54be4ed1a7b341c088c 2023-02-13T08:43:26Z Santos Gallegos stsewd@proton.me 2023-02-13T08:43:26Z urn:sha1:1ec36fdcd567ee97e77fbaec29c3f8145d51e72c 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 2022-11-26T11:17:51Z ObserverOfTime chronobserver@disroot.org 2022-10-17T17:09:56Z urn:sha1:53c26dd4af08d0a8cb59d8deb34049bf4761d707 2022-09-26T12:47:12Z Lewis Russell lewis6991@gmail.com 2022-09-26T09:19:02Z urn:sha1:37398c7d68826c8d6ae3f85cc52d83fd3dee4f84 2022-09-23T17:52:00Z Erik Westrup erik.westrup@gmail.com 2022-09-23T17:52:00Z urn:sha1:26105050aae3a15dd85feaeb0439e253e31d5ceb 2021-11-23T09:02:06Z Lewis Russell lewis6991@gmail.com 2021-11-18T09:51:03Z urn:sha1:011ac894ec5b9e36563d8629fb7734f43ddb27a8 as string.find is much quicker than vim.regex:match* 2021-06-26T10:19:08Z Jaehwang Jerry Jung tomtomjhj@gmail.com 2021-06-26T06:08:49Z urn:sha1:c04aa172a3feab61f8f4fbfa0e3d47fa12513485 2021-06-24T22:22:48Z Joakker joaquinandresleon108@gmail.com 2021-06-24T18:45:31Z urn:sha1:c699cc2e47fe302e9f414356cceb20a309be5bc6 2021-04-03T08:48:09Z Santos Gallegos stsewd@protonmail.com 2021-04-02T16:58:45Z urn:sha1:4bfccba843d4fb2da96996dd827cd03dd9e546fa As requested in https://github.com/nvim-treesitter/nvim-treesitter/issues/236#issuecomment-797878646 2021-03-12T16:21:46Z Santos Gallegos stsewd@protonmail.com 2021-03-12T16:21:46Z urn:sha1:e4083fc8e11e6585f53d62eb71778cc2af464fad Closes #236