14 commits

Author	SHA1	Message	Date
Amaan Qureshi	c729bb2487	fix(bitbake): remove unused rule	2024-10-16 08:35:54 +02:00
Phạm Huy Hoàng	722617e672	refactor(format): drop extra indentation for field	2024-03-21 15:51:26 +01:00
Jaehwang Jung	dccf31f9b1	feat(highlights)!: @keyword.storage → @keyword.modifier	2024-03-16 20:51:16 +08:00
Jaehwang Jung	998b230a77	feat(highlights)!: keyword @type.qualifier → @keyword.modifier	2024-03-16 20:51:16 +08:00
再生花	31641d72a4	feat(format-scripts): linewrap predicates ... "format-ignore".kick()	2024-02-23 10:42:01 +02:00
Phạm Huy Hoàng	77e298e4de	chore: format queries	2024-01-21 23:55:02 +09:00
ObserverOfTime	2f38c36294	fix(highlights): improve consistency	2024-01-19 16:58:37 +01:00
Pham Huy Hoang	57a8acf0c4	chore: query formatting	2024-01-19 16:58:37 +01:00
Pham Huy Hoang	edee83272e	refactor: manual pre-cleanup ... Moving comments, adding `format-ignore` to lines that will be better with it	2024-01-19 16:58:37 +01:00
Christian Clason	1ae9b0e455	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" (3f44b89685/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`	2024-01-19 16:58:37 +01:00
Christian Clason	5b90ea2aba	feat(locals)!: switch to upstream captures	2024-01-19 16:58:37 +01:00
Amaan Qureshi	eacb5e9468	chore(bitbake): update highlights from upstream	2023-11-08 08:08:17 +01:00
Pham Huy Hoang	107e61afb7	refactor: Remove all (ERROR) @error captures ... 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.	2023-10-25 18:18:50 +02:00
Amaan Qureshi	977e932726	feat: add BitBake	2023-08-17 11:14:32 -04:00