Skip to content

Use claude code to detect and fix issues #146

Merged
roosta merged 12 commits into
masterfrom
dev
May 27, 2026
Merged

Use claude code to detect and fix issues #146
roosta merged 12 commits into
masterfrom
dev

Conversation

@roosta

@roosta roosta commented May 25, 2026

Copy link
Copy Markdown
Member

I pointed claude code at the repo, it found several issues. Some stuff I missed during last refactor (like groups linking to other non-existing groups) and duplicates. I cleaned up the treesitter groups, some deprecations that could be removed, and there was some missing groups.

roosta and others added 9 commits May 25, 2026 12:12
- fix haskellPreProc link target (PrePrec -> PreProc)
- fix NvimPager cyan/white groups mapping to magenta
- remove redundant PreCondit link overriding explicit definition

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Defined twice, it's not supposed to be blue
- goBuiltins -> Function
- jsonKeyword -> Identifier
- xmlAttrib -> Function
- xmlCdataStart -> Delimiter

No rendered change; aligns with the convention that language-specific
syntax groups link to base groups rather than reference palette colors.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
These were almost the same, each having its own direct color mappings,
this commit creates a new SrceryDiag abstraction we can link to instead
of setting individually

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
TS will identify a lot of stuff as @variable, which results in to much
italic
Without explicit links, @keyword.repeat, @keyword.import, @keyword.operator,
@keyword.modifier, and @keyword.directive fell back to @Keyword (Keyword=red),
diverging from their regex counterparts (Repeat=yellow, Include=cyan,
Operator=white, StorageClass=bright_blue, PreProc=cyan).

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
The TS* highlight groups were deprecated in Neovim 0.8 and have no
effect on current versions. Removed 15 legacy links and added their
modern @* equivalents, plus a few captures that lacked legacy
counterparts (@Property, @type.builtin, @tag.delimiter, @string.escape)
to keep regex and treesitter buffers visually aligned. @markup.italic,
@markup.strong, and @markup.underline are styled directly, removing
the need for placeholder Italic/Bold/Underline base groups.

Author note: Claude calls Italic, Bold and Underline placeholder, but
its a holdover from older versions, these used to exist, but wasn't
properly corrected during last refactor (3.0.0)

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@roosta roosta requested a review from MindTooth May 25, 2026 12:22
Link keyword.import to keyword, otherwise there is too much cyan in the
import section of several languages.
@roosta

roosta commented May 26, 2026

Copy link
Copy Markdown
Member Author

The force push reverted Include = red back to Include = cyan, then linking TS @keyword.import to keyword. This is because there simply was too much cyan in the import statements of several languages, but changing Include to red broke other parts. This more directly solves the problem.

@MindTooth

Copy link
Copy Markdown
Member

Hmm. Why does not vint run? 🤔 Will look into it.

@roosta

roosta commented May 26, 2026

Copy link
Copy Markdown
Member Author

Thanks for fixing, gonna hold off a minute on merge, im not entirely happy about the Include/Keyword yet, gotta do a few more experiments tomorrow.

This strikes a fair balance I think, with bright red for import
keywords. It looks good both on regex and TS
@roosta

roosta commented May 27, 2026

Copy link
Copy Markdown
Member Author

I think I found a good balance here. With treesitter:
image

Regex:
image

Set Include to be bright_red so as to differentiate between regular keywords. This creates a balanced import section for most languages.

@roosta roosta requested a review from MindTooth May 27, 2026 10:04
@roosta roosta merged commit 49e3fcd into master May 27, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants