You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What Operating System(s) are you seeing this problem on?
macOS
Which Wayland compositor or X11 Window manager(s) are you using?
N/A
WezTerm version
20240914-092101-9668fa94
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
When using the command wezterm connect my.server --new-tab, WezTerm opens a new window with the SSH connection instead of opening a new tab in the existing window, as described in the documentation. The --new-tab option appears to have no effect, resulting in the same behavior as if the option wasn't specified.
To Reproduce
Open a WezTerm window on macOS.
Set up as ssh domain in your config file.
Run the following command to SSH into a server:
wezterm connect my.server --new-tab
Observe that a new window opens instead of a new tab.
What Operating System(s) are you seeing this problem on?
macOS
Which Wayland compositor or X11 Window manager(s) are you using?
N/A
WezTerm version
20240914-092101-9668fa94
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
When using the command
wezterm connect my.server --new-tab
, WezTerm opens a new window with the SSH connection instead of opening a new tab in the existing window, as described in the documentation. The--new-tab
option appears to have no effect, resulting in the same behavior as if the option wasn't specified.To Reproduce
Configuration
Expected Behavior
The SSH connection should open in a new tab in the current WezTerm window, not in a separate window, as indicated in the documentation.
Logs
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered: