aboutsummaryrefslogtreecommitdiffstats
path: root/queries/perl
Commit message (Collapse)AuthorAgeFilesLines
* feat!: drop modules, general refactor and cleanupChristian Clason2025-05-123-375/+0
|
* * feat(perl): highlight hash keys as `@variable.member` in various contextsVeesh Goldman2025-03-192-32/+48
| | | | also, injections for s///e should fully re-parse
* feat(perl): support more modern syntaxVeesh Goldman2024-09-221-0/+15
|
* feat(perl): update highlights and foldsPaul Evans2024-08-072-3/+35
|
* refactor(queries): Remove quotes from properties in set! directiveOmar Valdez2024-07-281-1/+1
|
* feat(perl): deactivate spelling in shebangsKai Moschcau2024-05-011-1/+1
|
* feat(perl): activate spelling in commentsKai Moschcau2024-05-011-1/+1
|
* feat(highlights)!: enforce documented captures (#6232)Christian Clason2024-03-031-13/+13
| | | | | | | | | | | | | | | 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 predicates再生花2024-02-231-2/+12
| | | "format-ignore".kick()
* chore: format queriesPhạm Huy Hoàng2024-01-211-2/+2
|
* feat(perl): add more highlightsVeesh Goldman2024-01-211-0/+3
|
* chore: query formattingPham Huy Hoang2024-01-193-80/+186
|
* feat!: align standard captures with upstreamChristian Clason2024-01-191-12/+12
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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 builtinsVeesh Goldman2023-11-031-7/+23
|
* feat: bump perlVeesh Goldman2023-10-291-2/+2
|
* refactor: Remove all `(ERROR) @error` capturesPham Huy Hoang2023-10-251-2/+0
| | | | | | | | | | | | 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 parserVeesh Goldman2023-10-231-1/+1
|
* feat(perl)!: switch to tree-sitter-perl org's parserVeesh Goldman2023-10-213-165/+133
|
* chore(injections)!: update injection syntax to 0.9Pham Huy Hoang2023-08-121-1/+2
| | | | | | | | | 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 highlightsObserverOfTime2023-08-031-59/+70
|
* fix(perl): update highlights from upstream changesAmaan Qureshi2023-08-011-2/+0
|
* perf: remove match where possibleAmaan Qureshi2023-04-211-1/+1
|
* feat(perl): update queries from upstream changesAmaan Qureshi2023-03-271-1/+0
|
* highlights: create subscoping for ternary operatorStephan Seitz2022-12-021-2/+4
| | | | | | | | | | 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 injectionsObserverOfTime2022-11-272-1/+3
|
* highlights: use @preproc where appropriateObserverOfTime2022-10-151-0/+3
|
* feat(spell): upstream spell queries from spellsitterLewis Russell2022-09-061-0/+1
|
* Split func/method definition from calls in several programming language querieslfenzo2022-08-031-2/+2
|
* Initial attempt at queries/perl/folds.scmPaul "LeoNerd" Evans2022-02-221-0/+12
|
* Add many perl keywords; highlight on those in preference to structural elementsPaul "LeoNerd" Evans2022-02-221-79/+87
|
* "::" should be of type "operator"Lucas Crownover2021-09-211-1/+1
| | | swap constant for operator per treesitter recommendation
* Separate special variables to catch up masterdelphinus2021-09-211-1/+3
|
* Use @string.regex to highlight regex'sdelphinus2021-09-211-2/+5
|
* Add minimum implementation for highlightsdelphinus2021-09-211-0/+169