feat: reduce spiral node-leaf subtree churn during new-pane #113
Labels
No labels
breaking-change
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
skip-release-notes
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
barrettruth/tmux-mosaic#113
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Problem
In the harder
spiralnode-leaf phases, the new pane takes an outer leaf slot and the previous tail gets pushed inward. Those phases are not the same as the easy leaf-node phases and deserve their own treatment.Blocked by: #101, #102, #109
Proposed solution
Investigate how much of the visible subtree churn in
spiralnode-leaf phases can be reduced, isolated, or otherwise made less jarring during explicit managednew-pane.The goal is not to promise perfect elimination. The goal is to separate avoidable churn from the recursive topology changes that may remain necessary.
Context
The current matrix classifies these as local role-shift cases. The strongest surveyed reprojection precedent is
tmux-tiling-revamped, which rebuilds the BSP geometry and then performsswap-paneorder repair forspiral.Acceptance notes
Alternatives considered