nvim-treesitter/queries/perl, branch master[no description]http://git.sudomsg.com/mirror/nvim-treesitter/atom/queries/perl?h=master2025-03-19T08:48:48Z* feat(perl): highlight hash keys as `@variable.member` in various contexts2025-03-19T08:48:48ZVeesh Goldmanrabbiveesh@gmail.com2025-03-19T08:48:48Zurn:sha1:f09a2215b8fed4c2e86f2dd1912e14166958c06a
also, injections for s///e should fully re-parse
feat(perl): support more modern syntax2024-09-22T18:15:38ZVeesh Goldmanrabbiveesh@gmail.com2024-09-22T18:15:38Zurn:sha1:20b5cbfa92cac93ab78f3fefeb6169e4ea303189feat(perl): update highlights and folds2024-08-07T13:30:44ZPaul Evansleonerd@leonerd.org.uk2024-08-07T13:30:44Zurn:sha1:3e0feeb062b29bb7d6d6df1e32ba28111c2bb734refactor(queries): Remove quotes from properties in set! directive2024-07-28T09:43:41ZOmar Valdezomarantoniovaldezf2@gmail.com2024-07-27T23:28:19Zurn:sha1:51bba660a89e0027929206b622c9c1cbdd995cfbfeat(perl): deactivate spelling in shebangs2024-05-01T13:01:48ZKai Moschcaukai.moschcau@blecon.de2024-04-29T12:58:23Zurn:sha1:57476501e2bda6f4fcaa481d1b34714bda13bcd7feat(perl): activate spelling in comments2024-05-01T13:01:48ZKai Moschcaukai.moschcau@blecon.de2024-04-29T12:58:01Zurn:sha1:e99b79c9c1dfd88a0919c6d4d502c0fbb76fd02efeat(highlights)!: enforce documented captures (#6232)2024-03-03T10:00:11ZChristian Clasonc.clason@uni-graz.at2024-03-03T10:00:11Zurn:sha1:99ddf573531c4dbe53f743ecbc1595af5eb1d32f
Problem: Allowing undocumented "secret" (sub)captures makes it harder
to write comprehensive colorschemes and catch inconsistent captures.
Solution: Only allow captures listed in CONTRIBUTING.md. Add useful
(cross-language) subcaptures and drop language-specific or too niche
ones.
Follow-up: Adding further `*.builtin` captures and changing queries to
use them.
Language-specific subcaptures should instead be added in user config or
a custom language plugin.
feat(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:77e298e4de607d69aa7f37dc6dcba6aee131ac7ffeat(perl): add more highlights2024-01-21T09:53:32ZVeesh Goldmanrabbiveesh@gmail.com2024-01-20T20:05:29Zurn:sha1:5d5eba78a7eee55df2c18d62cfc81ce9318bddd6chore: query formatting2024-01-19T15:58:37ZPham Huy Hoanghoangtun0810@gmail.com2024-01-06T06:05:50Zurn:sha1:57a8acf0c4ed5e7f6dda83c3f9b073f8a99a70f9feat!: 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`
perl: fix highlights for builtins2023-11-03T12:23:40ZVeesh Goldmanrabbiveesh@gmail.com2023-11-02T19:58:38Zurn:sha1:fca784da0eca70a4ed574d7e763e12c8f757ed7afeat: bump perl2023-10-29T19:56:01ZVeesh Goldmanrabbiveesh@gmail.com2023-10-29T19:39:57Zurn:sha1:c36681bb496ebce2946867459ed08774cb61788crefactor: 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.
chore(perl): update parser2023-10-23T18:40:18ZVeesh Goldmanrabbiveesh@gmail.com2023-10-23T18:40:18Zurn:sha1:84544f5cd3b7c046ebe0db6763c9ce7f20f4fe23feat(perl)!: switch to tree-sitter-perl org's parser2023-10-21T18:41:22ZVeesh Goldmanrabbiveesh@gmail.com2023-10-17T19:32:09Zurn:sha1:bb3f8f40b1443fb40665263e1b5b0658bc24be03chore(injections)!: update injection syntax to 0.92023-08-12T15:34:15ZPham Huy Hoanghoangtun0810@gmail.com2023-05-03T10:07:59Zurn:sha1:78b54eb7f6a9956d25a3911fa0dfd0cabfe2a4c5
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
feat(perl): improve highlights2023-08-03T12:45:39ZObserverOfTimechronobserver@disroot.org2023-08-03T10:49:22Zurn:sha1:131f665f9008d69d130f76f77603886e75c4b146fix(perl): update highlights from upstream changes2023-08-01T07:13:09ZAmaan Qureshiamaanq12@gmail.com2023-08-01T07:04:44Zurn:sha1:8e70f17f711afbef96b7a27b8c8ee08f7e5dc5e9perf: remove match where possible2023-04-21T22:24:17ZAmaan Qureshiamaanq12@gmail.com2023-04-21T08:06:20Zurn:sha1:85330918f05b3a4bd342a69063e7ef5fcdfadd2efeat(perl): update queries from upstream changes2023-03-27T17:49:44ZAmaan Qureshiamaanq12@gmail.com2023-03-27T17:30:37Zurn:sha1:47615a947ab2c40ac97dbd6082cac6de179256d0highlights: create subscoping for ternary operator2022-12-02T20:42:11ZStephan Seitzstephan.seitz@fau.de2022-12-02T19:22:58Zurn:sha1:d6a2ecb8b7093d6f6673cb6748bce9214a5099d3
After https://github.com/nvim-treesitter/nvim-treesitter/issues/470,
we decided to use `@conditional` for ternary operator instead of
operator despite `@conditional` is documented for keywords only.
A sub-scoping can make it easier for people to highlight this operator
group differently.
Also unify the usage of `@conditional...` across languages.
injections: add more regex injections2022-11-27T16:35:10ZObserverOfTimechronobserver@disroot.org2022-11-26T12:27:21Zurn:sha1:9018fb26cc91c5e2349f94e39e8fdcfd43773891highlights: use @preproc where appropriate2022-10-15T15:49:01ZObserverOfTimechronobserver@disroot.org2022-09-18T17:15:23Zurn:sha1:9b43ab819c756f01d2977cd481bdcaead6867174feat(spell): upstream spell queries from spellsitter2022-09-06T11:44:19ZLewis Russelllewis6991@gmail.com2022-09-06T10:56:27Zurn:sha1:2a63ea5665a6de96acd31a045d9d4d73272ff5a9Split func/method definition from calls in several programming language queries2022-08-03T19:05:30Zlfenzolfenzo@protonmail.com2022-07-30T00:09:58Zurn:sha1:c784720917bacb6716ce35ef07d464f5da738dd7Initial attempt at queries/perl/folds.scm2022-02-22T13:13:48ZPaul "LeoNerd" Evansleonerd@leonerd.org.uk2022-02-21T15:30:53Zurn:sha1:3533721282669e945b62b3ae9c53d4c5ffe16c76Add many perl keywords; highlight on those in preference to structural elements2022-02-22T13:13:48ZPaul "LeoNerd" Evansleonerd@leonerd.org.uk2022-02-21T15:30:35Zurn:sha1:09ea6ccd1d75e3896a66a2cbde6b24b7b1c6d902"::" should be of type "operator"2021-09-20T23:08:32ZLucas Crownoverlcrownover127@gmail.com2021-09-20T21:44:50Zurn:sha1:ec31c7efabff07411d11b889bcc4bba88605db94
swap constant for operator per treesitter recommendationSeparate special variables to catch up master2021-09-20T23:08:32Zdelphinusme@delphinus.dev2021-08-30T08:52:23Zurn:sha1:2f37720c8a4b46fa49df25b71345935bacc79959Use @string.regex to highlight regex's2021-09-20T23:08:32Zdelphinusme@delphinus.dev2021-08-30T03:36:55Zurn:sha1:0aaf937802eda8d01410c37a5c839bc1b8e29f64Add minimum implementation for highlights2021-09-20T23:08:32Zdelphinusme@delphinus.dev2021-08-28T08:16:35Zurn:sha1:ae9a9d60f155beca8580acf5b52b9da8f428356a