Skip to content

fix: wire up content pane registry for PTY dirty notifications#59

Merged
neumie merged 1 commit intomainfrom
fix/wire-content-pane-registry
Mar 24, 2026
Merged

fix: wire up content pane registry for PTY dirty notifications#59
neumie merged 1 commit intomainfrom
fix/wire-content-pane-registry

Conversation

@neumie
Copy link
Copy Markdown
Contributor

@neumie neumie commented Mar 24, 2026

Summary

  • The content pane registry callback (set_register_content_pane_fn) was never connected at startup
  • PTY events couldn't find terminal content panes to notify, so terminals only updated via GPUI's entity-tracking mechanism
  • Entity tracking doesn't work reliably through cached() views, causing 200–1300ms frame stalls

Changes

Wire up set_register_content_pane_fn in main.rs to insert into the existing content_pane_registry(). This is a 5-line fix — the registry and callback infrastructure already existed but were never connected.

Test plan

  • Type in a terminal — keystrokes render immediately (no lag)
  • Test with split panes and tabs — all terminals responsive
  • Verify cached() view optimization (from previous commit) still works

The content pane registry callback (set_register_content_pane_fn) was
never connected at startup, so the PTY event loop could never find
terminal content panes to notify. Terminals only updated via GPUI's
entity-tracking mechanism, which doesn't work reliably through cached
views — causing 200-1300ms frame stalls on macOS.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@neumie neumie merged commit 76421f9 into main Mar 24, 2026
8 checks passed
@neumie neumie deleted the fix/wire-content-pane-registry branch March 24, 2026 17:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant