wezterm icon indicating copy to clipboard operation
wezterm copied to clipboard

activate-pane Fail

Open aplatypus opened this issue 1 month ago • 0 comments

What Operating System(s) are you seeing this problem on?

Linux Wayland

Which Wayland compositor or X11 Window manager(s) are you using?

Plasma v5 wl_compositor, version: 5, name: 1 wl_subcompositor, version: 1, name: 33

WezTerm version

20240508-081413-d2fa4e98

Did you try the latest nightly build to see if the issue is better (or worse!) than your current version?

Yes, and I updated the version box above to show the version of the nightly that I tried

Describe the bug

Build from main:

  • wezterm 20240508-081413-d2fa4e98

To Reproduce

  1. Start in WezTerm pane:
    • current window: $WEZTERM_PANE => 616
  2. Open new WezTerm window:
    • new window: $WEZTERM_PANE => 777
  3. Apply activate-pane command -- Intention to (re-)activate, or return to, pane: 616
    • from new within pane: 777.
    • No change, focus/activation stayed on the 777 pane.
  4. Use wezterm cli send-text activate original pane (id: 616) from bash shell in xterm session.
    • No change, focus/activation did not change to 616 pane.
  5. The command: wezterm cli activate-pane --pane-id 616 from different pane (id = 778) in the same window as 616 ...
    • Worked as expected;
    • Focus changed from the other pane (778) to the target pane 616

Configuration

(no config)

Expected Behavior

  • Expect that: activate-pane command would change GUI focus to the target pane (and window).
    • E.g.: --pane-id "616"
  • To set-focus/activate pane: 616 (and the window containing pane 616).
  • The activate-pane is expected to change focus to the target, e.g.: 616 from any location.
  • Should work like the successful example: wezterm cli activate-pane --pane-id 616 * Issued from another pane in the same window as 616.

Logs

There was nothing reported in the logs aviable. There is one entry following the spawn --new-window instruction:

ERROR wezterm_mux_server_impl::local > writing pdu data buffer: Broken pipe (os error 32)

Which is also emitted on the terminal (launched from bash session).

Anything else?

aplatypus avatar Jun 09 '24 13:06 aplatypus