| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | feat!: drop modules, general refactor and cleanup | Christian Clason | 2025-05-12 | 2 | -27/+0 |
| | | |||||
| * | chore: query formatting | Pham Huy Hoang | 2024-01-19 | 2 | -4/+9 |
| | | |||||
| * | refactor: Remove all `(ERROR) @error` captures | Pham Huy Hoang | 2023-10-25 | 1 | -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. | ||||
| * | feat: @spell on comments | Jaehwang Jung | 2023-09-12 | 1 | -1/+1 |
| | | |||||
| * | feat: add pymanifest parser | ObserverOfTime | 2023-08-13 | 2 | -0/+24 |
 |
index : nvim-treesitter | |
| [no description] | git mirrorbot |
| aboutsummaryrefslogtreecommitdiffstats |