Cannot return to lazydocker from `exec` status in Warp

[bowentan]

Describe the bug
Return from an exec shell status via ctrl d did not work properly in Warp, where a blank window would display.

To Reproduce
Steps to reproduce the behavior:

1. Launch lazydocker in Warp
2. Press shift e on a running container
3. Press ctrl d and enter
4. See blank

Expected behaviour
Should return to lazydocker

Desktop (please complete the following information):

• OS: MacOS 13.7.2 (22H313)
• Lazydocker Version: 0.24.1
• The last commit id if you built project from sources (run : git rev-parse HEAD)

Additional context
I tried in iTerm2, it worked properly.

[Tej12345]

Can confirm that with warp this issue does exist and has no way to bypass it.

[ulad-ramanovich]

Faced with the same problem. It makes lazy docker hard to use

[PROGRAM-IX]

Happens on kitty as well for what it's worth. Unfortunate as it means q-ing out of lazydocker and relaunching it to get back to what I was doing after an exec.

[GabrielBlondeau-Kirby]

Hello, I have the same issue :(

• Ubuntu 22.04.5 LTS
• Terminal: Warp

[AbrhamSayd]

Hey everyone — I've been investigating this and identified what I believe is the root
cause.

What's happening: After Suspend() + Resume(), tcell (the terminal library underneath
gocui) physically clears the screen but leaves its internal "last drawn" cell cache
stale. When gocui tries to redraw, it diffs against that stale cache, finds nothing
changed, and writes nothing — blank screen.

Fix: One line in gocui's Resume() — calling g.screen.Sync() after g.screen.Resume()
invalidates the cache and forces a full redraw. I've confirmed this resolves the issue
locally on Warp (macOS), Warp (Windows), and WSL2/Debian.

A PR is being prepared for jesseduffield/gocui. In the meantime, if you want to run a
patched build right now:

Build from source with the fix:

Prerequisites: Go 1.21+ installed

git clone https://github.com/jesseduffield/lazydocker.git
cd lazydocker

Open vendor/github.com/jesseduffield/gocui/gui.go, find the Resume() function ('line 1539') and
replace it with:

  func (g *Gui) Resume() error {
      g.suspendedMutex.Lock()
      defer g.suspendedMutex.Unlock()
      if !g.suspended {
          return errors.New("Cannot resume because we are not suspended")
      }
      g.suspended = false
      if err := g.screen.Resume(); err != nil {
          return err
      }
      // engage() clears the physical screen but leaves tcell's "last drawn"
      // cache stale. Sync() invalidates it so the next Show() does a full redraw.
      g.screen.Sync()
      return nil
  }

Then build and run:

go build -o lazydocker . && ./lazydocker

If you can test and report back whether this resolves it for you, that would help
validate the fix across more terminals and platforms and hopefully get it upstreamed
faster — PR open at jesseduffield/gocui: jesseduffield/gocui#101