CurrentPaneDomain Not Working as Expected in Pane Splitting Configuration #57
Unanswered
cygnus1228
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi there! First of all, thank you for publishing this configuration. I’ve encountered an issue where CurrentPaneDomain doesn’t behave as intended in my pane splitting configuration.
Expected Behavior
New panes should open in the current domain (e.g., existing SSH session or working directory).
Actual Behavior
New panes always open in the default domain (local terminal).
Environment
WezTerm version: 20240203-110809-5046fc22 (via wezterm --version)
OS: Windows 11 Pro 23H2
Note: Basic splitting (without domain parameter) works fine.
Troubleshooting Attempted
✓ Confirmed DefaultDomain works as expected
✓ Tested alternate syntax: domain = { DomainName = 'CurrentPaneDomain' }
✓ Verified SSH sessions work independently
✓ Restarted WezTerm and system — issue persists
Questions
Is this a known limitation on Windows?
Does this require additional parameters (e.g., default_domain)?
Are there debug logs I can provide to help diagnose?
Thank you for your time! I’m happy to provide further details or run additional tests if needed.
Beta Was this translation helpful? Give feedback.
All reactions