# plan.planner.StepReason

- **Module:** plan.planner
- **Package:** libtmux
- **Language:** Rust
- **Kind:** enum
- **Source:** https://github.com/libtmux/libtmux-rs/blob/f0e37052c232636b61d095817046e6bfc8f2ca40/crates/libtmux/src/plan/planner.rs#L79
- **Page:** https://libtmux.org/en/rs/latest/reference/plan-planner-stepreason/

Why a [`Step`] is its own tmux invocation.

The answer a caller wants from [`Planner::explain`] is usually "why is this
not cheaper", so the reasons name the obstacle rather than the outcome.

## Members

- `MarkedFold` (constant): A pane creation sharing its invocation with what decorates it.
- `Folded` (constant): Several operations sharing one invocation.
- `CreatesId` (constant): Alone because it prints an id a later operation needs.
- `ReadsOutput` (constant): Alone because its output is its answer, and a shared invocation returns one merged stdout with no per-command boundary.
- `Alone` (constant): Alone because it had nothing to share with.