Improve compose buffer syntax and highlight treatment #198

Closed
opened 2026-04-12 21:42:33 +00:00 by barrettruth · 0 comments
barrettruth commented 2026-04-12 21:42:33 +00:00

Problem

Compose/edit buffers should feel visually deliberate, but the intended contract needs to match the chosen editing model.

forge.nvim should treat compose/edit buffers like a gitcommit buffer:

  • authored content lives in the main title/body region
  • metadata/help lives in a commented scaffold block
  • that scaffold remains editable, but is visually distinct and semantically non-authored

Expected

Polish the compose/edit surface around that model rather than introducing virtual or pseudo-read-only UI.

Specifically:

  • make the authored content region obvious
  • make the metadata/help comment block obvious
  • make fetched/template metadata easy to scan inside the commented section
  • reduce highlight/syntax rough edges between authored markdown and comment scaffolding

Out of scope

This issue is not about making parts of the buffer truly read-only.
The agreed model is a normal editable buffer with a commented scaffold, similar to gitcommit.

## Problem Compose/edit buffers should feel visually deliberate, but the intended contract needs to match the chosen editing model. forge.nvim should treat compose/edit buffers like a `gitcommit` buffer: - authored content lives in the main title/body region - metadata/help lives in a commented scaffold block - that scaffold remains editable, but is visually distinct and semantically non-authored ## Expected Polish the compose/edit surface around that model rather than introducing virtual or pseudo-read-only UI. Specifically: - make the authored content region obvious - make the metadata/help comment block obvious - make fetched/template metadata easy to scan inside the commented section - reduce highlight/syntax rough edges between authored markdown and comment scaffolding ## Out of scope This issue is not about making parts of the buffer truly read-only. The agreed model is a normal editable buffer with a commented scaffold, similar to `gitcommit`.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
barrettruth/forge.nvim#198
No description provided.