Interactive PTY session: opened a repository commit pane with navigation history, pressed q, and confirmed immediate clean process exit instead of back navigation
This is TUI-only, so no iPhone release build was performed as requested.
Implemented in `ccaa920`.
- `q` now exits the TUI from every non-editor state, including nested panes and confirmation overlays.
- Editors still accept `q` as normal text input.
- Escape and Backspace retain their existing back/cancel behavior.
- Built-in help now describes `q` unambiguously as quit.
- Added a regression test proving nested history is not popped and a confirmation is not merely dismissed.
Verification:
- `cargo fmt --all -- --check`
- `RUSTFLAGS="-D warnings" cargo check --workspace --all-targets`
- `cargo clippy --workspace --all-targets -- -D warnings`
- `cargo test --workspace` (45 tests)
- Interactive PTY session: opened a repository commit pane with navigation history, pressed `q`, and confirmed immediate clean process exit instead of back navigation
This is TUI-only, so no iPhone release build was performed as requested.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
right now "q" kinda behaves like backspace in that it goes one back, but "q" should just exit the app.
Implemented in
ccaa920.qnow exits the TUI from every non-editor state, including nested panes and confirmation overlays.qas normal text input.qunambiguously as quit.Verification:
cargo fmt --all -- --checkRUSTFLAGS="-D warnings" cargo check --workspace --all-targetscargo clippy --workspace --all-targets -- -D warningscargo test --workspace(45 tests)q, and confirmed immediate clean process exit instead of back navigationThis is TUI-only, so no iPhone release build was performed as requested.