nvim-treesitter/queries/bitbake, branch fix/lua[no description]http://git.sudomsg.com/mirror/nvim-treesitter/atom/queries/bitbake?h=fix%2Flua2025-05-12T16:43:40Zfeat!: drop modules, general refactor and cleanup2025-05-12T16:43:40ZChristian Clasonc.clason@uni-graz.at2023-06-12T15:54:30Zurn:sha1:692b051b09935653befdb8f7ba8afdb640adf17bfix(bitbake): remove unused rule2024-10-16T06:35:54ZAmaan Qureshiamaanq12@gmail.com2024-10-15T16:04:49Zurn:sha1:c729bb2487a4cf87e60416b0c75d580efa6d086crefactor(format): drop extra indentation for field2024-03-21T14:51:26ZPhạm Huy Hoànghoangtun0810@gmail.com2024-03-21T11:44:35Zurn:sha1:722617e6726c1508adadf83d531f54987c703be0feat(highlights)!: `@keyword.storage` → `@keyword.modifier`2024-03-16T12:51:16ZJaehwang Jungtomtomjhj@gmail.com2024-03-16T05:23:57Zurn:sha1:dccf31f9b1fbbbd09e6720c7d8f5f1a2433fd32dfeat(highlights)!: keyword `@type.qualifier` → `@keyword.modifier`2024-03-16T12:51:16ZJaehwang Jungtomtomjhj@gmail.com2024-03-08T10:09:51Zurn:sha1:998b230a77b544761bae8aa7518d40b91a5c9559feat(format-scripts): linewrap predicates2024-02-23T08:42:01Z再生花hoangtun0810@gmail.com2024-02-23T08:42:01Zurn:sha1:31641d72a4c33536e9d5fc8f829d2ba84211af8a
"format-ignore".kick()chore: format queries2024-01-21T14:55:02ZPhạm Huy Hoànghoangtun0810@gmail.com2024-01-21T13:05:44Zurn:sha1:77e298e4de607d69aa7f37dc6dcba6aee131ac7ffix(highlights): improve consistency2024-01-19T15:58:37ZObserverOfTimechronobserver@disroot.org2024-01-09T09:50:31Zurn:sha1:2f38c36294fde19a901b17589b153898b8a075e5chore: query formatting2024-01-19T15:58:37ZPham Huy Hoanghoangtun0810@gmail.com2024-01-06T06:05:50Zurn:sha1:57a8acf0c4ed5e7f6dda83c3f9b073f8a99a70f9refactor: manual pre-cleanup2024-01-19T15:58:37ZPham Huy Hoanghoangtun0810@gmail.com2024-01-04T18:19:54Zurn:sha1:edee83272efe9b597bc27e8060539cdffa3b12a8
Moving comments, adding `format-ignore` to lines that will be better
with it
feat!: align standard captures with upstream2024-01-19T15:58:37ZChristian Clasonc.clason@uni-graz.at2023-12-24T09:00:20Zurn: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`
feat(locals)!: switch to upstream captures2024-01-19T15:58:37ZChristian Clasonc.clason@uni-graz.at2023-07-22T13:29:32Zurn:sha1:5b90ea2abaa4303b9205b5c9002a8cdd0acd11a5chore(bitbake): update highlights from upstream2023-11-08T07:08:17ZAmaan Qureshiamaanq12@gmail.com2023-11-08T03:51:33Zurn:sha1:eacb5e9468665d842d2d25e857cad8f6d95c57fdrefactor: Remove all `(ERROR) @error` captures2023-10-25T16:18:50ZPham Huy Hoanghoangtun0810@gmail.com2023-10-25T07:45:14Zurn:sha1:107e61afb7129d637ea6c3c68b97a22194b0bf16
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: add BitBake2023-08-17T15:14:32ZAmaan Qureshiamaanq12@gmail.com2023-08-17T04:49:36Zurn:sha1:977e9327268196ace4d7839c6d44feb7978952c4