Skip to content

fix(compose): align highlights with gitcommit and fugitive conventions#35

Merged
barrettruth merged 1 commit intomainfrom
fix/compose-highlights
Apr 3, 2026
Merged

fix(compose): align highlights with gitcommit and fugitive conventions#35
barrettruth merged 1 commit intomainfrom
fix/compose-highlights

Conversation

@barrettruth
Copy link
Copy Markdown
Owner

Problem

Compose buffer highlights used generic groups (Type, Directory, italic-only) that didn't match established Neovim git conventions, producing inconsistent colors across colorschemes.

Solution

Relink ForgeComposeFile to Constant (matching gitcommitSelectedFile), ForgeComposeForge to Label (matching fugitiveHeader). Add ForgeComposeHeader (PreProc) for section headers and ForgeComposeLabel (Label) for metadata keys like Draft: and Reviewers:, inspired by gitcommitHeader and gitcommitTrailerToken.

ForgeComposeCommentComment is deferred to #33 due to treesitter overlay conflicts.

Closes #29.

Problem: compose buffer highlights used generic groups (`Type`,
`Directory`, italic-only) that didn't match established Neovim
git conventions, producing inconsistent colors across colorschemes.

Solution: relink `ForgeComposeComment` to `Comment` (matching
`gitcommitComment`), `ForgeComposeFile` to `Constant` (matching
`gitcommitSelectedFile`), `ForgeComposeForge` to `Label` (matching
`fugitiveHeader`). Add `ForgeComposeHeader` (`PreProc`) for section
headers and `ForgeComposeLabel` (`Label`) for metadata keys, inspired
by `gitcommitHeader` and `gitcommitTrailerToken`.
@barrettruth barrettruth merged commit eefcce8 into main Apr 3, 2026
7 checks passed
@barrettruth barrettruth deleted the fix/compose-highlights branch April 3, 2026 23:11
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.

fix highlight colors use gitCommitSelected file and take inspiration from fugitive

1 participant