Summary
Make pane readiness behavior configurable independently from builder selection, so users can choose compatibility or speed without swapping the entire workspace builder.
Related: #1053, #1056, #1058.
Proposed behavior
- Add a
pane_readiness configuration policy that can be used by the classic builder and future builders.
- Preserve the current safe behavior by default unless a compatibility decision changes it deliberately.
- Support an
auto mode that enables readiness waiting where tmuxp knows it matters, especially zsh prompt redraw safety.
- Support an
always mode for users who want the safest prompt/layout behavior.
- Support a
never mode for users who prefer speed and accept prompt/layout race risk.
- Keep this policy separate from parallel builder work so users can tune readiness without opting into relaxed build ordering.
Example shape:
Acceptance criteria
- The default preserves existing workspace behavior.
- Tests cover
auto, always, and never behavior for default-shell panes and custom shell/window shell cases.
- Documentation explains the zsh prompt-readiness motivation and the speed/compatibility tradeoff.
- The option remains usable with the classic builder even before a parallel builder exists.
Summary
Make pane readiness behavior configurable independently from builder selection, so users can choose compatibility or speed without swapping the entire workspace builder.
Related: #1053, #1056, #1058.
Proposed behavior
pane_readinessconfiguration policy that can be used by the classic builder and future builders.automode that enables readiness waiting where tmuxp knows it matters, especially zsh prompt redraw safety.alwaysmode for users who want the safest prompt/layout behavior.nevermode for users who prefer speed and accept prompt/layout race risk.Example shape:
Acceptance criteria
auto,always, andneverbehavior for default-shell panes and custom shell/window shell cases.