Now that WinResized does a simple `redraw!` on every window-geometry
change, the accumulated defensive autocmds are redundant. Removed:
- `OptionSet showtabline` handler — when bufferline uses an expr
tabline format, the option itself never changes, so this never
fired for the primary case we cared about. When it DOES fire
(explicit `:set showtabline=N`), a window geometry change
immediately follows and WinResized handles the redraw.
- `BufEnter/BufWinEnter/TabEnter` fallback — was guarding against
bars going missing on buffer transitions. In practice bars only
get killed on editor resize (VimResized covers that), not on
buffer changes.
- Orphan bar cleanup in recover_chrome — earlier theory that the
"duplicate turbo-debug" rows came from stale windows. User
correctly diagnosed it as leftover render pixels; WinResized's
redraw! is the actual fix. No orphans to clean up.
- Internal `redraw!` in recover_chrome — redundant because when
recover_chrome runs (VimResized), it creates splits which trigger
WinResized which does the redraw for us.
What's left:
- VimResized: recreates bars killed by editor shrink + re-renders
- WinResized: single `redraw!` to clear stale pixels on any shift
Cleaner and easier to reason about.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
swaitsandClaude Opus 4.6
c420acd599