Revert .tmux.conf to minimal initial config #1

New issue

Open

opened 2026-04-10 16:23:06 +00:00 by forgejo_admin · 0 comments

forgejo_admin commented

2026-04-10 16:23:06 +00:00

Owner

Type

Bug

What Broke

Layered additions on top of abeb159 introduced user-visible bugs and made the config opaque:

Ctrl-b c opens new windows at the end of the stack instead of next to the current window
after-split-window + pane-exited rebalance hooks fight manual pane layouts
TPM + tmux-resurrect + tmux-continuum + pain-control + catppuccin widen the surface area of possible breakage without clear benefit
</> swap-window bindings required a follow-up "insert at boundaries" fix (kludge on kludge)

Repro Steps

cd ~/tmux-custom && git log --oneline — see 5fd40bb, df57813, 11a3cda stacked on abeb159
In a tmux session using current .tmux.conf, press Ctrl-b c while focused on a window in the middle of the stack
Observe: new window appears at the end, not next to current

Expected Behavior

.tmux.conf should match the minimal 22-line baseline from abeb159 (mouse on, clickable session, battery in status-right, vi mode). From that clean state, future additions land deliberately, one per PR, only if they earn their keep.

Environment

Host: archbox (Linux 6.18.9-arch1-2)
tmux: system package
Repo: ~/tmux-custom, branch main at 11a3cda
Also has uncommitted branch 1-fix-window-move-insert with 8a8fcf5 (doesn't touch bind c, unrelated to the Ctrl-b c bug)

Lineage

Standalone — dotfile regression triage. Not tied to a plan.

Repo

forgejo_admin/tmux-custom

User Story

As Lucas, I want my tmux config small enough to read without scrolling and Ctrl-b c to behave predictably, so I can trust it and add features back deliberately.

Context

Lucas confirmed: "we've made it worse." Recent commits (5fd40bb onward) stacked plugins and hooks that outweigh their value. Going back to baseline.

File Targets

.tmux.conf — restore byte-identical to abeb159:.tmux.conf

Acceptance Criteria

.tmux.conf matches abeb159:.tmux.conf exactly (22 lines)
Forward revert commit — history preserved, no reset --hard + force push
Commit message records why the additions were removed (bug list above)

Test Expectations

Manual: after merge, tmux source-file ~/.tmux.conf reloads cleanly with no TPM/catppuccin references.

Constraints

No history rewrite. Forward revert only.
Do not touch ~/.tmux/plugins/ on disk — user decision after merge.
Do not re-add any removed features in this PR.

Checklist

Branch from main
git checkout abeb159 -- .tmux.conf
Commit with rationale
Open PR
Merge after approval

Reverts effects of: 5fd40bb, df57813, 11a3cda, 8a8fcf5
Baseline restored: abeb159

### Type Bug ### What Broke Layered additions on top of `abeb159` introduced user-visible bugs and made the config opaque: - `Ctrl-b c` opens new windows at the end of the stack instead of next to the current window - `after-split-window` + `pane-exited` rebalance hooks fight manual pane layouts - TPM + tmux-resurrect + tmux-continuum + pain-control + catppuccin widen the surface area of possible breakage without clear benefit - `<`/`>` swap-window bindings required a follow-up "insert at boundaries" fix (kludge on kludge) ### Repro Steps 1. `cd ~/tmux-custom && git log --oneline` — see `5fd40bb`, `df57813`, `11a3cda` stacked on `abeb159` 2. In a tmux session using current `.tmux.conf`, press `Ctrl-b c` while focused on a window in the middle of the stack 3. Observe: new window appears at the end, not next to current ### Expected Behavior `.tmux.conf` should match the minimal 22-line baseline from `abeb159` (mouse on, clickable session, battery in status-right, vi mode). From that clean state, future additions land deliberately, one per PR, only if they earn their keep. ### Environment - Host: archbox (Linux 6.18.9-arch1-2) - tmux: system package - Repo: `~/tmux-custom`, branch `main` at `11a3cda` - Also has uncommitted branch `1-fix-window-move-insert` with `8a8fcf5` (doesn't touch `bind c`, unrelated to the `Ctrl-b c` bug) ### Lineage Standalone — dotfile regression triage. Not tied to a plan. ### Repo forgejo_admin/tmux-custom ### User Story As Lucas, I want my tmux config small enough to read without scrolling and `Ctrl-b c` to behave predictably, so I can trust it and add features back deliberately. ### Context Lucas confirmed: "we've made it worse." Recent commits (`5fd40bb` onward) stacked plugins and hooks that outweigh their value. Going back to baseline. ### File Targets - `.tmux.conf` — restore byte-identical to `abeb159:.tmux.conf` ### Acceptance Criteria - `.tmux.conf` matches `abeb159:.tmux.conf` exactly (22 lines) - Forward revert commit — history preserved, no `reset --hard` + force push - Commit message records *why* the additions were removed (bug list above) ### Test Expectations Manual: after merge, `tmux source-file ~/.tmux.conf` reloads cleanly with no TPM/catppuccin references. ### Constraints - No history rewrite. Forward revert only. - Do not touch `~/.tmux/plugins/` on disk — user decision after merge. - Do not re-add any removed features in this PR. ### Checklist - [ ] Branch from `main` - [ ] `git checkout abeb159 -- .tmux.conf` - [ ] Commit with rationale - [ ] Open PR - [ ] Merge after approval ### Related - Reverts effects of: `5fd40bb`, `df57813`, `11a3cda`, `8a8fcf5` - Baseline restored: `abeb159`