12 commits

Author	SHA1	Message	Date
Riley Bruins	f58cae6c22	feat: more @keyword.type captures	2024-05-01 09:59:50 +02:00
Phạm Huy Hoàng	722617e672	refactor(format): drop extra indentation for field	2024-03-21 15:51:26 +01:00
再生花	31641d72a4	feat(format-scripts): linewrap predicates ... "format-ignore".kick()	2024-02-23 10:42:01 +02:00
Amaan Qureshi	8e1df60b13	chore(puppet): update queries	2024-02-18 10:10:55 -05:00
ObserverOfTime	fa38f4e6f9	fix(highlights): improve member/property distinction	2024-01-19 16:58:37 +01:00
Pham Huy Hoang	57a8acf0c4	chore: query formatting	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
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
Pham Huy Hoang	78b54eb7f6	chore(injections)!: update injection syntax to 0.9 ... Since 0.9, @lang syntax is still available as fallback but will soon be deprecated. Because of that, new syntax should be adopted once 0.9 becomes the baseline requirements for nvim-treesitter - update health check - update doc	2023-08-12 17:34:15 +02:00
Amaan Qureshi	48df8efa25	chore(puppet): update queries from upstream	2023-07-24 23:38:46 -04:00
Amaan Qureshi	fe3afeaa73	feat: add puppet	2023-04-26 19:29:01 -04:00