Add an explicit abandon path for compose and edit buffers #200

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

It is not obvious how to cleanly abandon a partially written compose or edit buffer.

Right now the write path is defined, but the discard path is mostly implicit.
That makes it easy to leave scratch compose buffers around or be unsure whether closing them is the intended workflow.

Expected

Compose and edit buffers should expose a clear, intentional abandon path so users can discard in-progress work without guessing.

## Problem It is not obvious how to cleanly abandon a partially written compose or edit buffer. Right now the write path is defined, but the discard path is mostly implicit. That makes it easy to leave scratch compose buffers around or be unsure whether closing them is the intended workflow. ## Expected Compose and edit buffers should expose a clear, intentional abandon path so users can discard in-progress work without guessing.
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#200
No description provided.