From 1758fad8ca84254ff5e92ed0c8072bb8b5781ef3 Mon Sep 17 00:00:00 2001
From: Stephen Waits <steve@waits.net>
Date: Sun, 12 Apr 2026 15:01:16 -0600
Subject: [PATCH] fix: recreate bars killed by shrink-below-minimum resize
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

When the user shrinks the terminal window small enough that nvim
can't fit all splits (including our two bars + dapui panes + source),
nvim closes some windows to make room. winfixheight prevents resize
but doesn't prevent close. When the user expands again, the closed
bars don't come back automatically — the layout is permanently
broken until debug mode is toggled.

Fix: on VimResized (deferred via vim.schedule), check if sbar_win
and cbar_win are still valid. If either got killed, clear the
stale reference and call open_bars() which idempotently recreates
anything missing. Then re-pin dapui sizes to restore the intended
layout.

WinResized autocmd retained for intra-session drift (mouse-drag
resizes, plugin-driven wincmd=).

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
---
 lua/turbo-debug/mode.lua | 33 +++++++++++++++++++++------------
 1 file changed, 21 insertions(+), 12 deletions(-)

diff --git a/lua/turbo-debug/mode.lua b/lua/turbo-debug/mode.lua
index bcaae31..d3abf01 100644
--- a/lua/turbo-debug/mode.lua
+++ b/lua/turbo-debug/mode.lua
@@ -1085,26 +1085,35 @@ function M.enter()
       if active then M._install_for_buf(args.buf) end
     end,
   })
+  -- On editor resize:
+  --   1) if any bar got killed by a shrink-below-minimum, recreate it
+  --   2) re-pin dapui pane sizes (defensive against any plugin — our
+  --      own, another's, or nvim's own shrink-recovery — that might
+  --      have skewed the layout).
+  -- Deferred via vim.schedule so we run AFTER other plugins' handlers.
   vim.api.nvim_create_autocmd("VimResized", {
     group = group,
     callback = function()
-      -- Defer via vim.schedule so our pin runs AFTER any other plugin's
-      -- VimResized handler in the same event-loop tick. The user has
-      -- tiny-equalizer.nvim which runs `tabdo wincmd =` on VimResized,
-      -- equalizing every window — that fights our explicit sizing. By
-      -- re-asserting after them, we restore the layout.
-      vim.schedule(reposition_bars)
+      vim.schedule(function()
+        if not active then return end
+        -- recreate missing bars
+        if not (sbar_win and vim.api.nvim_win_is_valid(sbar_win)) then
+          sbar_win, sbar_buf = nil, nil
+        end
+        if not (cbar_win and vim.api.nvim_win_is_valid(cbar_win)) then
+          cbar_win, cbar_buf = nil, nil
+        end
+        open_bars()   -- idempotent; only creates what's missing
+        pin_dapui_sizes()
+        render_bars()
+      end)
     end,
   })
-  -- WinResized fires on any individual window resize (including user
-  -- mouse-drags on separators, or `wincmd =` from other plugins). We
-  -- re-pin defensively so intentional user resizes stick but drive-by
-  -- equalizer plugins don't wipe our layout.
+  -- WinResized catches mouse-drag resizes and plugin-driven wincmd=
+  -- that don't fire VimResized. Guarded against self-recursion.
   vim.api.nvim_create_autocmd("WinResized", {
     group = group,
     callback = function()
-      -- Only respond to resizes we DIDN'T initiate. Guard with a flag
-      -- so our own pin_dapui_sizes doesn't trigger an infinite loop.
       if M._pinning then return end
       vim.schedule(function()
         if not active then return end